I’ve been following the LevelOneTechs youtube channel this year and enjoy the content. I’ve recently come upon a problem with very little documented solutions and insight available on the general internet and am hoping to tap the minds at the LevelOneTechs forums.
I’m working on an external SATA SSD for a client (Sandisk Extreme Portable SSD) trying to identify why a spreadsheet file became unusable suddenly. As I dug into the disk more, it seemed like that it may have been corrupted somehow over time as there was a huge discrepancy with the file size and size on disk figures, prompting me to go into data salvaging and recovery mode.
After making several backups of what’s currently available (archive, test and usable copy for client), I’ve been stuck on what should be one of the easiest steps–chkdsk.
After initializing chkdsk (all forms of it) and shortly after 0% runs for a few seconds, "An unspecified error occurred (766f6c756d652e63 470) or (766f6c756d652e63 45d) if I use the plain old chkdsk command.
exFAT 1TB, ShortDST passed, Long generic in progress (approx 10 hours, nearly complete) and drive appears very usable. The original computer this was used on may have had a faulty USB port or USB cable as remoting into it initially kept having the drive screaming at Windows for disconnecting/reconnecting and that Windows found errors on the drive but couldn’t do anything.
Still using the original NVME PCB interface as it seems the drive itself may be glued, but depending on the results of current testing I may try look deeper into removing the drive and using another interface.
Any insight or alternatives to get Chkdsk up and going, or another way to examine the drive itself?