Win10 Lenovo M900 <1 year old
1TB SSD
No signs of issues before one day the computer simply wouldn't boot. I tried updating the BIOS first, just in case, but it had no effect.
I put TestDisk on a USB drive and I ran the deep scan, which took like 4 hours. It showed two NTFS partitions and said "the following partitions can't be recovered"
There weren't any options, except to "Continue" so I pressed Continue with the larger partition highlighted.
I get this screen:
I don't know what I'm supposed to do next. How do I know what letter I'm supposed to put next to each partition?
My hope is to get it to boot once, put in a thumb drive, and transfer off everything I can get. I don't know if this is a realistic goal.
I've ordered a new SSD, but it won't be in for a couple days.
Surprise SSD failure, got "the following partitions can't be recovered"
Forum rules
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
When asking for technical support:
- Search for posts on the same topic before posting a new question.
- Give clear, specific information in the title of your post.
- Include as many details as you can, MOST POSTS WILL GET ONLY ONE OR TWO ANSWERS.
- Post a follow up with a "Thank you" or "This worked!"
- When you learn something, use that knowledge to HELP ANOTHER USER LATER.
Before posting, please read https://www.cgsecurity.org/testdisk.pdf
-
- Posts: 5
- Joined: 10 May 2021, 18:31
-
- Posts: 2735
- Joined: 04 Jan 2019, 09:48
- Location: Hannover, Deutschland (Germany, Allemagne)
Re: Surprise SSD failure, got "the following partitions can't be recovered"
Check each partition for valid content using the "p"-key ("list files").
-
- Posts: 5
- Joined: 10 May 2021, 18:31
Re: Surprise SSD failure, got "the following partitions can't be recovered"
Partitions:
1 - Seems okay, had recycle bin and system volume info
2 - Can't open file system.
3 - Can't open file system.
Partition 4:
Scrolling down showed many more red files.
Partition 5 - Seemed okay, only a few items, recovery and system volume info
6 - Can't open file system.
Partition 7:
Partition 8:
1 - Seems okay, had recycle bin and system volume info
2 - Can't open file system.
3 - Can't open file system.
Partition 4:
Scrolling down showed many more red files.
Partition 5 - Seemed okay, only a few items, recovery and system volume info
6 - Can't open file system.
Partition 7:
Partition 8:
-
- Posts: 5
- Joined: 10 May 2021, 18:31
Re: Surprise SSD failure, got "the following partitions can't be recovered"
Okay, so 3 of those partitions (the ones with screenshots) have bootmgr and bootmgr.efi which I am assuming are needed to try to boot from the drive.
Two more partitions seemed okay.
The rest said Can't open file system.
Assumptions I have:
1 - "Can't open file system." partitions need to keep the D next to their name.
2 - The two mostly empty partitions need to say either L or E. I'm not sure which.
3 - One of the three partitions with bootmgr and bootmgr.efi needs to say *
4 - One of the three partitions with bootmgr and bootmgr.efi needs to say P
5 - One of the three partitions with bootmgr and bootmgr.efi needs to say L or E, I'm not sure which.
Are my assumptions correct, or am I on the wrong track?
Two more partitions seemed okay.
The rest said Can't open file system.
Assumptions I have:
1 - "Can't open file system." partitions need to keep the D next to their name.
2 - The two mostly empty partitions need to say either L or E. I'm not sure which.
3 - One of the three partitions with bootmgr and bootmgr.efi needs to say *
4 - One of the three partitions with bootmgr and bootmgr.efi needs to say P
5 - One of the three partitions with bootmgr and bootmgr.efi needs to say L or E, I'm not sure which.
Are my assumptions correct, or am I on the wrong track?
-
- Posts: 2735
- Joined: 04 Jan 2019, 09:48
- Location: Hannover, Deutschland (Germany, Allemagne)
Re: Surprise SSD failure, got "the following partitions can't be recovered"
Did you find the data that you were missing?
-
- Posts: 5
- Joined: 10 May 2021, 18:31
Re: Surprise SSD failure, got "the following partitions can't be recovered"
Looking inside the partitions that aren't "Can't open file system." I've gone through them, but there doesn't seem to be like any windows file structure.
There was another smaller partition detected on the previous step (when I did the deepscan), but I don't know how to go back to that page and select the other partition without doing a deep scan again. (Takes about 4 hours to deep scan.)
There was another smaller partition detected on the previous step (when I did the deepscan), but I don't know how to go back to that page and select the other partition without doing a deep scan again. (Takes about 4 hours to deep scan.)
-
- Posts: 2735
- Joined: 04 Jan 2019, 09:48
- Location: Hannover, Deutschland (Germany, Allemagne)
Re: Surprise SSD failure, got "the following partitions can't be recovered"
You will have to rerun the deep scan again.
If you don't see the data you expect you are left to use Photorec or any other recovery software.
If you don't see the data you expect you are left to use Photorec or any other recovery software.
-
- Posts: 5
- Joined: 10 May 2021, 18:31
Re: Surprise SSD failure, got "the following partitions can't be recovered"
Running deep scan again didn't help. I'll just accept it as lost. I'm just surprised there were no warnings... no BSoD, no crashes, no weird behaviour at all.
-
- Posts: 2735
- Joined: 04 Jan 2019, 09:48
- Location: Hannover, Deutschland (Germany, Allemagne)
Re: Surprise SSD failure, got "the following partitions can't be recovered"
You could try Photorec or other commercial recovery software.
If you want to prevent failure you have to monitor at least SMART parameters regularly. It seems to me that SDD failures are not preceded by warning signs.
If you want to prevent failure you have to monitor at least SMART parameters regularly. It seems to me that SDD failures are not preceded by warning signs.