oneiric boot sequence very slow with lvm

I had something similar a few months ago on Maverick - but it disappeared, never did find out why.

The problem still exists on my pc but I can't reproduce it on a virtualbox machine with similar configuration.

Same here, I can recreate it on a VirtualBox VM though.
Tried both using a separate logical volume for /var and keeping /var on the root logical volume.
Same effect.

I've noticed this effect before on Narwhal, but with the upgrade to 11.10 the effects are worse

Status changed to 'Confirmed' because the bug affects multiple users.

I have also this problem with 11.10.

My root device is just a normal SSD, but the /home logical volume and an additional logical volume is a lvm which currently only has /dev/md0 as physical disks. /dev/md0 is a raid 1 with /dev/sda1 and /dev/sdc1 in it.

the boot hangs indefinitely, but if I press ctrl-alt-del, the machine reboots to grub. Have to press enter, and the system then boots normally, but asks if I want to boot with degraded raid. If I say "n", busybox starts. Then writing "exit" results in a nice rest of the boot. A bit complicated, but works.

After the updates of yesterday, the machine has booted much quicker now. Only a couple of times of experience yet, though.

I was too hasty. The problem is still here. Is it possible to switch to the old (sysV?) style boot sequence?

This seems to be the same problem reported on bugs #802626 and #906358, and it's related to udev. The workarround suggested on comment 31 on the later worked for me.

The workaround did not seem to work for me. I guess the bug I am experiencing is different, or the combination of RAID+LVM needs yet another workaround to work.

Is there an option of switching to a different boot process, like SYSV type init scripts etc. within Ubuntu?

I have a similar setup in a debian system and it has no such problem. I would not want to start switching to a different distribution.

updated to precise pangolin and it seems that it does not have the boot issue for me. I don't know whether they fixed it or is it just a race condition that is not triggered for some reason.