DiskSalvor › Help

How a drive connects, and why it matters

How drives work · Why the same disk behaves differently in different USB enclosures, and what bridges and card readers mean for recovering data.

ComputerWindows SATAcable inside a PC → HDD or SATA SSD speaks ATA directly PCIeM.2 slot → NVMe SSD speaks NVMe directly USB port bridge chiptranslates USB ↔ SATA/NVMe drive S.M.A.R.T. passes onlyif the bridge allows it A card reader works the same way: its own little controller sits between USB and the card.

SATA and NVMe drives talk to Windows directly. A USB drive talks through a bridge chip that converts USB commands into the drive's own language. Bridges are why the same disk can behave differently in different enclosures: some hide the health log, some time out and reset the connection when the disk struggles, and some encrypt everything (see Encryption).

LinkNotes for recovery
SATA (inside a PC, or a SATA dock)Most direct and predictable. The best way to connect a failing hard disk, if you can get it out of its case (unless its bridge encrypts it).
NVMe / PCIeVery fast; health log always available.
USB, BOT modeOlder, simpler protocol. Slower, but tolerant of slow drives.
USB, UAS modeFaster, queues commands, can pass TRIM. Some bridges reset the whole connection when a failing drive stalls.
Card readerThe reader has its own controller. An empty slot still shows a drive letter with no size. Readers rarely pass TRIM.
Hubs, docks, front-panel portsAdd another chip and weaker power. Plug a fragile drive straight into the computer.
← PreviousKinds of drivesNext →Inside: platters vs flash

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.

Start here if your drive is failing

How drives work

Reference