DiskSalvor › Help

The drive's health log (S.M.A.R.T.)

Start here if your drive is failing · What S.M.A.R.T. values like reallocated and pending sectors mean, why a failing drive can still say 'passed', and which numbers matter.

Drives keep their own statistics. DiskSalvor reads them directly (the same way CrystalDiskInfo does): NVMe SSDs always, SATA drives directly, and USB drives when the bridge allows it. Memory cards and most sticks have no health log.

Each item has a count (the real number of events) and a score (the drive's own 1–253 rating; lower is worse). The drive only calls itself "failing" when a score drops to its fail line, which is often too late. The counts are more useful:

Item	Healthy	Meaning when it's above zero
197 Pending sectors	0	Sectors unreadable right now. The key number for recovery: copy first, gently.
198 Uncorrectable (offline)	0	Sectors that failed the drive's own scan.
5 Reallocated sectors	0 (a few can be stable)	Bad spots already swapped for spares. Growing = deteriorating.
187 Reported uncorrectable	0	Reads the drive couldn't correct.
188 Command timeouts	0	The drive stopped answering: weak power, cable, or the drive.
199 Interface CRC errors	0	Transfer errors: almost always the cable, port or USB adapter, not the disk.
10 Spin retries	0	The motor struggled to spin up.
9 Power-on hours, 194 Temperature	–	Age, and heat (above 50–55 °C speeds failure).
NVMe: Percentage used	under 100%	Rated write endurance used up.
NVMe: Available spare / Media errors / Critical warning	high / 0 / none	Spare flash left; unreadable data; serious condition.

Self-tests: the drive can test itself (short ≈ 2 min, extended = the whole surface). Its log of past results is shown too. An extended test on a failing drive takes hours and adds wear, so copy your data first.

Free help for a failing drive

DiskSalvor is free, open-source data recovery for failing drives on Windows. It never writes to the drive, gets the easy files off first, goes back for the rest round by round, and explains what it's doing in plain English. No file limits, no paid edition, no account.

See how it works Follow on GitHub

Start here if your drive is failing

Common situations: what to doDrive asks to be formatted, isn't detected, shows 0 bytes, clicks or is very slow: the most likely cause of each, and what to do first.
Windows pop-ups on a damaged drive: what to clickWhat Windows' format, scan-and-fix and initialize prompts mean on a damaged drive, and which button keeps your files safe.
When the file index is damagedWhy a drive turns RAW after a power cut or unplug, why your files are usually still there, and how they're recovered.
Bad sectors, retries and hangsWhat a bad sector is, why one bad spot can freeze Windows for minutes, and how to read a failing drive without making it worse.
How the safe copy worksWhy copying a failing drive once, easy parts first, protects your files, and how an image lets you recover from the copy instead.
What can be fixed, and whenBoot sector, partition table, file index, bad sectors: what can be repaired, and why repairs should wait until your files are safe.
Deleted, quick-formatted, fully formatted, wipedWhat deleting, quick formatting, full formatting and wiping change on a hard drive, SSD or memory card, and the chances for each.

How drives work

The big picture: a drive is a stack of layersFrom numbered sectors to partitions, file systems and your files: the layers of any drive, and why 'format the disk' usually means one is damaged.
Kinds of drivesWhat's inside each kind of drive, how each usually fails, whether deleted files can come back, and whether it keeps a health log.
How a drive connects, and why it mattersWhy the same disk behaves differently in different USB enclosures, and what bridges and card readers mean for recovering data.
Inside: platters vs flashHow hard disks and flash drives store data, why disk order matters on a hard drive, and why deleted data on an SSD is usually gone.
Sectors, LBAs and clustersThe smallest units a drive and a file system work in: sectors, 512e and 4Kn, logical block addresses and clusters.
Partition tables: MBR and GPTWhat MBR and GPT partition tables hold, which one has a backup copy, and why a USB stick with no partition table is normal.
File systems comparedWhere each file system is used, how it finds files, what safety features it has, and how good the chances of recovery are.
Inside NTFSHow NTFS finds your files through the Master File Table and folder listings, and why files can be recovered when parts of the MFT are lost.
Inside FAT32 and exFATHow FAT32 and exFAT store folders and file chains, what deleting changes, and which deleted files come back whole.
What Windows does when you plug in a driveDrivers, Disk Management, indexing and thumbnails: what Windows does to a drive on its own, and how to stop it straining a failing one.
What has a backup copy, and what doesn'tWhich disk structures have backups (GPT, the NTFS boot sector, the MFT mirror) and which don't, so you know what can be rebuilt.
EncryptionHow BitLocker and enclosure encryption affect recovery, where the keys are, and why some WD drives only read through their own USB bridge.

Reference

Where DiskSalvor fitsHow DiskSalvor reads a drive as raw sectors, layer by layer, without writing to it, even when Windows calls the volume RAW.
GlossaryPlain-English meanings of bridge, carving, CHKDSK, LBA, MFT, RAW, S.M.A.R.T., TRIM and other drive and recovery terms.