Hi Guys and Gals,

I have a problem with a couple of Western Digital hard drives. I cannot get fdisk to see more that 10,781 MB on either drive. One is NEW (WD-800JB), other is RE-Furb (WD-800AW-R).

I am testing on the bench with bare necessities, no OS involved.

I have used two completly different mobo, CPU, Vid, Mem etc setups (all support Large Drives, with same results)

I have reduced my troubleshoot to the common denominator, the BOOT DISK('s) and a faulty FDISK.EXE program. Although I have tried FDISK.EXE from several different boot disks as well as a fresh copy off of the Partition Magic 8.0 Program

I have only used the two WD hard drives though. (Both Bad?? probably not likely, but possible).

I've been doing this for a few years now and havn't had a problem with fdisk not seeing all of the drive before, so I'm am asking for some input on this.

ps, I have heard of different versions of FDISK.EXE but have not seen anything different in any of them. How do you tell what version of FDISK you have anyway?? :?:

Thanks for any feedback on this subject

Do these drive contain any partions on them? Try to delete any partions on the drive then run a zerofill on it. It should break the drives allocations, then fdisk back in. If your looking to setup XP or Server, then just load the bootable disk and your can creat the partion the same way with out installing an OS: This option may work out better beuacse of more hardware support.

Try the GParted LiveCD, as it will try to scan a drive to account for bad partition tables.

Another option is the TestDisk tool on the ultimate boot cd, which in addition to scanning the disk for broken partition data, is often able to recover any lost data.

If you haven't lost any data on these, then zero-filling as PCcashCow suggested will fix the solution with minimal work (unless there's some hardware issue here, not likely) Many "wipers" are also on the ultimate boot cd.

I'm surprised you've never seen it before, cause I use fdisk probably once a week if not more, and it happens on all disks above a certain size. Sometimes the max size is 10G, sometimes 15G, give or take, but it never shows all the space on large disks.

ADDED: I just did some poking around, and it appears the displayed size for disks larger than 64G could be the disk size minus 64G. So, if the disk is 80G, the displayed size might be around 16G, etc. That's pretty much what I've seen and I don't recall exact numbers for specific drive sizes, but I always see the wrong size listed for large disks.

Why the hell do people still use FDISK?

Because it works and we're all old school. Jerky boy.

word. hehe

Knowing how to boot to a dos prompt and find your way around is invaluable.

I have also seen that. (64G could be the disk size minus 64G)

When this happens (fdisk won't read all), do you go ahead and format it anyway at the 10,781 size? How are you supposed to get the full usage out of the drive?

After I fdisk it (10,781mb), I go to format and it only wants to format 10,781???? Not 80G! Now What?

To be honest with you, I have never formated a partition like that. I always use fdisk to create a partition equal or smaller than the recognized size. However, it seems I do recall once just selecting the maximum size it recognized, then formated the drive, and it was the full, actual size of the disk, not the incorrectly displayed size from fdisk. But, I can't say for sure that is what happened.

Give it a try, it can't hurt anything. If it doesn't work right, no harm done, just start over. let me know what happens.

No, there are no partitions and No OS involved. I am running these on the bench with the bare necessities. These are fresh drives. 1 new and 1 a just bought refurb.

I just used Data Lifeguard tool to zerofill the drive and it had no effect.

BTW, DLG found no errors on the drive after running the DIAGs.

Thanks

I found this page, that has a link to an updated fdisk.exe file, but I haven't tried this version of fdisk to see if it works with large disks.

It looks like that version is just the one that ships with 98se, which is what I have I'm pretty sure.

Where do I find copies of the softwear below.
---
Another option is the TestDisk tool on the ultimate boot cd, which in addition to scanning the disk for broken partition data, is often able to recover any lost data.
---

Thanks

I see on the ultimate boot cd page linked above, there is a free-fdisk utility you might want to try.

What I usually do is; fdisk a full sized partition (C: Drive 100%). Then load OS and partition with Partition Magic.

I am formatting now (at 10,781), to see what happens.

Thanks

If you're talking about windows XP, then why not just create the partition from within the loading menu?

The only reason I use fdisk now is if I'm replacing a disk on an existing machine and want to, for example, ghost one disk to another, but want to have a smaller system partition, etc. If I'm just loading the OS from scratch, I can't think of any good reason to use fdisk. That is, if you are using XP.

Real answer: don't use "A:fdisk.exe", use "/usr/sbin/fdisk"