1.3MB bad sector!

[kaz]

Hi,
My comp:
win xp all updates
athlon 2000xp
HD= http://www.seagate.com/cda/products/discsales/marketing/detail/0,1081,381,00.html

A few weeks ago I realized that I had 128KB of bad sector. Then for
that past few days my comp has been crashing. Once it crashed and I
restart the pc and I get a message saying the registry had to be
recovered. Then my comp was running really slow. Hanging whenever I
was trying to access the HD. I tried to analyze the drive using
diskeeper, but it would just hang. Also my drive was making really
weird noises like it was stuck. So I restart my comp run check disk
and the following happens. This is a very long log, but most of it is
bullshit. Btw I use Bit torent a lot. I thought I should tell you guys
that because someone told me it really messes up your HD

*********************************************************************
Checking file system on D:
The type of the file system is FAT32.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
Volume Serial Number is 1B32-10D2
The \pagefile.sys entry contains a nonvalid link.
Read failure with status 0xc000009c at offset 0x9e7fbc000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0x9e7fbc000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x9e8034000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x9e83b4000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x9e8994000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x9e8a6c000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x9e8acc000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x9e8b2c000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x9e8c3c000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x9e8eec000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x9e8f4c000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x9f0734000 for 0x8000
bytes.
Windows replaced bad clusters in file \pagefile.sys
of name (null).
The size of the \pagefile.sys entry is not valid.
Read failure with status 0xc000009c at offset 0xb43954000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0xb43954000 for 0x8000
bytes.
Folder \j2sdk1.4.0_03\docs\api\javax\imageio\plugins is entirely
unreadable.
Folder entry removed.
Read failure with status 0xc000009c at offset 0xb30144000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0xb2adc4000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0xb2adc4000 for 0x8000
bytes.
Folder \j2sdk1.4.0_03\docs\api\java\awt\event is entirely unreadable.
Folder entry removed.
Read failure with status 0xc000009c at offset 0x30808c000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x30808c000 for 0x8000
bytes.
Windows replaced bad clusters in file \Program Files\Common
Files\Symantec Shared\CommonClient.dat
of name (null).
Read failure with status 0xc000009c at offset 0x4046cc000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x4046cc000 for 0x8000
bytes.
Windows replaced bad clusters in file \Documents and Settings\Kaz
\Local Settings\Temporary Internet Files\Content.IE5\GK2ZTU42\js[13]
of name (null).
Read failure with status 0xc000009c at offset 0x403e04000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x403e04000 for 0x8000
bytes.
Windows replaced bad clusters in file \Documents and Settings\Kaz
\Local Settings\Temporary Internet
Files\Content.IE5\CTQ74DEJ\home[1].htm
of name (null).
Read failure with status 0xc000009c at offset 0x404584000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x404584000 for 0x8000
bytes.
Windows replaced bad clusters in file \Documents and Settings\Kaz
\Local Settings\Temporary Internet
Files\Content.IE5\CTQ74DEJ\hNavCats[1].gif
of name (null).
Read failure with status 0xc000009c at offset 0x404564000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x404564000 for 0x8000
bytes.
Windows replaced bad clusters in file \Documents and Settings\Kaz
\Local Settings\Temporary Internet Files\Content.IE5\22EVXMY0\js[28]
of name (null).
Read failure with status 0xc000009c at offset 0x4045dc000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x4045dc000 for 0x8000
bytes.
Windows replaced bad clusters in file \Documents and Settings\Kaz
\Local Settings\Temporary Internet
Files\Content.IE5\22EVXMY0\p0059144_c0000020_p0000000[1].jpg
of name (null).
Read failure with status 0xc000009c at offset 0x40465c000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x40465c000 for 0x8000
bytes.
Windows replaced bad clusters in file \Documents and Settings\Kaz
\Local Settings\Temporary Internet
Files\Content.IE5\22EVXMY0\amazing_deals[1].gif
of name (null).
Read failure with status 0xc000009c at offset 0x4045cc000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x4045cc000 for 0x8000
bytes.
Windows replaced bad clusters in file \Documents and Settings\Kaz
\Local Settings\Temporary Internet
Files\Content.IE5\KVPRIUN5\p0034833_c0000007_p0000000[1].jpg
of name (null).
Read failure with status 0xc000009c at offset 0x4045ec000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x4045ec000 for 0x8000
bytes.
Windows replaced bad clusters in file \Documents and Settings\Kaz
\Local Settings\Temporary Internet
Files\Content.IE5\4T6RCTMV\p0059308_c0000042_p0000000[1].jpg
of name (null).
Read failure with status 0xc000009c at offset 0x40457c000 for 0x8000
bytes.
Read failure with status 0xc000009c at offset 0x40457c000 for 0x8000
bytes.
Windows replaced bad clusters in file \Documents and Settings\Kaz
\Local Settings\Temporary Internet
Files\Content.IE5\WNGHAZY5\cart[1].gif
of name (null).
The size of the \WINDOWS\Internet Logs\STUEF1C.ldb entry is not valid.
\WINDOWS\Prefetch\NUCD.EXE-02CB91BF.pf first allocation unit is not
valid. The entry will be truncated.
Bad links in lost chain at cluster 458260 corrected.
Bad links in lost chain at cluster 458774 corrected.
Bad links in lost chain at cluster 458780 corrected.
Bad links in lost chain at cluster 459073 corrected.
Bad links in lost chain at cluster 459560 corrected.
Bad links in lost chain at cluster 1249915 corrected.
Bad links in lost chain at cluster 1251689 corrected.
Convert lost chains to files (Y/N)? Yes
191232 KB in 124 recovered files.
Windows is verifying free space...
Read failure with status 0xc000009c at offset 0xa6f844000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0xa6f854000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0xa6f894000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0xa6f984000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0xa6f994000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0xa6fa74000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0xa6f844000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0xa6f854000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0xa6f894000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0xa6f984000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0xa6f994000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0xa6fa74000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0xa6f844000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0xa6f854000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0xa6f894000 for 0x10000
bytes.
Read failure with status 0xc000009c at offset 0xa6f984000 for 0x10000
bytes.
Bad sectors found.
Free space verification is complete.
Windows has made corrections to the file system.
74041504 KB total disk space.
585824 KB in 1122 hidden files.
130176 KB in 4062 folders.
63662464 KB in 49513 files.
1376 KB in bad sectors.
9661632 KB are available.

