|
Post by stormymondays on Dec 16, 2020 6:53:04 GMT -6
I’ll spare you the details - but it wasn’t me I have an SSD drive that someone just hit “format” by mistake. The data was also freshly recorded yesterday. I’m on a Mac. Do you guys have some good software that you can personally recommend? Not all is lost, I can probably reconstruct the data I need by piecing together various sources. But it would be great to simply “unformat” it.
|
|
|
Post by svart on Dec 16, 2020 8:20:53 GMT -6
I looked for a few minutes and the consensus seems to be that the wear leveling firmware will immediately start to erase blocks of data.
This is opposite to what I believed they would do for wear on the cells.
Unfortunately, Ssd's don't seem to be recoverable.
|
|
|
Post by stormymondays on Dec 16, 2020 8:29:02 GMT -6
I was fearing exactly that. Thanks for the investigation.
I also have an SD card to recover that might help me.
|
|
|
Post by Ward on Dec 16, 2020 11:47:26 GMT -6
Good news: Not everything is erased in a formatting . . . Bad news: The directory is, which means all data is inaccessible.
|
|
|
Post by svart on Dec 16, 2020 13:24:37 GMT -6
Good news: Not everything is erased in a formatting . . . Bad news: The directory is, which means all data is inaccessible. Usually true for spinning drives, but not true for SSDs from what I've read today.
|
|
|
Post by Ward on Dec 16, 2020 13:29:36 GMT -6
Good news: Not everything is erased in a formatting . . . Bad news: The directory is, which means all data is inaccessible. Usually true for spinning drives, but not true for SSDs from what I've read today. They would do that, wouldn't they? Make things more tangly.
|
|
|
Post by svart on Dec 16, 2020 14:40:19 GMT -6
Usually true for spinning drives, but not true for SSDs from what I've read today. They would do that, wouldn't they? Make things more tangly. It's all about balancing cell wear. Historically hdds would write in areas closer together on the physical disc so that seek times were lower. In Ssd's there is no physical seeking, but you don't want to write in specific areas more than others, so the controllers randomize where things are written. So when you delete/format, the randomization makes it impossible to piece together anything once the locations are lost.
|
|
|
Post by BenjaminAshlin on Dec 17, 2020 1:56:19 GMT -6
They would do that, wouldn't they? Make things more tangly. It's all about balancing cell wear. Historically hdds would write in areas closer together on the physical disc so that seek times were lower. In Ssd's there is no physical seeking, but you don't want to write in specific areas more than others, so the controllers randomize where things are written. So when you delete/format, the randomization makes it impossible to piece together anything once the locations are lost. Unfortunately this is true with SSDs. HDD you could often just reconstruct the partition table pretty quickly.
|
|
|
Post by mrholmes on Dec 17, 2020 22:23:27 GMT -6
That’s why I love time machine I could recover my bookkeeping from 2001🙏🙏🙏🙏
|
|
|
Post by stormymondays on Dec 18, 2020 0:56:49 GMT -6
It seems I’ll be able to recover the SSD after all, I’ll keep you posted.
|
|
|
Post by stormymondays on Dec 18, 2020 16:53:55 GMT -6
Good news. After trying 4-5 programs, Disk Drill recovered the files on the SSD with a very high rate of success. It’s also decently priced. So if anyone finds this thread in the future, give it a try. It took around 5 hours to scan the full 1TB SSD disk. The scan can be paused, saved and resumed which is nice. Then a couple hours for the restore.
As for the SD cards, the Sandisk software did a perfect job. The software is clunky but it works. First I created an image out of the cards, then run the recovery on the images saved to my hard drive.
|
|
|
Post by EmRR on Dec 18, 2020 17:28:07 GMT -6
Fantastic!
One random Mac SSD observation recently, haven't seen this behavior before. I purged about 50GB of files from a nearly full drive, yet disc utility and 'about this mac' both looked as though I hadn't. 2 days later, it caught up. Something to do with wear leveling schedule? No idea.
|
|