I have a problem. I had the "mount: wrong fs type, bad option, bad superblock on /dev/hdb1" problem and ended up loosing everything on both drives I had.

This error really needs to be fixed.

Anyway I have a WD3200BJ Western Digital 320 GB drive and it will not report anything larger than 305 GB capacity with 298 GB free. I have no partitions on this drive I am trying to get it running now. I also have a 250GB drive which is reporting find 239 total space available to partition. This problem started right after I got the error mentioned above.

Motherboard: A8N-SLI Premium
Hard Drive: Western Digital wd3200bj
System: Ubuntu 6.10

Also, I ran this hard drive for about a year with windows with no problems. It started when I put it in the new computer. The data is gone and there are no partitions on the drive so I can do what ever is needed to get this problem fixed.

Any suggestions are welcome.

ddevore

Isn't that the typical issue with the drive manufacturer quoting the
size in base 10 units and the computer mostly reporting in base 2?

See "consumer confusion" section in
REF: http://en.wikipedia.org/wiki/Megabyte

Mark

This is the normal marketing gag of hard disk/DVD/storage media manufacturers. Your "missing" GB are simply not present physically. If you would have checked the drive size in Windows, it would have given you similar figures. Don't even try fixing it, you can't, it's normal your OS (Linux, Windows, whatever else) does display this values.

For more infos follow the link markos provided.

I understand that there is a difference between what is advertised and what is actual but a 22gb loss on a 320gb HD seemed a little much and I don't remember it being that big of a loss before my little error mentioned before.

Is there someone with this drive who can confirm this size for me?

The size is being reported correctly. WD is claiming that the size is 320,000,000,000 bytes. The OS is reporting the size in terms of multiples of 1024.

Try:
and see what it returns.

Those darned marketing people play this game to make things appear bigger than they are. (And that's all I'm gonna say in order to keep it clean. )

Your memory is decifient, or you were duped.
Bigger disks show (more) disproportionate differences - try the math for 500Gig, and compare to your 250 Gig experience.

Though I hate to admit it but I must admin my memory must be deficient. Thanks for the replies.

Hi


I do understand that the the actual size of the hard disk is not the advertised one

but in my case i have installed today a 200 GB hard drive.

the western digital support knowledge base reports the actual size for a 200 GB is 186 GB

now after formating with the command
mkfs -c -t ext2 /dev/hdc1

the df -h and KDiskFree utility reports 186 GB the size of the disk
and as available 174 GB.


Why is that ? i am losing extra 12 GB . I though i would have been a 186 GB hard drive not a 174GB

Any suggestions very appreciated

I have this drive. "df" reports it as 312437568 1K-blocks in size.

Hi Quakeboy02

so how many GBs available do you see ? 174 or 186 or perhaps something else.

Here is the "df" for my drive in its entirety:

Filesystem 1K-blocks Used Available Use% Mounted on

/dev/hdb1 312437568 13084996 299352572 5% /data2

Adding Used and Available does actually equal 312437568

AFAIK, you lost the additional 12GB because of the filesystem you selected. I have given up on ext3 precisely because of that. A 100GB partition would have only 94 or 95GB available; when I use XFS instead, it has 99.something available. Careful: I may be wrong - ext2 may be different from ext3 in this respect - but I guess someone else who is actually using ext2 could clear this up.

Hi

when i sum used and available i get 182524204

Filesystem 1K-blocks Used Available Use% Mounted on
dev/hdc1 192292124 18829624 163694580 11% /mnt/music

i started adding data but thats irrelevant

By default when an ext2/3 filesystem is created 5% is reserved for root use.
The output of the df command does not show this space. Reserved space is supposed to reduce fragmentation as well as allow root to login if the filesystem becomes full.

You can use tune2fs to reduce the amount of reserved space. If this filesystem is used just for data then you can safely set it to 0%

Hi michaelk

You saved me lots of time from truing various file systems to restore those 12 GBs. I have set to 0 the root reserved space by following this thread
and now i have reached 184GB


Thank you all for assisting me


regards