32768 bytes in each allocation unit.
2313797 total allocation units on disk.
301926 allocation units available on disk.
*********************************************************************
So here are my questions:
Has downloading shit loads of stuff of bit torrent made my HD worse?
Where are these bad sectors? Are they near the boot? If so am I
****ed?
Do I need to replace this HD?
Or can I fix this problem, by re formatting my drive/re-install OS?
Why is this happening? Is it physically my hard disk or my bad
management of software?

Btw I would like to say I don't really care about losing the 1.3mb,
but I just want to be sure my HD won't die on me and carry on getting
worse.
I have so much important stuff on my comp and I can't risk losing it.

I would to thank you in advance for any help you can give me, also i
am sorry if some of the stuff i have said is Amateurish, but i know
very little about this sort of thing.

regards
kaz

P.S It would be great, if you could email and post your responses.

 

[Joep]

So here are my questions:
Has downloading shit loads of stuff of bit torrent made my HD worse?
No.

Where are these bad sectors? Are they near the boot? If so am I
****ed?

With that many you're ****ed anyway, you don't have to bother where they are
....

Do I need to replace this HD?
Guess

Or can I fix this problem, by re formatting my drive/re-install OS?
Guess

Why is this happening?
Guess

Is it physically my hard disk
Yes
or my bad
management of software?

No

Btw I would like to say I don't really care about losing the 1.3mb,
but I just want to be sure my HD won't die on me and carry on getting
worse.

It will probably

I have so much important stuff on my comp and I can't risk losing it.

Sigh, then replace the disk

I would to thank you in advance for any help you can give me, also i
am sorry if some of the stuff i have said is Amateurish, but i know
very little about this sort of thing.

A bit of common sense would be nice though ...

 

[S.Heenan]

1376 KB in bad sectors.
Do I need to replace this HD?

Yep, ASAP.

Btw I would like to say I don't really care about losing the 1.3mb,
but I just want to be sure my HD won't die on me and carry on getting
worse.
I have so much important stuff on my comp and I can't risk losing it.

If it's that valuable to you, you have it backed up somewhere, right ?


"It's dead Jim"
Stop using the drive now and you may be able to recover data from it when
it's connected as a slave. Bite the bullet and buy a new hard drive.

 

[J. Clarke]

Hi,
My comp:
win xp all updates
athlon 2000xp
HD=
http://www.seagate.com/cda/products/discsales/marketing/detail/0,1081,381,00.html

