How to know if bad sectors are caused by physical or logical damage?

5,617

The only way I know for something to be marked as a bad sector by the OS when there isn't a physical problem is if something has falsely manipulated the bad block list in the master file table, such as if you directly clone a hard drive that did have bad physical sectors to a new one that does not. A simple byte-for-byte partition copy preserves the same list of bad blocks, even if they aren't bad on the new drive. Another way this can happen is if there is some sort of temporary controller or driver issue fooling the OS into marking a whole bunch of clusters as bad when they really aren't. new drive.

If you think this situation applies to you, and you have a newer version of Windows, chkdsk /b will reevaluate clusters marked as bad. On older versions of Windows this option was not available. There is a way to do this with a Linux boot disk, but it is not nearly as straightforward.

Share:
5,617

Related videos on Youtube

Gabriel
Author by

Gabriel

Updated on September 18, 2022

Comments

  • Gabriel
    Gabriel almost 2 years

    Is it possible to know whether bad sectors are caused by physical damage or logical damage on a hard drive?

    • Daniel B
      Daniel B over 9 years
      How would a bad sector be caused by software?
    • fixer1234
      fixer1234 over 9 years
      Your confusion is now clear. That article appears to be written by someone who knows just enough to be dangerous. Much of the information is either written in a confusing way (probably because the author doesn't understand), or is incorrect. There are basically 2 types of problems, physical inability to store the data, and data corruption. Physically bad sectors are locked out and replaced by spare sectors through logical mapping. Corruption is fixed by rewriting. Humans generally don't deal with the actual sectors. The drive electronics or system utilities fix things appropriately.