Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Please quote the essential parts of the answer from the reference link(s), as the answer can become invalid if the linked page(s) change.
    – DavidPostill
    Commented Mar 9, 2017 at 13:56
  • Ok, will do. Stand by ;) Commented Mar 10, 2017 at 15:21
  • Huge drawback of HD Sentinel for that particular feature: it will actually try to access the defective sectors and display their contents when requested to display which files they belong to. Piriform's Defraggler is excellent for that purpose, in combination with the LBA values of bad sectors provided by HD Sentinel during its scan: point a block on the map and it lists which files are in that area. But the first step should be cloning/imaging, and as Scott Petrack mentioned, it's possible to get a list of files affected by bad sectors by using ddru_ntfsfindbad in combination with ddrescue.
    – GabrielB
    Commented May 23, 2019 at 20:55
  • nfi.exe does not have this issue, it gives its results by analysing the MFT and does not attempt to access the requested sectors, but there seems to be an issue with values beyond 2^31 or 2147483648. superuser.com/questions/1267334/… The native multi-purpose Windows tool fsutil doesn't seem to have that issue, and the output is more streamlined, but it's slower (can be a problem if there are many clusters to request). With nfi use sector numbers, but with fsutil use cluster number.
    – GabrielB
    Commented May 23, 2019 at 21:50