Hi all- I''ve been fortunate enough to not have to email this august group for advice regarding my mdadm arrays in quite awhile, but am looking for some suggestions. I woke up this morning to something beeping in my headless Norco server case at home (never a promising start to the morning). I was unable to ping the box which increased my dismay. I proceeded to perform a hard reboot, and still nothing on the ping. At this point, I plugged a monitor in to see what was happening on reboot. Let me take a moment to provide details of my basic set up. There are three separate HD controllers being used in this box: the motherboard headers, a supermicro PCI-X card (in a PCI slot), and a Highpoint RocketRaid SAS controller used as JBOD. I have a number of separate mdadm arrays tied to this physical box that have been built over the years including a RAID6 one, a RAID10, and 2 mirrors. Unfortunately, I did not take the time to physically label the drives in the box (there are close to 20) as I built these, and had been meaning to, but life got in the way. Since I have had no issues with these arrays in a very long time, I don't even remember if I split them across controllers or what. So back to the reboot, I can see the motherboard drives showing up as the POST runs through its paces. I can then see what appears to be the Supermicro drives showing up, but when the Highpoint controller gets to it own internal boot screen, it hangs at detecting drives, and I am unable to get into the controller card BIOS by hitting ctrl-H (keyboard works though, as I can ctrl-alt-delete, so it is not locking the PC). So at this point, I don't know my point of failure. I am guessing the Highpoint flaked out though, especially since I now believe that was the component beeping based on the PC restarting ok otherwise. I am looking for advice on minimizing my risk of making things worse as I attempt to identify what drives belong which with array. The RAID6 is my most immediate concern in getting back up and running. My immediate thought was to disconnect all drives and then reconnect them one by one from a motherboard header, and use: mdadm --examine /dev/sdX1 Will that give me enough info to figure out which drive belongs to which array? Does anyone have any other suggestions? I am not sure of the current state of ANY of the arrays that were on this box, but I don't want to make things worse by booting this system up with some drives missing because I've unplugged them, and having the a bad situation get worse. -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