A few weeks ago I realized that I had 128KB of bad sector.

At that point you had good notice that your drive was going to die. When
any modern drive reports that many bad sectors that means that it's very
likely used up its hot-spare space already with bad sectors that you never
see. When that happens things are just gong to get worse.

Then for
that past few days my comp has been crashing. Once it crashed and I
restart the pc and I get a message saying the registry had to be
recovered. Then my comp was running really slow. Hanging whenever I
was trying to access the HD. I tried to analyze the drive using
diskeeper, but it would just hang. Also my drive was making really
weird noises like it was stuck.

Those are called "recalibrations"--the drive is readjusting itself in an
effort to read a damaged sector.

So I restart my comp run check disk
and the following happens. This is a very long log, but most of it is
bullshit. Btw I use Bit torent a lot. I thought I should tell you guys
that because someone told me it really messes up your HD

*********************************************************************
Checking file system on D:
The type of the file system is FAT32.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
Volume Serial Number is 1B32-10D2
The \pagefile.sys entry contains a nonvalid link.
Read failure with status 0xc000009c at offset 0x9e7fbc000 for 0x10000

Bad sectors found.
Free space verification is complete.
Windows has made corrections to the file system.
74041504 KB total disk space.
585824 KB in 1122 hidden files.
130176 KB in 4062 folders.
63662464 KB in 49513 files.
1376 KB in bad sectors.
9661632 KB are available.

32768 bytes in each allocation unit.
2313797 total allocation units on disk.
301926 allocation units available on disk.
*********************************************************************
So here are my questions:
Has downloading shit loads of stuff of bit torrent made my HD worse?

No. Continuing to use a damaged disk has made it worse.

Where are these bad sectors? Are they near the boot? If so am I
****ed?

Doesn't matter where they are, you're ****ed regardless. You've already
gotten error messages during boot--that should answer your question. Even
if you didn't get such messages, wait a while and you would.

Do I need to replace this HD?
Yes.

Or can I fix this problem, by re formatting my drive/re-install OS?
No.

Why is this happening? Is it physically my hard disk or my bad
management of software?

There is a technical term which is used to describe the state of your disk.
That term is "busted".

Btw I would like to say I don't really care about losing the 1.3mb,
but I just want to be sure my HD won't die on me and carry on getting
worse.

You may be sure that it _will_ die on you very soon if it has not already
done so.

I have so much important stuff on my comp and I can't risk losing it.

Then remove that disk, put in another one, install the OS, get it set up,
_then_ put that disk back in and copy as much as you can. Until you are
ready to copy data, do _not_ run that disk anymore, every rotation likely
does more damage.

I would to thank you in advance for any help you can give me, also i
am sorry if some of the stuff i have said is Amateurish, but i know
very little about this sort of thing.

Learn about RAID and backups.

 

[James Andrus]

At that point you had good notice that your drive was going to die. When
any modern drive reports that many bad sectors that means that it's very
likely used up its hot-spare space already with bad sectors that you never
see. When that happens things are just gong to get worse.

What is hot spare space? Are these 'bad sectors that you never see' ones
that developed in use (as opposed to ones marked out on low level format at
the factory), and if so, are they really invisible to things like scandisk
(W98)?

It is really fascinating to learn this. At the same time, this is not very
efficient, picking up these tidbits one at a time. Can anyone recommend any
good books on modern hard drives that get to this level?

Thanks.

Jim Andrus

 

[Rod Speed]

What is hot spare space?

Basically a set of spare sectors available for
the drive to use to replace sectors that go bad.

Are these 'bad sectors that you never
see' ones that developed in use

In theory. In practice that doesnt happen
much except when a drive is dying.

(as opposed to ones marked out on low level
format at the factory), and if so, are they really
invisible to things like scandisk (W98)?

Yes. The only thing scandisk shows are
clusters marked bad at the OS level.

It is really fascinating to learn this. At the same time, this is not very
efficient, picking up these tidbits one at a time. Can anyone recommend
any good books on modern hard drives that get to this level?

There's plenty of stuff online.

 

[kaz]

Thanks for your help guys.
Btw I am thinking of buying this HD. I was wondering what you think of
it.
http://www.ebuyer.com/customer/prod...WN0X3Byb2R1Y3Rfb3ZlcnZpZXc=&product_uid=57114
Also is it a good idea to not through my old drive away and keep it on
the side, so I can keep movies on it?
Also I was wondering if there is a way of backing up all the critical
window updates. So I can re-install them on my new HD.
My last question. Is it a good idea to backup all my registry settings
and transfer them over to my new HD or is it good to start of clean
and make sure to bad data can get transferred over. Because my problem
is I would like my new HD to have the same settings/look has my first
one, but I am worried in doing so, I might transfer some of the bad
data.

 

