Quoting Rui Ruas: > After reading about this on a few foruns, I think the problem is created > by mdadm. Have you tried manually editing the contents of fstab using > the output of "mdadm --detail --scan"?
Well, the problem is that my / is a logical volume on /dev/md1. So mdadm --detail --scan returns a UUID for /dev/md1, but fstab is mounting a different UUID -- the one for /dev/mapper/group0-linux, which *lives* on md1. For some reason, initramfs is not "seeing" the logical volumes, so it can't match up my "root=/dev/mapper/group0-linux" with its UUID. Which forums were you looking at? Peter -- Peter A. H. Peterson, technician and musician. ---=[ http://tastytronic.net/~pedro/ ]=--- -- 2.6.24-21 kernel update breaks mdadm raid 1 boot https://bugs.launchpad.net/bugs/290231 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
