Came to issue a friendly warning.
My son's PC had a NVMe WD SN850x 4T upgrade shortly after Christmas 2022.
He recently said his machine has been acting weird, I investigate, and find the drive is having issues and has bad/unrecoverable blocks.
I had happened to buy another exact same drive during the recent Prime Day sale, so I figured we would copy his data over to the new one and RMA the old one.
Tried several different utils to copy the data, but they all kept getting stuck on the bad blocks.
Even tried CloneZilla with various expert mode settings around block mode copy and keep going after bad sectors, etc, still failed.
I saw someone mention ddrescue and figured I would give it a shot.
Found that SytemRescue was bootable and included it, so added it to my Ventoy drive, booted up, mounted one of his other drives for the log, and followed the advice here to run it.
At first it said it would take just over an hour, but once it found some bad blocks, it said 4 hours.
I went to bed.
Woke up this morning to find it was hung and on pass 3, said it had recovered 99.85% of the data, so I was thrilled.
Powered off the machine since it was unresponsive, swapped the drives around, booted, went straight to BIOS.
BIOS Said the M.2 slot was empty.
Shut it down, pulled the drive, put it in my little JMicron USB to NVMe adapter and attached it to my crappy little laptop, Unknown drive, zero bytes.
Swapped back over to his original SN850x, Unknown drive, 0 bytes.
So this process of letting it run overnight to recover the drive, has somehow killed BOTH my source and destination drive.
So I am here to issue this warning, backup anything/everything you can before running this tool.
I am kicking myself for not simply doing a robocopy or similar of as much data as I could off the drive before I started this. (IF you use Robocopy, remember to change the /R and /W settings or it will sit forever on bad files)
I figured with 13 pages in this thread, this tool was safe.
I guessed wrong.