[Folkert Rienstra]

Hi,
My comp:
win xp all updates
athlon 2000xp
HD= http://www.seagate.com/cda/products/discsales/marketing/detail/0,1081,381,00.html

A few weeks ago I realized that I had 128KB of bad sector.

Of bad clusters or more to the point:
128kB of clusters with some bad sectors in them.

Then for the past few days my comp has been crashing. Once it crashed
and I restart the pc and I get a message saying the registry had to be
recovered. Then my comp was running really slow. Hanging whenever I
was trying to access the HD. I tried to analyze the drive using
diskeeper, but it would just hang. Also my drive was making really
weird noises like it was stuck.

All signs of read errors occuring.

So I restart my comp run check disk and the following happens. This is a very
long log, but most of it is bullshit. Btw I use Bit torent a lot. I thought I should
tell you guys that because someone told me it really messes up your HD

*********************************************************************
Checking file system on D:
The type of the file system is FAT32.


One of your disks needs to be checked for consistency. You may cancel
the disk check, but it is strongly recommended that you continue.
Windows will now check the disk.
Volume Serial Number is 1B32-10D2
The \pagefile.sys entry contains a nonvalid link.

Read failure with status 0xc000009c at offset 0x9e7fbc000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x9e7fbc000 for 0x8000 bytes.

1 cluster
(NB, 0x8000 = 32768 = 1 cluster, 0x10000 = 65536 = 2 clusters)

Read failure with status 0xc000009c at offset 0x9e8034000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x9e83b4000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x9e8994000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x9e8a6c000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x9e8acc000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x9e8b2c000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x9e8c3c000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x9e8eec000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x9e8f4c000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x9f0734000 for 0x8000 bytes.

Windows replaced bad clusters in file \pagefile.sys of name (null).
The size of the \pagefile.sys entry is not valid.

11 clusters sofar

Read failure with status 0xc000009c at offset 0xb43954000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0xb43954000 for 0x8000 bytes.

Folder \j2sdk1.4.0_03\docs\api\javax\imageio\plugins is entirely unreadable.
Folder entry removed.
12

Read failure with status 0xc000009c at offset 0xb30144000 for 0x8000 bytes.

Read failure with status 0xc000009c at offset 0xb2adc4000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0xb2adc4000 for 0x8000 bytes.

Folder \j2sdk1.4.0_03\docs\api\java\awt\event is entirely unreadable.
Folder entry removed.
14

Read failure with status 0xc000009c at offset 0x30808c000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x30808c000 for 0x8000 bytes.

Windows replaced bad clusters in file \Program Files\Common Files\Symantec Shared\CommonClient.dat of name (null).
15

Read failure with status 0xc000009c at offset 0x4046cc000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x4046cc000 for 0x8000 bytes.

Windows replaced bad clusters in file \Documents and Settings\Kaz\Local Settings\Temporary Internet
Files\Content.IE5\GK2ZTU42\js[13] of name (null).
16

Read failure with status 0xc000009c at offset 0x403e04000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x403e04000 for 0x8000 bytes.

Windows replaced bad clusters in file \Documents and Settings\Kaz\Local Settings\Temporary Internet
Files\Content.IE5\CTQ74DEJ\home[1].htm of name (null).
17

Read failure with status 0xc000009c at offset 0x404584000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x404584000 for 0x8000 bytes.

Windows replaced bad clusters in file \Documents and Settings\Kaz\Local Settings\Temporary Internet
Files\Content.IE5\CTQ74DEJ\hNavCats[1].gif of name (null).
18

Read failure with status 0xc000009c at offset 0x404564000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x404564000 for 0x8000 bytes.

Windows replaced bad clusters in file \Documents and Settings\Kaz\Local Settings\Temporary Internet
Files\Content.IE5\22EVXMY0\js[28] of name (null).
19

Read failure with status 0xc000009c at offset 0x4045dc000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x4045dc000 for 0x8000 bytes.

Windows replaced bad clusters in file \Documents and Settings\Kaz\Local Settings\Temporary Internet
Files\Content.IE5\22EVXMY0\p0059144_c0000020_p0000000[1].jpg of name (null).
20

