Archived from groups: comp.sys.laptops (
More info?)
Note that what he probably has is ONE SINGLE bad sector, but because DOS
and Windows both deal in "clusters", the entire cluster containing that
sector has to be marked bad -- not just the single bad sector.
Still, this is odd in an IDE drive. Normally, IDE drives handle bad
sectors internally (within the drive), and the operating system never
sees any bad sectors at all until there are an overwhelming number of
them. When a bad sector is found, it is marked bad (internally) by the
drive, which then semi-permanently substitues a "spare" sector (of which
thousands exist) for the bad sector. The operating system, DOS,
Windows, whatever, never knows that any of this has happened, and
doesn't report any errors at all. The only time you find out that
something is wrong is when you get a "S.M.A.R.T." message or when the
drive runs out of "spare" sectors (or when you try to read a sector that
the drive had thought was good)..
Chris Hill wrote:
> On 22 Jun 2004 20:19:47 -0700, myfiles3000@hotmail.com (willem) wrote:
>
>
>>Hello,
>>
>>The past week has been very frustrating. I had been experiencing
>>problems with what looked like a Sasser infection, and eventually
>>decided to re-format the Toshiba drive I purchased around 3 months
>>ago. Hated to do it, but enough was enough.
>>
>>While things have improved, chkdsk now shows "4kb in bad sectors" (see
>>bottom for .log). And there is this strange noise that occurs,
>>particularly boot up (Win XP Pro), which, if you'll allow me to render
>>in visual form with the help of Extended ASCII, sounds like:
>>
>>Chi-Chi-Chi-
>>CHIT CHIT
>>Chi-Chi-Chi-
>>
>>[pause of a second or so, then repeats...}
>>
>>Chi-Chi-Chi-
>>CHIT CHIT
>>Chi-Chi-Chi-
>>
>>This sound always occurs in the same "batch pattern" above, and
>>sometimes repeats a second time. I'm pretty annoyed as the drive is
>>barely 3 months, and I've lost all my data thanks to the reformatting.
>>I've run chkdsk /f and /r, and I've also run the scan disk function in
>>norton system works to no avail. Is it fair to say that the computer
>>has failed to move the 4 kb from the bad sectors? Is there anything
>>else I can do to repair? Should I replace the drive even if I can't
>>get my money back on the one I have now? Finally, is it possible one
>>of the variants of Sasser or Blaster caused the drive damage?
>
>
> Not likely software causing the problem. I'd return the drive. If
> you are seeing bad sectors, the drive is out of spares, that tells me
> the drive isn't healthy.