View Single Post
  #6   (View Single Post)  
Old 5th May 2022
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
Join Date: May 2008
Location: USA
Posts: 7,723

"Not responding" is not the same as "crashing." And I will guess that your system is not responding because you are having a series of temporary, recoverable read errors. Each of these recoverable read errors follows this basic process:
  1. Drive attempts to read a sector and cannot do so successfully.
  2. Drive waits until the platters rotate the sector by the head again (8.33 milliseconds).
  3. Drive attempts to read the sector and cannot do so successfully
  4. Drive waits until the platters rotate, 8.33 milliseconds again.
  5. Drive attempts to read again.
  6. <repeat dozens or even hundreds of times>
If, eventually, the sector is read successfully, the drive sends the data to the OS, and the failure is considered "temporary and correctable." But it may have taken a very long time to successfully read one sector. Then, repeat this process for the next sector.

When sectors fail, they often do so in groups, as most physical problems that cause sector failure occur over areas that comprise multiple sectors.
Reply With Quote