Discussions on using the professional data recovery program R-STUDIO for RAID re-construction, NAS recovery, and recovery of various disk and volume managers: Windows storage spaces, Apple volumes, and Linux Logical Volume Manager.

Firstly, I'm an idiot and don't know what I'm doing. But I have read the help yet it is not matching my experience... and I figure this is because I'm an idiot. And I've been trying to sort this out for weeks, making me feel even more like an idiot.

Something happen and Win 10 swapped drivers to one incompatible with RAID disks. After 5 months of trying to resolve the issue by fixing Windows I gave up and did a fresh install on a new SSD.

Into all this add Seagate drives... 2 x 1Tb and 2 x 3Tb (the damn backup drive) that have either failed or failed on initial testing.

I'm 60% sure they are in the right order. The disks are definitely in same order as they were removed from the stack. If I'm wrong then it is a total invert of the 4.

So I didn't have much choice but to try using the motherboard utility to recreate the RAID. At that point I might have rewritten some tables. I have no idea and would take advice.

Firstly because I'm following the help I have not scanned the disks first. Nor do I have the replacement 3Tb drive to image the disks at this stage. I want to make a virtual raid set and see what the story is.

I think what I might have done wrong is to not scan the drive before trying to create the virtual raid but I see nowhere in the help documents that talks on this topic.

Everything is going fine setting up the RAID 5 virtual disk until I run autodetect. I've created an addition desktop as you can't hide the main program window and run that for up to 3 days. How long is this meant to take? I have reasons to wanta reboot, pesty programs that insist on it.

So if I can just get one thing right... do I have to scan the 4 disk before I start messing with creating the virtual raid?

And with that a software suggestion. I have been known to get up every 2 hours during the night to feed orphan baby fruit bats but I'd prefer if I could select multiple disks and scan them in a batch.

Hi Yani, how did you ever make out with this? I haven't been on this forum much lately or I'd have offered some help.

Auto detect only works in some cases, and from what you're describing I doubt it'll correctly detect the settings. This is a case that'll need some manual expertise. If you haven't solved it yet, please message me and I can hopefully guide you further.

Data-Medics wrote:Hi Yani, how did you ever make out with this? I haven't been on this forum much lately or I'd have offered some help.

Auto detect only works in some cases, and from what you're describing I doubt it'll correctly detect the settings. This is a case that'll need some manual expertise. If you haven't solved it yet, please message me and I can hopefully guide you further.

Jared

It would be very interesting if you try to do that using R-Studio's Internet capabilities.

I would guess that the RAID was re-assembled using the wrong drive order or configuration.

You'll need to connect the drives independently (not as part of a RAID) so you can work with them in R-Studio. Nothing you can do through the RAID card in RAID mode, as it's trying to automatically destripe the data using the wrong config.

As I understand, this is a built-in RAID controller. Somehow the RAID had failed, and you (or the system) created a new one.
You definitely should disassemble the RAID in the RAID controller and create a virtual one in R-Studio out of the drives from that RAID. R-Studio's help: Basic RAID 4 and RAID 5 Operations. RAID Recovery Presentation.