Read failure with status 0xc000009c at offset 0x40465c000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x40465c000 for 0x8000 bytes.

Windows replaced bad clusters in file \Documents and Settings\Kaz\Local Settings\Temporary Internet
Files\Content.IE5\22EVXMY0\amazing_deals[1].gif of name (null).
21

Read failure with status 0xc000009c at offset 0x4045cc000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x4045cc000 for 0x8000 bytes.

Windows replaced bad clusters in file \Documents and Settings\Kaz\Local Settings\Temporary Internet
Files\Content.IE5\KVPRIUN5\p0034833_c0000007_p0000000[1].jpg of name (null).
22

Read failure with status 0xc000009c at offset 0x4045ec000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x4045ec000 for 0x8000 bytes.

Windows replaced bad clusters in file \Documents and Settings\Kaz \Local Settings\Temporary Internet
Files\Content.IE5\4T6RCTMV\p0059308_c0000042_p0000000[1].jpg of name (null).
23

Read failure with status 0xc000009c at offset 0x40457c000 for 0x8000 bytes.
Read failure with status 0xc000009c at offset 0x40457c000 for 0x8000 bytes.

Windows replaced bad clusters in file \Documents and Settings\Kaz\Local Settings\Temporary Internet
Files\Content.IE5\WNGHAZY5\cart[1].gif of name (null).
24

The size of the \WINDOWS\Internet Logs\STUEF1C.ldb entry is not valid.
\WINDOWS\Prefetch\NUCD.EXE-02CB91BF.pf first allocation unit is not valid.
The entry will be truncated.

Bad links in lost chain at cluster 458260 corrected.
Bad links in lost chain at cluster 458774 corrected.
Bad links in lost chain at cluster 458780 corrected.
Bad links in lost chain at cluster 459073 corrected.
Bad links in lost chain at cluster 459560 corrected.
Bad links in lost chain at cluster 1249915 corrected.
Bad links in lost chain at cluster 1251689 corrected.
Convert lost chains to files (Y/N)? Yes
191232 KB in 124 recovered files.

Windows is verifying free space...
Read failure with status 0xc000009c at offset 0xa6f8 44000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xa6f8 54000 for 0x10000 bytes.

26 (possibly neighbouring clusters?)

Read failure with status 0xc000009c at offset 0xa6f894000 for 0x10000 bytes.
27

Read failure with status 0xc000009c at offset 0xa6f984000 for 0x10000 bytes.
28

Read failure with status 0xc000009c at offset 0xa6f994000 for 0x10000 bytes.
29

Read failure with status 0xc000009c at offset 0xa6fa74000 for 0x10000 bytes.
30

Read failure with status 0xc000009c at offset 0xa6f8 44000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xa6f8 54000 for 0x10000 bytes.

32 (possibly neighbouring clusters?)

Read failure with status 0xc000009c at offset 0xa6f894000 for 0x10000 bytes.
33

Read failure with status 0xc000009c at offset 0xa6f9 84000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xa6f9 94000 for 0x10000 bytes.

35 (possibly neighbouring clusters?)

Read failure with status 0xc000009c at offset 0xa6fa74000 for 0x10000 bytes.
36

Read failure with status 0xc000009c at offset 0xa6f8 44000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xa6f8 54000 for 0x10000 bytes.

38 (possibly neighbouring clusters?)

Read failure with status 0xc000009c at offset 0xa6f894000 for 0x10000 bytes.
39

Read failure with status 0xc000009c at offset 0xa6f9 84000 for 0x10000 bytes.

40 clusters.
The missing 3 clusters (see 43 below) may be hidden in the 4 incidents of possibly neighbouring clusters.

Bad sectors found.
Free space verification is complete.
Windows has made corrections to the file system.

74041504 KB total disk space.

80 GB or 148,083,008 or so sectors.

585824 KB in 1122 hidden files.
130176 KB in 4062 folders.
63662464 KB in 49513 files.

1376 KB in bad sectors.

With 32KB clusters that is a whopping 43 (!) out of 148,083,008 or so sectors.

IE .0003 percent of the drive

Of course that is a minimum -and it could be a few times that- but then you would
likely see neighbouring clusters, as neighbouring bad sectors don't know about
cluster bounderies.
Nonetheless there will likely be some clusters with more than one bad sector in them.

9661632 KB are available.

32768 bytes in each allocation unit.

I.E. 32 kB clusters.

2313797 total allocation units on disk.
301926 allocation units available on disk.
*********************************************************************
So here are my questions:

