Question Can I fix Highpoint RocketRAID 2320 card's RAID1/0 array that appears to fractured/split ?

[c19]

Have Highpoint RocketRAID 2320 8-Channel PCI-Express x4 SATA 3Gb/s RAID Controller configured with 6 drive RAID1/0 and 1 spare drive and labeled the array "RAID10". It has ran for a year in the current configuration. Now I've had a failure alarm go off with Windows 10 freeze. Event log below:

Upon restart the RAID1/0 array shows up in the cards boot interface and webGUI as two separate RAID1/0 arrays both called "RAID10" ?

Upon further inspection of the arrays, the first/top of the two arrays labeled "RAID10" (call it RAID10 A) shows 2 of the 3 RAID1 mirrored members, members 1 and 2 and the corresponding 2 devices of each present while member 3 shows the spare device there (Device_1_1) with the mirror drive not present as Offline Disk.

The next or bottom entry of "RAID10" (lets call it RAID10 B) shows members 1 and 2 as Offline Array and member 3's corresponding 2 devices present.

So basically upon restart my single RAID1/0 "RAID10" array is split into 2 different arrays both labeled "RAID10" when both devices (7 and 8) of member 3 "failed" at same time, it tried to replace the member with the single spare drive and Windows locked up requiring hard restart. But on restart the two devices 7 and 8 read as ok but are now in a second "RAID10" array. I have tried removing the spare and cycling, but it still shows them and 2 separate RAID10 arrays wherein member 3 of RAID10 A is just Offline Array since spare device_1_1 is unplugged.

Any ideas? Any help is appreciated. Can I get the RAID card to recognize that it is the SAME "RAID10" array and not 2 separate "RAID10" arrays? Is there a way to recover the original RAID1/0 array?
I understand I am limited by my basic knowledge/ignorance and the cards known limited capabilities here (you can see the options from the screenshots and the cards boot interface has even less options accessible than the webGUI). I have reached out to Highpoint but still awaiting a response (the product is no longer on the website or in the pulldown list for support). In before, RAID is not backup and the 2320 is obsolete and fake raid card.
Thank you.

 

[Ralston18]

This:

"In before, RAID is not backup and the 2320 is obsolete and fake raid card."

I understand that the RAID is not intended for or as a backup? Where are your backups located?

Clarify "2320 is obsolete and fake raid card". If the card is obsolete and/or fake then problems will occur.

How full are those drives? I do not understand all of the "Max free" capacities being shown as 0.00 GB.

Lastly, unless you are just experimenting or learning, there is no need for any sort of RAID for most people and computing environments.

Why is RAID being used?

More information needed.

 

[USAFRet]

Is the data still readable in either of the existing "arrays"?

If so, copy it to some other device, rebuild the array if possible...not worrying about what data is on it.

 

[c19]

Is the data still readable in either of the existing "arrays"?

If so, copy it to some other device, rebuild the array if possible...not worrying about what data is on it.

With my tools and knowledge: No, the data is not readable. The RAID10 A is incomplete because it only has 2 of the 3 members. RAID10 B is incomplete because only has member 3. It needs at least 1 device in each member to show as functional and be able to read/write. RAID10 array metadata I believe has that spare drive device_1_1 prioritized/assigned as member 3 currently instead of device_1_7 and device_1_8 but I do not have a way to remove the device_1_1 through the software/boot interface to see if that will allow the RAID10 to remerge.
To my understanding the 2320 card is just SATA controller with an XOR chip to do parity while relies on driver with CPU to manage the reads/writes. None of the actual drives ever show up in windows device manager. If the RAID10 is working then it shows up as a single SCSI drive and RAID10 volume in explorer, otherwise nothing but RocketRAID 2320 SATA Controller in device manager.

 

[USAFRet]

This is why backups are a thing.

Yes, we understand that you know the RAID thing is not a backup.
But you need a backup of IT.

Entirely unsure of how to resurrect your data.
Possibly this: https://www.freeraidrecovery.com/?s=rd

 

[c19]

<<Removed by moderator>>

