What I mentioned as "bad sectors" here are quoted from following scan/test:
- result from CHKDSK, referred as "Bad Sectors" on the report screen.
- result from HD Tune - Error Scan, referred as "Damaged Blocks" or red square.
I have an internal HDD that has been successfully recovered from bad sectors by performing a full erase on whole sectors at that disk. (After an erase, running surface test told that all sector are OK, I don't see bad sectors anymore).
After that I encountered BSOD. After restart, I do the surface scan again, but this time 1 bad sector is found. I tried to erase it again, then running surface test told that the bad sector went away (again).
I already heard several times that sudden power-off or any power-related problem can break your hard drive. But can BSOD cause bad sectors, too? Or does this mean that my drive is already falling and need to be replaced? FYI, the S.M.A.R.T status from HD Tune is still "OK".
Since BSOD is quite common to occur (on my case, for every 3-6 months), I found it's annoying if after that I should repeat the "rescan the disk, erase, and restore" cycle.
EDIT:
In reply to all comments & answers here
I found many article explaining that bad sectors aren't always physical reason. There is also logical reason (e.g. the CRC for that block does not match the data read back by the disk).
A logical — or soft — bad sector is a cluster of storage on the hard
drive that appears to not be working properly. The operating system
may have tried to read data on the hard drive from this sector and
found that the error-correcting code (ECC) didn’t match the contents
of the sector, which suggests that something is wrong. These may be
marked as bad sectors, but can be repaired by overwriting the drive
with zeros
Since there are too many, instead of copy the content, I will just put the link here:
No comments:
Post a Comment