bad sector remaping isn't silent; Clickety Clack, Clunk . . .
Clickety Clack, Clunk . . . . . . . . .
is more like the sound of bad sector remapping
when the drive S.M.A.R.T. system detects one
it goes offline to attempt the remap
WD consumer drives are especially bad for going completely offline into what they call "Deep Cycle Recovery" to attempt to remap the bad sector
and the whole time windows flips out and fills the event viewer with
Disk Error logs of various sorts
ie.
a> The device, \Device\Hardkisk_, has a bad block.
b> The system failed to flush data to the transaction log. Corruption may occur.
c> The driver detected a controller error on \Device\RaidPort0. (or whatever controller)
d> An error was detected on device \Device\Harddisk_\DR_ during a paging operation.
e> Application popup: Windows - Device Timeout : The specified I/O operation on \Device\Harddisk_\DR_ was not completed before the time-out period expired.
etc.
I've never seen a system remap or attempt to remap any bad sector(s) without;
- a soft crash where everything seems frozen for a short period or and extended period of time
or it seems to take forever to load certain user files
or
- a hard crash where a BSOD occurs because the bad sector is in the pagefile or in a locked in use system file, or the MFT etc.