Thank you for the response and the warnings. Yes appears so, RAID10 array metadata desync/corrupt/inconsistent whatever issue. Checked as you said, it shows all 6 the individual devices/drives as NORMAL and Configured in BIOS, but missing the respective members of split instances of RAID10, reseated cables again, latest firmware. I have no way to access or edit any of the metadata with my knowledge besides deleting existing array, creating new array or initializing drives. I believe there was an old DOS raid tool from Highpoint that I had used before on a USB key with DOS to have more access but I cannot find it.
Highpoint has responded that the card is EOL (i think they mean End Of Life?) and they can only provide limited support and told me to upgrade to 1 of their new cards. Then said this:

"We checked the screenshots and found that two RAID 10 arrays appeared because two member disks in Member 3 had been dropped for too long. Unfortunately, the loss of Member 3 of RAID 10 has caused data inconsistency. The RAID has become Disabled and its data may not be recoverable. We do not have any other solutions to offer."

They have not responded to the inquiry as to the DOS RAID tool though. I cannot use any 3rd party windows RAID recovery tools more than likely because as I said:

To my understanding the 2320 card is just SATA controller with an XOR chip to do parity while relies on driver with CPU to manage the reads/writes. None of the actual drives ever show up in windows device manager. If the RAID10 is working then it shows up as a single SCSI drive and RAID10 volume in explorer, otherwise nothing but RocketRAID 2320 SATA Controller in device manager.

I'll wait and see if they respond again, but do not have much hope.
No, the data isn't critical. It was full of my Blu-rays and DVDs ripped for plex media server and couple old games moved to make room on SSD. But I want to exhaust all possibility of recovery since it'll take quite awhile to rip/encode all those movies and tv shows again (most likely I won't even bother). Honestly, I just like solving/fixing problems and learning or relearning stuff.

 

[Misgar]

Honestly, I just like solving/fixing problems and learning or relearning stuff.

Best of luck, but if this was my system I'd abandon the Highpoint controller and stick to individual drives, or find a different RAID solution. Prior to that, I'd start backing up all my remaining files to two more locations. Check all your hard disks thoroughly before committing any new data to them.

I mess around with TrueNAS Core RAID-Z2 which being software RAID, does not rely on proprietary hardware RAID controllers. This makes it more versatile and tolerant of handware changes.

I swapped an 8-disk array of 2TB drives from an HP server (Intel Xeon) to another PC (AMD desktop). After copying a small configuration file across, the array was fully operational again. RAID-Z2 means I can afford (in theory) to lose 2 drives from the array and keep all my data intact (fingers thoroughly crossed). I do keep numerous backups on other machines though.

 

[SkyNetRising]

Highpoint said this:
"We checked the screenshots and found that two RAID 10 arrays appeared because two member disks in Member 3 had been dropped for too long. Unfortunately, the loss of Member 3 of RAID 10 has caused data inconsistency. The RAID has become Disabled and its data may not be recoverable. We do not have any other solutions to offer."

You have this kind of config.

Your RAID consists of 3 members (striped RAID 0) and each member consists of 2 drives (mirror RAID1).
You have lost both drives in 3rd member.
In this situation RAID is not recoverable (unless you can somehow magically revive at least one of your failed drives).

 

[c19]

You have this kind of config.

Your RAID consists of 3 members (striped RAID 0) and each member consists of 2 drives (mirror RAID1).
You have lost both drives in 3rd member.
In this situation RAID is not recoverable (unless you can somehow magically revive at least one of your failed drives).

Clearly. And the "failed drives" (device_1_7 and device_1_8) as said are healthy currently labeled as NORMAL and CONFIGURED in the RAID10 B array with members 1 and 2 listed as MISSING, just as the drives of member 1 and 2 (device_1_3 through device_1_6) of RAID10 A show as NORMAL and CONFIGURED with member 3 devices listed as MISSING. If they were failed or showing inconsistency it would be labeled as DEGRADED or CRITICAL. Suggesting that the data is possibly intact but the metadata configuring the RAID10 is corrupted/inconsistent via split/duplicate.