AMD RAID 1 keeps losing drive assignment for one of the drives

r00tb33r

Distinguished
Jan 21, 2011
135
1
18,715
Motherboard: Gigabyte GA-MA770-UD3 rev 2.1, latest BIOS
Chipset: AMD SB770
Drives: 2x 500GB Samsung HD501LJ
OS: Windows 7 64-bit

I have a problem where one of two drives in RAID 1 array repeatedly loses it's assignment to the array. Normally the drive is 1 of 2 in the array, but now it's state is single drive for some reason and drive 2 of 2 remains in the array and array status is "Critical" (obviously). The drive that loses it's assignment is reported as "Healthy" and Windows sees it, and Disk Management sees the partitions. SMART status says good.

AMD RAIDXpert user interface gives me an option to rebuild the array, choosing the "single drive" which was formerly from this very array. So I rebuilt the array yesterday, today it lost the drive assignment again and it's a single drive + broken array with one remaining drive ("Critical"). Considering it has now happened twice I would like to know why this is happening because from what I've read rebuilding arrays is always very taxing on the drives, so rebuilding the array every day would probably not be productive.

Both RAIDXpert interface under Windows and RAID BIOS utility concur on the status of the drive assignments.

I have three of these motherboards and this is the first time I have a RAID problem on it, RAID 1 normally works well for me. This particular build is 6 months old. No, I can't test with another board because that would require me to destroy the RAID setup on another machine.

A picture is worth a thousand words...
BIOS RAID utility array status:
IMG_20150211_205359.jpg

BIOS RAID utility physical drive list:
IMG_20150211_205444.jpg

AMD RAIDXpert interface physical drive list:
IMG_20150211_211123.jpg

AMD RAIDXpert interface array status:
IMG_20150211_211149.jpg


I need help fixing this in such a way that drives STAY assigned to the array. What's going on here, why is the first drive losing it's assignment to the array???

Note:
AMD's Catalyst driver distribution service is a piece of junk... All three of my machines use the same RAID driver, so it's doubtful that it's a driver issue.
 
Was the array (the one the drive was originally setup to) as single drive array or multiple drives? Often times, if you are taking a drive that was in a multiple drive array, and changing it to a single drive array, you have to delete the array, then create a new single drive array.
 

r00tb33r

Distinguished
Jan 21, 2011
135
1
18,715


RAID 1 is a two drive setup where the contents are mirrored and the OS sees the array as one drive.

The drive was in the array. Now it claims it's a single drive and the other drive is the sole remaining drive in the array that is now broken. I want it back in the same array it used to be in. No, I did not change it's status myself, it just randomly happened and the only reason I know is because the RAID watchdog service notified me that the array has become "Critical".

After rebuilding it's back in the array, but some hours later it has lost it's assignment to the array again.