On Sat, 2007-02-03 at 16:12 +0000, Matt Price wrote: > On Sat, 2007-02-03 at 15:20 +0000, Fabio Massimo Di Nitto wrote: > > It is a known problem that is being worked out. At the moment the only > > workaround is to > > run a couple of commands from the command line when you are dropped to the > > shell at boot time. > > > > basically you need to start the raid manually, and then: > > > > lvm vgscan > > lvm vgchange -a y > > exit > > > thanks for the quick response fabio. unfortunately this system has > three lvm vg's, and only one of them is detected by vgscan -- alas, not > the root system, but the vg containing my audio and video storage. so > still no luck!
correction: actually this fix works if the following command is run first: ./scripts/local-top/mdadm it may also be necessary to append: break=mount to the boot line in grub. > > > Fabio > > > > PS Yes i am aware this is not optimal but as i said a fix shold land > > sometimes next week. > > > -- > Matt Price > History Dept > University of Toronto > [EMAIL PROTECTED] > -- Matt Price History Dept University of Toronto [EMAIL PROTECTED] -- mdadm broken after feisty upgrade, no boot https://launchpad.net/bugs/83050 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
