dist-upgrade LVM on RAID: boot failure

 affects lucid
 summary "boot failure with LVM on RAID"
 importance high
 subscribe

System has 2 disks, each of 500 MB.
System was installed with Ubuntu 8.10, and disks set up as follows:
1: sda partitioned to:
        /dev/sda1 50GB Linux raid autodetect
        /dev/sda2 16GB Linux raid autodetect
        /dev/sda3 Rest Linux raid autodetect

2: sdb partitioned to:
        /dev/sdb1 50GB Linux raid autodetect
        /dev/sdb2 16GB Linux raid autodetect
        /dev/sdb3 Rest Linux raid autodetect

3: RAID1 mirrors created:
        /dev/md0, created from /dev/sda1 and /dev/sdb1:
                assigned as / (ext3)
        /dev/md1, created from /dev/sda2 and /dev/sdb2:
                assigned as swap
        /dev/md2, created from /dev/sda3 and /dev/sdb3:
                set up as an LVM volume
 and with package updates downloaded from the network,
4: The LVM volume was configured to hold the following
        file systems, all using ext3:
        /var
        /home
        /vol/archives
        /vol/vmware

This setup worked fine for upgrades to:
        9.04
        9.10
        10.04 alpha 2

Having upgraded to 10.04 alpha 2, I applied updates using update
manager. A reboot on 13 April was successful. After my next update, on
18 April, the system failed to complete the boot.

With the same disk structure, the system fails to boot after an install
from the 10.04B1 alternate CD with updates from the Internet being
included.

The boot process is waiting for /home to become available, but the LVM
volume is not accessible. Examining the list of loaded modules suggests
that the kernel module to support LVM is no longer being included
in /boot/initrd for the latest kernels.

If I boot from the 9.10 or 10.04B1 alternate CD (or the 9.10 DVD), and
mount the file systems manually, the mounts succeed, which indicates
that the underlying file system structure is OK.

This seems to indicate that a change to kernel or to LVM

--
Tim Frost <email address hidden>