yesterday 1 drive of my mirror Group in Storage Spaces in windows 10 was damaged. So I disconnected both drives , the damaged one and the good one. After that I deleted the complete pool in the Storage Spaces. But now when I connect again the good working drive , it mentions in disc management 'non allocated space'. The RAID 1 mirror in Storage Spaces has the ReFS filesystem and 1 partition (only one drive letter originaly). what are the steps I need to do in Testdisk to get back the data on the good working drive ? So I want to have the good working drive again normally. So to resume :
- yesterday I disconnected both drives of a mirror in Storage Spaces in Windows 10, because of a damaged drive.
- after that I deleted the group in the Storage Spaces.
- than I connected again the good working drive of the mirror.
- but now I see in disc management : "non allocated space" for the good working drive. I cannot see a drive letter.
There is important data (old photos) on the good working drive, so it's important for me to have him working again. For safety I disconnected both drives for the moment until I find a solution for this.
I have taken a screenshot of the original partitions that testdisk finds, but what do I have to do next ?
How to get back partition and data on disc from Storage Spaces mirror drive
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
How to get back partition and data on disc from Storage Spaces mirror drive
- Attachments
-
- Knipsel.JPG (54.65 KiB) Viewed 5117 times
-
recuperation
- Posts: 3026
- Joined: 04 Jan 2019, 09:48
- Location: Hannover, Deutschland (Germany, Allemagne)
Re: How to get back partition and data on disc from Storage Spaces mirror drive
Dear FSHEHTESI,
thank you for rewriting your past contribution in a readable structured manner and to write "Storage Spaces" instead of "Storgage Spaces". By writing terms correctly other internet users have a chance of finding articles.
Your enclosed picture shows partition table information. Testdisk marked partition number 2 as "Primary MS Storage Spaces".
Some users probably assume now that TestDisk understands what is inside this partition.
This assumption is wrong!
Look at the homepage of CGSecurity:
[...
If you have lost partition or strange problem with your hard disk partitions, run TestDisk to recover your data. TestDisk detects numerous filesystem including NTFS, FAT12, FAT16, FAT32, exFAT, ext2, ext3, ext4, btrfs, BeFS, CramFS, HFS, JFS, Linux Raid, Linux Swap, LVM, LVM2, NSS, ReiserFS, UFS, XFS.
TestDisk can also undelete files from FAT, NTFS, exFAT and ext2 filesystem.
...]
Source:
https://www.cgsecurity.org/
Detecting file systems only means recognizing without necessarily being able to interpret the content inside. This ability is important when it comes to rebuilding a partition table.
Unfortunately that does not mean TestDisk can do things inside of BTRFS, XFS and others, for example. It might recognize Storage Spaces (or it only translates the partition ID into a readable name) but TestDisk has no idea, how data is structured inside.
Therefore, the answer I already gave to you does not change!
viewtopic.php?t=12894
You can always try out PhotoRec as last line of defense as PhotoRec does not need to know the internals of file system organisation.
thank you for rewriting your past contribution in a readable structured manner and to write "Storage Spaces" instead of "Storgage Spaces". By writing terms correctly other internet users have a chance of finding articles.
Your enclosed picture shows partition table information. Testdisk marked partition number 2 as "Primary MS Storage Spaces".
Some users probably assume now that TestDisk understands what is inside this partition.
This assumption is wrong!
Look at the homepage of CGSecurity:
[...
If you have lost partition or strange problem with your hard disk partitions, run TestDisk to recover your data. TestDisk detects numerous filesystem including NTFS, FAT12, FAT16, FAT32, exFAT, ext2, ext3, ext4, btrfs, BeFS, CramFS, HFS, JFS, Linux Raid, Linux Swap, LVM, LVM2, NSS, ReiserFS, UFS, XFS.
TestDisk can also undelete files from FAT, NTFS, exFAT and ext2 filesystem.
...]
Source:
https://www.cgsecurity.org/
Detecting file systems only means recognizing without necessarily being able to interpret the content inside. This ability is important when it comes to rebuilding a partition table.
Unfortunately that does not mean TestDisk can do things inside of BTRFS, XFS and others, for example. It might recognize Storage Spaces (or it only translates the partition ID into a readable name) but TestDisk has no idea, how data is structured inside.
Therefore, the answer I already gave to you does not change!
viewtopic.php?t=12894
You can always try out PhotoRec as last line of defense as PhotoRec does not need to know the internals of file system organisation.