Data Recovery and Disk Utilities Forum @R-TT

Do you have a way to independently connect all the drives (even if it's just one at a time) to make images independent of the RAID controller? Can't really do anything through that PERC controller.

I don't mind doing the case remotely for some beer money if you want to hit me up.

Probably the partition table was on the failed disk. It exists in the first few sectors only so if you lose one of the two disks, there's a 50% chance it's lost.

There is usually a backup copy at the end of the block storage device, so a fair chance there is a copy of the partition table ...

I'm not sure what is with the silly reply above. If you only have one of two disks of a RAID 0 set, you are not going to get a good recovery of any file larger than the stripe size (probably something like 64kb). R-Studio may find the file system Metadata and show you file names and folder structure ...

You need to create a virtual block array, add all the member drives to the array, then configure all the parameters like drive order, stripe size, and parity rotation. You can try auto detect, but very often it requires manual configuring.

Normally you'd want to click the green or blue found partitions. But, it's also very likely that your RAID isn't configured correctly if you are finding a bunch.

What type of RAID was it? Can you post a screenshot of what you are seeing?

What model is the drive? Some newer SMR drives now support T.R.I.M. so even a quick format will result in files that are all zeros.

Edit: just realized this post is a couple of months old.

I created a virtual raid and added the 8 drives.

There's quite a bit more to RAID recovery than just adding the drives. You've also got to figure out drive order, stripe size, party rotation, etc. If one single thing is off, it won't work.

Do you see R-Studio auto-assembling an mdadm RAID down ...

It just means that the partition table, as found and as the RAID is virtually configured, would extend past the end of the array. Typically, this means your array isn't built right.

Your WD Easystore USB adapter is probably encrypting the data. Thow that away and find a way to properly connect the drives, as a start.

Did you scan just the partition or did you scan the whole physical volume? My guess would be you scanned the partition, which caused every found result to have the wrong starting offset. Try going back and scan the actual physical drive, not the logical.