On Mon, 27 Dec 2010 18:31:25 -0800 John Jason Jordan <[email protected]> dijo:
>On Sat, 25 Dec 2010 23:01:28 -0800 >drew wymore <[email protected]> dijo: > >>mdadm --query should be able to get you the array name at least if my >>interpretation of the man page is correct. In terms of which device >>has the correct boot information it might be a matter of trail and >>error, if you unplug sdb and works then you know that logically it >>should be sda that has the correct boot information. > >Well, mdadm --query fails because I didn't specify a device. Of >course, that is the whole problem. The correct command is "cat /proc/mdstat," since the arrays are maintained in mdstat, which is just a text file. Turns out my arrays are named md0 to md3, and the query command goes "mdadm --query /dev/md0" etc., although --detail gives better results. And it appears that md1 is the bad one. The md1 array is composed of /dev/sda1 and /dev/sdb1, but the --detail command says that /dev/sda1 has been removed. I'm trying to get my head around why removing /dev/sda1 would give me the symptoms I am having. The only problem is that each dist-upgrade installs a new kernel option in the Grub menu, but I cannot boot to anything but the last Hardy kernel. Selecting any of the newer kernels gives me a Grub error -15. So what did these dist-upgrades do, write a kernel to a non-existent disk? _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
