*** This bug is a duplicate of bug 22107 *** On Tue, Oct 31, 2006 at 04:08:38PM -0000, Phillip Susi wrote: > *** This bug is a duplicate of bug 22107 *** > > Matt Zimmerman wrote: > > > > If this is true, then it is probably related to your hardware, and ought to > > be reported as a bug. > > Negative, it is a defect in the lvm script where it spins for up to 3 > minutes waiting for the vg to appear, which never does since we are > using dmraid, not lvm. The lvm script does this because the boot path > starts with /dev/mapper, so it assumes it is referring to an LVM volume. > I have discussed it on IRC with Fabio ( who made the change to the lvm > script since dapper ) and we could not see any other way to resolve this > at this time.
The lvm script shouldn't do any waiting; that step should be in common code for all root device types. That way, all activation takes place, then a single wait for the device to appear. And as I said above, this should be reported as a bug. Positive. > > This will not be satisfactory, as the script will be restored on upgrade and > > the initramfs regenerated. Please help us fix the root cause of the bug > > instead. > > Since edgy has already been released it can not be fixed until the next > release now, and during this development cycle all of the > lvm/dmraid/mdraid/evms boot scripts will be removed and replaced with > udev callouts. This should fix the problem. We have a procedure for post-release updates. -- - mdz -- Intel RAID controller doesn't work https://launchpad.net/bugs/57860 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
