Comment 20 for bug 310928

Revision history for this message
John Ryan (johnryannz) wrote :

Well after a fair bit of mucking around, it looks like I have completely lost my array. The BIOS now reports the array status as "Failed", while /dev/sda is listed as a "Non-RAID Disk" and /dev/sdb is a "Member Disk(0)". However, I cannot seem to be able to add /dev/sda back into the array either in the BIOS or with "dmraid -R isw_bbiechciij_Array /dev/sda". Nor does adding /dev/sda as a hot spare work as it gets added to a new array instead of "isw_bbiechciij_Array" (it will not accept "isw_bbiechciij_Array" as a legal array name to add it to because it is greater than 15 chars long).

The problem all seemed to stem from the fact that when I first re-added a disk to the array last night (prior to the successful rebuild), the name of the array was changed by the BIOS. After a reboot (or in my case, powering off for a day), I then had two different array names and neither could be started. I had to use "dmraid -x isw_daifjieafd_Array" (from either a live CD or the busybox prompt) to delete the new array, then go into the BIOS and re-add the disk again. Unfortunately, this resulted in a new name for the array being generated and so on and so forth. This went on until I deleted the array on /dev/sda instead of the one on /dev/sdb and as a result ended up stuck with the "Failed" array.