Has downloading shit loads of stuff of "bit torrent" made my HD worse?

Perhaps, perhaps not.

Where are these bad sectors?

roughly in 5 places

0x30808c000 13,019,693,056 bytes
0x403e04000 ...
0x9e7fbc000 ...
0xa6f844000 ...
0xb2adc4000 47,963,717,632 bytes

into the drive.

Are they near the boot? If so am I ****ed?

Doesn't matter.

Do I need to replace this HD?

Maybe, maybe not. Depends on whether causes are internal or external.

Or can I fix this problem, by re-formatting my drive/re-install OS?

No. The only things fixable are external causes like drive temperature or
power supply problems. Once they are fixed running the MFGR diagnostic
may fix the bad sectors (or anything else that writes to the bad sectors)
and return the drive to normal again.

Why is this happening?

Can be from external causes.

Is it physically my hard disk

Possibly that or external causes.

or my bad management of software?
Nope.


Btw I would like to say I don't really care about losing the 1.3mb,

It's probably only 43 sectors.

but I just want to be sure my HD won't die on me and carry on getting
worse.

Then check drive temperature and Powersupply/supply_of_power.

 

[S.Heenan]

Thanks for your help guys.
Btw I am thinking of buying this HD. I was wondering what you think of
it.

http://www.ebuyer.com/customer/prod...WN0X3Byb2R1Y3Rfb3ZlcnZpZXc=&product_uid=57114

Never heard of that brand.Ebuyer has Maxtor and Seagate 80GB 7200RPM 8MB
cache drivers for less than £39. The Barracuda IV is a very quiet drive.

Also is it a good idea to not through my old drive away and keep it on
the side, so I can keep movies on it?

FFS. Don't use your existing drive. Every second you use it. you damage
more data. After you've installed a new hard drive, connect the old one as a
slave and transfer what data you can. You *do not* need to transfer OS files
or hotfixes.

Once your data is off, either RMA the drive or keep it as a paper weight. It
isn't good for much else.

 

[Folkert Rienstra]

That the possibility of it dying was there.

Not necessarily. Power Supply problems may show in this way too.

Correct, except that you don't really know that it has.
Only when "bad sectors" refuse to go away after they have been overwritten
is it likely that the drive is_dying/has_died.

Uncorrectable read error bad sectors will always show, whether spares are
available or not. The difference is whether they can be made to disappear
again (or not).

What is hot spare space?

Sectors at end of drive that are on standby for when a sector that passes
a certain limit on read retries is found and then will replace that sector
and take its address while data is copied to it. Same will happen when the
bad sector is written to and the drive knows that the previous data was
unrecoverable. The data is written to the replacement sector instead.

Are these 'bad sectors that you never see' ones that developed in use
(as opposed to ones marked out on low level format at the factory),

Very similar.

and if so, are they really invisible to things like scandisk (W98)?

Yup, should be.

It is really fascinating to learn this. At the same time, this is not very
efficient, picking up these tidbits one at a time. Can anyone recommend any
good books on modern hard drives that get to this level?

Just google for "comp.sys.ibm.pc.hardware.storage" and "bad sector".
Or read your drive manual.

 

[Folkert Rienstra]

Thanks for your help guys.
Btw I am thinking of buying this HD. I was wondering what you think of it.
http://www.ebuyer.com/customer/prod...WN0X3Byb2R1Y3Rfb3ZlcnZpZXc=&product_uid=57114
Also is it a good idea to not throw my old drive away and keep it on
the side, so I can keep movies on it?
Also I was wondering if there is a way of backing up all the critical
window updates. So I can re-install them on my new HD.

Aren't they cumulative (including all previous) updates these days?
Anyway, you can probably find the .exe(s) or cabinets in your browser
cache afterwards and save those to a directory of choice.

My last question. Is it a good idea to backup all my registry settings
and transfer them over to my new HD or is it good to start of clean
and make sure to bad data can get transferred over. Because my problem
is I would like my new HD to have the same settings/look has my first one,

but I am worried in doing so, I might transfer some of the bad data.

That's not possible. The data is either good or unavailable.

 

[Rod Speed]

Only if you dont care about losing those movies.

Aren't they cumulative (including all previous) updates these days?
Nope.

Anyway, you can probably find the .exe(s) or cabinets in your browser
cache afterwards and save those to a directory of choice.
Nope.

That's not possible. The data is either good or unavailable.

Wrong. As always.