Data Recovery and Disk Utilities Forum @R-TT

I read the manual here:

https://www.r-studio.com/Unformat_Help/ ... raids.html

Step 1 is fine, it creates 'virtual block raid 1'
over in the raid parameters panel the only choice in the dropdown is raid0. Raid5 is grayed out.

Still, I forged ahead and inserted the first hard drive of my 5 drive RAID5 array into a usb dock.
After a little while, I heard the windows sound of a new usb device but nothing showed up under 'device/disk' in R-studio.
I clicked refresh and (not responding) appeared in the title bar of R-studio and after 2 minutes this appeared

ASMT ASM1156-PM 0
HarddiskVolume29
HarddiskVolume30
HarddiskVolume31

I clicked on virtual block raid 1 to get the panel in the right pane.
I dragged HarddiskVolume29 and it appeared
I dragged HarddiskVolume30 and after a delay this appeared in the log:

Severity Type Date Time Message
----------------------------------------------------------------------------------------------------

Error OS I/O error 10/18/2024 7:44:31 PM Sector 0 failed to read from after 2 attempts. Not enough RAID drives to perform I/O
Error OS I/O error 10/18/2024 7:44:31 PM Sector 1 failed to read from after 2 attempts. Not enough RAID drives to perform I/O
Error OS I/O error 10/18/2024 7:44:45 PM Sector 8388607 failed to read from after 2 attempts. Internal error (error #0:0)
Error OS I/O error 10/18/2024 7:44:53 PM Sector 8388600 failed to read from after 2 attempts. Internal error (error #0:0)
Error OS I/O error 10/18/2024 7:44:53 PM Sector 0 failed to read from after 2 attempts. Not enough RAID drives to perform I/O
Error OS I/O error 10/18/2024 7:44:53 PM Sector 1 failed to read from after 2 attempts. Not enough RAID drives to perform I/O
Error OS I/O error 10/18/2024 7:45:01 PM Sector 8388607 failed to read from after 2 attempts. Internal error (error #0:0)
Error OS I/O error 10/18/2024 7:45:09 PM Sector 8388600 failed to read from after 2 attempts. Internal error (error #0:0)

I dragged HarddiskVolume31 and after a delay this also appeared in the log:

Error OS I/O error 10/18/2024 7:48:00 PM Sector 0 failed to read from after 2 attempts. Not enough RAID drives to perform I/O
Error OS I/O error 10/18/2024 7:48:00 PM Sector 1 failed to read from after 2 attempts. Not enough RAID drives to perform I/O
Error OS I/O error 10/18/2024 7:48:14 PM Sector 35134154879 failed to read from after 2 attempts. Internal error (error #0:0)
Error OS I/O error 10/18/2024 7:48:22 PM Sector 35134154872 failed to read from after 2 attempts. Internal error (error #0:0)
Error OS I/O error 10/18/2024 7:48:22 PM Sector 0 failed to read from after 2 attempts. Not enough RAID drives to perform I/O
Error OS I/O error 10/18/2024 7:48:22 PM Sector 1 failed to read from after 2 attempts. Not enough RAID drives to perform I/O
Error OS I/O error 10/18/2024 7:48:30 PM Sector 35134154879 failed to read from after 2 attempts. Internal error (error #0:0)
Error OS I/O error 10/18/2024 7:48:38 PM Sector 35134154872 failed to read from after 2 attempts. Internal error (error #0:0)

Now I CAN change the RAID type to RAID5 in the dropdown.
Am I on the right track? Will I ever be able to see a directory of the files on this array?
Obviously I can keep going, changing the hard drive in the usb dock as I go through my individual drives from my RAID5 array.

However, I would prefer to use images of the volumes (as multiple sources suggest) to prevent data loss from the failing drives.
I select HarddiskVolume29 but the create image button remains grayed out. I tried right clicking and using 'copy' but nothing happens.
how can image this drive?

Also, is there a way to 'save' the virtual block raid 1 object so I dont have to recreate it every time I want to work on this problem?

welll i found out that this drive is actually the bad one in my array. Restarting R studio and reinserting the drive allowed me to create images of each of the three volumes (but for some reason the volume numbers keep incrementing)

I get three files each of which is only 2kb
HarddiskVolume32.rdr
HarddiskVolume33.rdr
HarddiskVolume34.rdr

The actual volumes are much bigger (see attached pic) How can these be images of volumes??

after some reading, I realized that these 2 kb files are aborted attempts at imaging. Obviously the disk could not be read.
I wish there were a way to find out which files the bad sectors belonged to.
I could then ignore those sectors from imaging (possible?)
and know which files are corrupt.