problems with / on LVM/RAID1
Hi,
I'm having some problems with / on LVM/RAID1. The situations is as follows:
/dev/sda1 ext3 /boot
/dev/sda3 and /dev/sdb3 are used for /dev/md0 (raid1)
/dev/md0 is a single PV for a VG "raid"
this volume group contains three LVs, one of them being
/dev/mapper/raid-slash with ext3 mounted on /
This layout was created with the Etch beta 3 installer, and the
installation worked fine. The kernel is
linux-image-2.6.17-2-amd64-generic 2.6.16-17.
Now I want to run linux-image-2.6.17-2-amd64 2.6.17-8. However, the raid
device is not started, no LV are available and / cannot be mounted. The
exact error message is:
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
mdadm: No devices listed in partitions
device-mapper: 4.6.0-ioctl (2006-02-17) initialised: dm-devel@redhat.com
Volume group "raid" not found
Done.
Begin: Waiting for root file system... ...
This does not happen for the old kernel.
mdadm is configured to bring up all raid devices early in the boot
sequence. When I install the new kernel package, there is the following
message:
Using mkinitramfs-kpkg to build the ramdisk.
I: mdadm: RAID support installed to mount all RAID arrays during boot.
I: mdadm: use `dpkg-reconfigure -plow mdadm` to change this.
So, everything should be fine. And I use /dev/mapper/X-Y, not /dev/X/Y
(see #378332).
I have no idea what's going wrong. I compared the two initrd's:
Only in 2.6.17-2/etc/modprobe.d: nvidia-kernel-nkc
Only in 2.6.17-2/etc/udev: libnjb.rules
Only in 2.6.17-2/etc/udev: logitechmouse.rules
Only in 2.6.17-2/etc/udev/rules.d: 025_logitechmouse.rules
Only in 2.6.17-2/etc/udev/rules.d: libnjb.rules
Only in 2.6.17-2/etc/udev/rules.d: z60_xserver-xorg-input-wacom.rules
Only in 2.6.17-2/etc/udev: xserver-xorg-input-wacom.rules
Binary files 2.6.16-2/lib/libc.so.6 and 2.6.17-2/lib/libc.so.6 differ
Binary files 2.6.16-2/lib/libcrypt.so.1 and 2.6.17-2/lib/libcrypt.so.1
differ
Binary files 2.6.16-2/lib/libdevmapper.so.1.02 and
2.6.17-2/lib/libdevmapper.so.1.02 differ
Binary files 2.6.16-2/lib/libdl.so.2 and 2.6.17-2/lib/libdl.so.2 differ
Binary files 2.6.16-2/lib/libm.so.6 and 2.6.17-2/lib/libm.so.6 differ
Binary files 2.6.16-2/lib/libselinux.so.1 and
2.6.17-2/lib/libselinux.so.1 differ
Binary files 2.6.16-2/lib/libsepol.so.1 and 2.6.17-2/lib/libsepol.so.1
differ
Only in 2.6.16-2/lib/modules: 2.6.16-2-amd64-generic
Only in 2.6.17-2/lib/modules: 2.6.17-2-amd64
Binary files 2.6.16-2/lib64/ld-linux-x86-64.so.2 and
2.6.17-2/lib64/ld-linux-x86-64.so.2 differ
Of course, some binary files differ, but no obvious changes in the
configuration files that could be responsible for the problem. Google
shows only one hit for "mdadm: No devices listed in partitions" ...
Thanks for any hints,
Joachim
Reply to: