Recover data from "Storage Spaces - Parity"

How to use TestDisk to recover lost partition
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
Locked
Message
Author
Hog79
Posts: 1
Joined: 16 May 2019, 23:12

Recover data from "Storage Spaces - Parity"

#1 Post by Hog79 »

Hi,

I'm using Storage Spaces in Windows 10.
The storage pool is built on 3x 4TB USB drives.
It's configured with a single parity drive.

I was playing around in PowerShell and accidentally messed something up.
My parity drive still exists, but the utilization of the pool is 0%.
The drive is now unformated but partitioned.
(My guess is that it was repartitioned, or something similar)

Any good advice on how to go about this?
Is it possible to restore the partition completely, or at least restore the data itself?

Any help would be much appreciated!

recuperation
Posts: 2720
Joined: 04 Jan 2019, 09:48
Location: Hannover, Deutschland (Germany, Allemagne)

Re: Recover data from "Storage Spaces - Parity"

#2 Post by recuperation »

Hog79 wrote: 16 May 2019, 23:30 Hi,

I'm using Storage Spaces in Windows 10.
The storage pool is built on 3x 4TB USB drives.
It's configured with a single parity drive.

I was playing around in PowerShell and accidentally messed something up.
My parity drive still exists, but the utilization of the pool is 0%.
The drive is now unformated but partitioned.
(My guess is that it was repartitioned, or something similar)

Any good advice on how to go about this?
Is it possible to restore the partition completely, or at least restore the data itself?
Maybe. This question is very strange given the fact that you don't know what you did to your "Storage Space".

You should try out testdisk first.
If testdisk does not show you a way to address your "Storage Space" instead of targetting individual devices you are forced to read out the whole storage space and either write it to a device that is at least 8TB big (my guess: (3-1)x 4TB because of the parity information) or a file that is approx. 8TB big.

Locked