Re: 61GB in bad sectors (ref: 200GB drive reads as 128)

From: Ron Martell (ron.martell_at_gmail.com)
Date: 09/15/04


Date: Wed, 15 Sep 2004 04:08:09 GMT


"S" <sa###@msn.com> wrote:

>Sorry for the long post.
>
>My problem is that I have corrupted data (61132684 KB in bad sectors) on my
>200GB WD hard drive. That's right - 61GB!
>Not too happy with that because I had a difficult time partitioning and
>installing xp on the drive and had to settle for a single partition. Each
>effort to make multiple partitions resulted in less than 186GB of total
>avail. space.
>So, I installed with a Windows XP Pro with SP1a CD on the single partition
>(186GB).
>My Intel 845 motherboard already had the latest BIOS (48-bit LBA support
>confirmed).
>Things went fine as far as I could tell.
>I've had no problems with the correct space being reported or bad sectors
>for the last month or so. I just happend to take a look at available space
>last night and was shocked to see only 85.4GB left! Well, I only have
>40.8GB (44,387 Files, 2,234 Folders) of data on my C:\ so obviously
>something is wrong somewhere.
>186-40.8 != 85.4
>
>Running chkdsk found this:
>
>"C:\Documents and Settings\Scott>chkdsk
>The type of the file system is NTFS.
>Volume label is XP Professional.
>
>WARNING! F parameter not specified.
>Running CHKDSK in read-only mode.
>
>CHKDSK is verifying files (stage 1 of 3)...
>File verification completed.
>CHKDSK is verifying indexes (stage 2 of 3)...
>Index verification completed.
>CHKDSK is verifying security descriptors (stage 3 of 3)...
>Security descriptor verification completed.
>Correcting errors in the Volume Bitmap.
>Windows found problems with the file system.
>Run CHKDSK with the /F (fix) option to correct these.
>
> 195350368 KB total disk space.
> 44652732 KB in 43976 files.
> 16268 KB in 2255 indexes.
> 61,132,684 KB in bad sectors.
> 140072 KB in use by the system.
> 65536 KB occupied by the log file.
> 89408612 KB available on disk.
>
> 4096 bytes in each allocation unit.
> 48837592 total allocation units on disk.
> 22352153 allocation units available on disk."
>
>I ran "chkdsk /f" (required a reboot) but the bad sectors have stayed.
>Nothing has changed with "chkdsk /r" either.
>
>WD's Data Lifeguard Quick Test results:
> Test Option: QUICK TEST
> Model Number: WDC WD2000BB-00DAA3
> Serial Number: WD-WMACK1926431
> Firmware Number: 571.B357
> Drive Type: IDE
> Port Number: 0, Primary/Master
> Capacity: 134.22 GB
> SMART Status: PASS
> Test Result: PASS
> Test Time: 18:31:51, September 14, 2004
>
>After lots of googlin' I finally found MKBA-303013.
>
>I checked my registry and
>"HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Atapi\Parameters\" did
>NOT have the "EnableBigLba" key AT ALL!
>
>That was one thing I didn't do and I don't know how if this is responsible
>for the problem.
>
>I also don't know if adding this key will solve the problem (I am backing up
>all my data now so I will give it a shot).
>
>The reason I'm bugging you is I want to know if I can EVER get XP to
>recognize the whole 200GB drive and (if it comes down to another fresh
>install)
>HOW DO I INSTALL XP PROPERLY to do that.
>There's no time PRE-installation to edit the registry. SP1, I would think,
>should have set this key but it didn't.
>
> Is there something I'm missing or am I hosed?
>Is the Data Lifeguard Quick Test telling me anything (except the incorrect
>capacity) ?
>
>
>Thanks in advance!
>

A drive with 30% of its capacity in bad sectors is almost certainly
doomed and could fail completely at any moment. I am surprised that
it passes even the WD Data Lifeguard Quick Test. What does the
complete test tell you?

I would be checking with WD regarding possible warranty status for
this drive and getting a replacement a.s.a.p.

As for the capacity question, this is the old confusion between binary
and decimal measures for computer data.

Computers have always used binary measures for capacity.
Kilobyte = 1,024 bytes (2^10)
Megabyte = 1,048,576 bytes (2^20)
Gigabtye = 1,073,741,824 bytes (2^30)

However the hard drive manufacturers have decided to use decimal
values for reportion the capacity of their drives and so to them a
gigabyte = 1,000,000,000 bytes

Windows reports the drive capacity in binary gigabytes.

186 binary gigabytes x 1,073,741,824 = 199,715,979,264 bytes which
Western Digital would round up to 200 billion and call the drive a 200
gigabyte model.

Similarly with your chkdsk report:

195350368 KB x 1024 = 200,038,776,832 bytes, bang on with the 200 gb
value by Western Digital.

But with 61 gb of bad sectors (unless you got the drive for free) I
would be looking to replace it as soon as possible.

Good luck

Ron Martell Duncan B.C. Canada

-- 
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca
"The reason computer chips are so small is computers don't eat much."


Relevant Pages

  • Re: Hard Disk Failure
    ... Does the HDD's OEM diagnostic tool see the full size of the HDD, ... Do you see anything in Disk Management that relates to the 160GB HDD, ... tool on the drives and this is the result. ... Sectors per Cluster: 8 ...
    (microsoft.public.windowsxp.hardware)
  • Re: Hard Disk Failure
    ... is so much stuff on the hard disk that I want to try to keep. ... tool on the drives and this is the result. ... Sectors per Cluster: 8 ... MFT Start Cluster: 786432 ...
    (microsoft.public.windowsxp.hardware)
  • Re: Summary of Recent Data Recovery Methods; Spinrite 5.0
    ... > I had a 3 gig hd with about 5-10% bad sectors. ... > most data and DP had no special recovery capabilities other than ... But you need to make up your mind: You either clone a disk as ... xcopy data off failing drives, ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: Quantum XP39100S Atlas II and 8GB limit (not int 13h extd related?)
    ... Seagate nor Maxtor seem to know or have anything to do with this disk ... LBA sectors, ... capacity of 9.1GB or so. ... it's been happily working with 18GB drives just fine). ...
    (comp.periphs.scsi)
  • Re: Hard Disk Failure
    ... is so much stuff on the hard disk that I want to try to keep. ... tool on the drives and this is the result. ... Sectors per Cluster: 8 ... MFT Start Cluster: 786432 ...
    (microsoft.public.windowsxp.hardware)