SSD Went from Working to Unbootable to Unreadable
Go to solution
Solved by HD137,
Issue is now, finally, mostly resolved. Drive was successfully (?) cloned while sitting between two bags of ice to keep it cool, but Windows failed to boot when the cloned drive was inserted. Could not repair or restore the install, so performed a fresh install on the new drive. Few other issues I ran into along the way if anyone is reading this for posterity:
- Cloning the drive resulted in a GPT style partition, which meant that Windows couldn't be installed, even after the main partition was formatted. Had to return the drive to out-of-the-box style fully unallocated space, which required using Windows' DISKPART command line utility as the Disk Management utility couldn't delete certain protected partitions that the cloning had created
- Even with fully unallocated space, having another SATA drive (HDD) connected prevented Windows from installing with an unhelpful "Could not install Windows on the selected location" message. Removing the secondary HDD allowed for install.
- Incidental, but with the fresh Windows install, my PCIe Wireless Adapter (TP-Link T6E) wasn't initially recognized. USB tethering to my phone allowed for an internet connection and download of the drivers necessary.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now