So to offer a status update:Hardware -
Following the advice of mikewinddale
I replaced the 500GB Samsung 560 EVO with an inexpensive 120GB PNY CS900. I already had a Win10 image thumb-drive on hand, and upon plugging it into my Samsung NP-QX410-JUS, the laptop fired up without hesitation and completed the OS install without any issues, including retrieval of the OS activation key. Big ol' sigh of relief.Software -
In addition to weekly backups utilizing the native (Win7) Windows Backup tool, I also redundantly save really important files to a couple of local external drives, and I've worked OneDrive storage into the mix as well. While I haven't had time to do a comprehensive review yet, it looks like I have most of the really important stuff I don't want to be without. So another pretty big sigh of relief. That said, I still don't have access to a number of easily recognizable files (music downloads, certain images/photos, etc.) that cam hopefully be recovered from backups.Corrupted Drive -
With Win10 freshly installed on a new SSD, I plug the corrupted 850 EVO into one of the ports on my docking station and, as expected, Windows returns the message "You need to format the disk in drive G: before you can use it."
followed by the message "G:\ is not accessible. The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupted."
I clearly don''t want to format the drive just yet as it contains files/data I may still hope to recoverSo ... Questions:
- I'm presuming the EVO 560 can't be considered reliable for anything important. Is it likely the "missing drivers" referenced above are inherent to the EVO's controllers and don't impact upon any of the other laptop's hardware?
- Do Linux distros include a functionality (absent from Windows) that allows a failed drive to be read/diagnosed and, possibly, used for file recovery?
- Are there any (hopefully freeware) Windows applications that can be installed to allow for reading/diagnosing/recovering-data from failed drives?
- After an eventual reformatting attempt on the corrupted EVO 560, is there any reason to expect that it may serve duty in some non-critical storage capacity, or am I better off taking Captain Ned
's advice and going full Ripley on it? And if it's a Ripley, should I take the "Human Ripley" tactic or the "Cross-species Hybridized Ripley" approach?
- Are there system backup applications that are decidedly superior to the Win10 (i.e. Win 7) software native to the OS, and what are your favorite recommendations? (edited to add prev question)
Wrapping up, thanks again to all who helped guide me through this (my most recent) freak-out and return me to the path of being a productive and regular ol' very stable genius. ...