JonRussell
New member
No worries. I knew it was a long shot. Just thought someone here would know. Looks like I bricked £600 worth of SSDs ! :-(
-
For $29/mo, we provide access to advanced level technicians who will answer your questions on any Macbook board related matter to the best of their knowledge promptly & walk you through how to solve your problem so you can deliver a working board to your customer.Subscribe Now
Long shot - Help with "frozen" SM0512F SSDs on MBP 2013 ?
- Thread starter JonRussell
- Start date
smiba
New member
Isn't the frozen setting set by using disk encryption? Not sure if all Apple SSDs have these set after using FileVault (Default on pretty much all models with a new version of OS X), might also be enforced by the BIOS.
You might get some luck by using the Parted Magic live CD ($11 one time purchase, $49 year subscription), this is one hell of a live CD bundled with a lot of different tools for HDD/SSD management. You'll use this in the future as well for anything storage related (and its also a really neat linux live ISO which runs 100% from ram after boot).
Booted in Parted Magic, use the "Erase Disk" option under Tools > Erase Disk (iirc), it might be able to unlock the device again and if its not one of the different tools might be of used.
I just find it hard to believe these SSDs are all bricked beyond repair by a simple command, sounds like a disaster waiting to happen!
You might get some luck by using the Parted Magic live CD ($11 one time purchase, $49 year subscription), this is one hell of a live CD bundled with a lot of different tools for HDD/SSD management. You'll use this in the future as well for anything storage related (and its also a really neat linux live ISO which runs 100% from ram after boot).
Booted in Parted Magic, use the "Erase Disk" option under Tools > Erase Disk (iirc), it might be able to unlock the device again and if its not one of the different tools might be of used.
I just find it hard to believe these SSDs are all bricked beyond repair by a simple command, sounds like a disaster waiting to happen!
Last edited: