When booting my powerpc server into lucid, it hangs in initramfs, unable to find /dev/mapper/vg00-root : the same disk configuration and fstab worked successfully under karmic. To complete the boot, I must run the following two commands manually:
modprobe dm_mod
lvm vgchange -a y
I do not encounter this issue on a similarly configured amd64 system. Further investigation shows that the dm_mod kernel module is built-in for amd64, and that the /dev/mapper/* nodes are populated correctly during startup with this configuration.
Please set the dm_mod module to be a built-in also for powerpc (or any other architectures where it may be missing).
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-20-powerpc 2.6.32-20.29
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-20.29-powerpc 2.6.32.11+drm33.2
Uname: Linux 2.6.32-20-powerpc ppc
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: powerpc
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
CurrentDmesg:
[ 126.309570] input: Mouseemu virtual keyboard as /devices/virtual/input/input3
[ 126.311333] input: Mouseemu virtual mouse as /devices/virtual/input/input4
[ 127.947501] eth0: no IPv6 routers present
Date: Sun Apr 11 23:05:54 2010
HibernationDevice: RESUME=UUID=94943b87-8978-4bd5-a2fb-bc5421e1c791
PciMultimedia:
ProcCmdLine: root=/dev/mapper/vg00-root ro quiet splash
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.33
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Unfortunately this wasn't discovered before the kernel freeze was already in effect for final release. It can and should be fixed for the first post-release kernel upload, as well as being mentioned in the release notes.