Brian, I started from scratch tonight building the arrays again as I spec'd in the first post using the beta1 server install disk.. After a successful install and a few reboots I was able to get a normal prompt from which I performed a apt-get dist-upgrade. I noticed this time that I was prompted in the middle of the upgade to choose which arrays were to become active. It defaulted to "all" and that's the way I set it.
However, after a reboot, it once again fails. Just to make sure I'm clear about the problem, when it fails - which is most of the time - here's an approximation of the screen info: Loading please wait mdadm: no devices listed in conf file were found 3-4 modprobe usage statements 4 mount statements no such file or dir target filesystems doesn't have /sbin/init Busybox info can't access tty: job control turned off (initramfs) prompt Even on those rare occasions when it actually does boot successfully, I still see the "mdadm: no devices listed..." line. When it fails it always looks pretty much like the screen approximation (above) dumping me at the initramfs prompt. From there, /proc/mdstat always says that my 3 arrays are active. As an aside, If I'm understanding many of the other raid bug posters they *have* to insert a break=mount statement in order to arrive at the initramfs prompt. That has never been the case with this machine. I've *always* been dumped to a iniramfs prompt after installing, both before and after the dist-upgrade. -- Feisty beta1 raid is broken https://bugs.launchpad.net/bugs/96511 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
