Very slow processing of RAID 10 auto detect?

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.
ckryanco

Very slow processing of RAID 10 auto detect?

Post by ckryanco » Thu Jul 25, 2019 3:26 pm

Hello. First-time R-Studio user here.

I'm trying to recover a RAID 10 array that was working perfectly before I did a BIOS update (at the suggestion of the motherboard tech-support, who did not mention that this would delete the RAID... :oops: )

I've created a Virtual Block RAID & Autodetect, added the four SATA disks, and selected RAID 10 (1.0) as the RAID type, and left everything else as default. This created the 1122 block order shown in the manual.

However, when I click the auto-detect button, it processes data *very* slowly -- it's only some 60MB in, with four 2TB disks. Is this normal?

Also, I see the following items in the log:
ST2000DM006-2DM164 CC26: Basic data partition at 32768 extends beyond disk bounds
ST2000DM006-2DM164 CC26: GPT tables error 0x20304
Virtual Block RAID 1: GPT tables error 0x104

Will these affect data recovery?

Many thanks!

Data-Medics
Posts: 194
Joined: Tue Oct 20, 2015 10:13 am
Location: Providence, RI USA
Contact:

Re: Very slow processing of RAID 10 auto detect?

Post by Data-Medics » Thu Aug 01, 2019 2:15 pm

There's no reason to build it as a RAID 10.

Step 1: open each of the disks in hex and navigate to a random sector somewhere in the middle where there is data (like sector 10,000,000)
Step 2: figure out which drives are the same data as each other so you know which ones are the mirrors
Step 3: use one from each mirror set and assemble a RAID 0

There's no autodetect for RAID 0, but there are only two possible drive rotations and you can quickly cycle through all the possible stripe sizes in a few minutes.

Then, once you find the right config, you just have to check if all the latest data is there. If recent data is corrupt/missing, then you've probably got an out of sync drive that needs to be switched out with its mirror.

Typically takes me 5-10 from start to finish for such cases.

Data-Medics
Posts: 194
Joined: Tue Oct 20, 2015 10:13 am
Location: Providence, RI USA
Contact:

Re: Very slow processing of RAID 10 auto detect?

Post by Data-Medics » Thu Aug 01, 2019 2:17 pm

ckryanco wrote:
Thu Jul 25, 2019 3:26 pm
ST2000DM006-2DM164 CC26: Basic data partition at 32768 extends beyond disk bounds
ST2000DM006-2DM164 CC26: GPT tables error 0x20304
Virtual Block RAID 1: GPT tables error 0x104

Will these affect data recovery?
That's totally normal for a RAID since the partition table should allocate a partition bigger than the size of one disk.

Post Reply