09-07-2018 12:17 PM
After switching off my desktop computer which was in sleep mode at the time, I can no longer access the 512GB MX200 main drive.
Booting up the computer gives me a Boot BCD error:
An unexpected I/O error has occured.
The BIOS still sees the drive, but I tried running the Windows recovery tools on that computer, and they cannot access the drive. Nor can Windows access the disk in an external USB enclosure.
I now have the SSD plugged into another computer (via SATA) and while Windows 10 can see the drive, it cannot see any of the contents. The Disk Utilities recognizes it as having a RAW partition, but none of the Windows 10 tools or the Easeus tools can recover the partition or the data on that drive.
I don't know at this stage if the drive itself is salvagable because I don't want do anything to irrevocably delete my data, but is there anything else I can try? Any tools or processes left that might be able to access the data, at the very least? I haven't tried using Linux yet, but that's all I can think of.
Any assistance gratefully accepted.
09-08-2018 02:49 PM
If you really need to recover the data from the SSD, I would suggest using a professional data recovery service such as Drive Savers. They provide free estimates and you only pay if they are succcessful at recovering data, plus most manufacturers will still honor the warranty on a drive. The more you use a possibly failing drive the harder & more expensive it will be to recover data. I haven't had enough first hand experience with failing SSDs to truly understand how they fail or what is possible with off the shelf recovery tools.
If you don't want to use a professional data recovery service, then Linux is definitely your best chance at understanding the issue and recovering your data. If you do not have Linux installed on a system, then I recommend using Knoppix and "burning" it to a USB drive with Etcher.
The first thing I would do is use GNU ddrescue to clone the SSD to another drive or image file (make sure to use the logging feature so you can resume the clone if necessary). Then you can use other tools such as "testdisk" to fix the filesystem on the image or cloned drive leaving the source as intact as possible.
You may want to post the SMART Attributes for the SSD. You should check the Linux log files to check on communication with your SSD and any possible errors as that might assist in understanding what is happening to the SSD. Connecting the SSD with USB after Linux boots makes it easier to read the log entries for the SSD as they will be at the end of the log.
If you need assistance doing any of this let me know and I will provide some instructions.
Good luck and please let us know how you make out.
09-09-2018 12:47 PM
Thank you so much for the pointers you gave, HWTech. Much appreciated!
Regarding professional data recovery, fortunately, I do keep backups of the most critical files, so that won't be necessary. What I didn't have (to my regret) is a full backup of the drive, and I am hoping to avoid the pain of having to rebuild my main desktop system, which included my main development environment. Lesson learned, I guess
Thanks for the information on using Linux to probe the drive. I know it's probably a lost cause at this stage, but I do want to exhaust all the possibilities before biting the bullet and reinstalling. I'll have a go and let you know what happens.
The firmware level is one behind, but looking at the MU05 information, it doesn't look as though upgrading will help. I will do it anyway, if the Linux based recovery fails.
Finally, here are the SMART values of the drive, as read by Crucial's Storage Executive, below. The "Retired NAND Blocks" value has exceeded the threshold, which I'm guessing isn't a good sign, though it's showing zero?
|5||Retired NAND Blocks|
|1||Raw Read Error Rate||119||Errors/Page|
|5||Retired NAND Blocks||0||NAND Blocks|
|9||Power On Hours Count||3929||Hours|
|12||Power Cycle Count||1581||Cycles|
|171||Program Fail Count||0||NAND Page Program Failures|
|172||Erase Fail Count||0||NAND Block Erase Failures|
|173||Average Block-Erase Count||76||Erases|
|174||Unexpected Power Loss Count||122||Unexpected Power Loss events|
|180||Unused reserved block count||5578||Blocks|
|183||SATA Interface Downshift||0||Downshifts|
|184||Error Correction Count||0||Correction Events|
|187||Reported Uncorrectable Errors||0||ECC Correction Failures|
|194||Enclosure Temperature||35||Current Temperature (C)|
|55||Highest Lifetime Temperature (C)|
|196||Reallocation Event Count||0||Events|
|197||Current Pending Sector Count||0||512 Byte Sectors|
|198||SMART Off-line Scan Uncorrectable Errors||0||Errors|
|199||Ultra-DMA CRC Error Count||12||Errors|
|202||Percentage Lifetime Used||3||% Lifetime Used|
|206||Write Error Rate||0||Program Fails/MB|
|210||RAIN Successful Recovery Page Count||0||TUs successfully recovered by RAIN|
|246||Cumulative Host Write Sector Count||26620582142||512 Byte Sectors|
|247||Host Program Page Count||834538072||NAND Page|
|248||FTL Program Page Count||835447807||NAND Page|
09-09-2018 05:39 PM
Update: I'm using the System Rescue Live CD version of Linux, and the disktest tool finds the missing partitions no problem at all. I'm in the process of finding enough free space to back up the partition before making an attempt to fix the MBR, but at the very least it looks as though all the files are recoverable. Woohoo!
09-09-2018 06:37 PM
Good to hear!
The SMART status error doesn't really match up with the reported SMART attributes since you still have most of your Reserved Blocks still available. After retrieving your data and updating the firmware on the SSD, I would suggest you perform a Secure Erase to reset the SSD. I have resolved some SSD issues this way. Then run some tests on it and recheck the SMART attributes & status. Hopefully you will be able to continue using the SSD.
Please keep us updated.
09-10-2018 06:42 PM - edited 09-12-2018 10:27 PM
Well, I guess I may have missed my chance at reviving the drive. After a long time powered on yesterday, I could no longer read anything from it reliably, so turned off for the night. Today, it was reliably readable again (via Linux only) but the Crucial utilities can no longer see the drive, and there are errors when running parted, gparted, etc.
I've tried various tools (parted, testdisk, fdisk, gdisk, sfdisk, hdparm) to delete the partitions, some giving errors, others claiming success, but upon reboot, everything is still as it was. Nothing's changed -- as though the drive is in read-only mode. Windows still sees it as a RAW partition, but can't do anything with it.
I haven't tried diskpart under Windows 10 yet -- will try again after leaving it powered off for a while -- but not hopeful at this stage. Unless something changes tomorrow, or there is a lowlevel tool that can force a full reset I don't know about, I guess I'm looking at an RMA.
Edit: Diskpart doesn't work either, even though it reports the disk as not read-only. I think the drive is well and truly toast.
Further Edit: No joy. Crucial's Storage Executive managed to see the drive today. Performed a "Sanitize Drive" on it, but it's still running several hours later.
Thanks for the assistance, but methinks the drive is kaput. I have a Crucial m4 drive that died after an unexpected power loss, only to revive almost a year later after a final power cycling attempt before RMAing, but I fear this one is headed back to the factory for a replacement.