http://bugzilla.opensuse.org/show_bug.cgi?id=923150 Bug ID: 923150 Summary: dracut initrd doesn't manage software raid correctly Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: diego.ercolani@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 627622 --> http://bugzilla.opensuse.org/attachment.cgi?id=627622&action=edit initrd containing the raid/lvm defiition mdadm-3.3.1-5.14.1.x86_64 lvm2-2.02.98-43.17.1.x86_64 dracut-037-17.9.1.x86_64 This bug is similar to my #864046 I have a server with 2 software raid1 partitions: bacula:~ # fdisk -l /dev/sd[ab] Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x000de4bf Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 1953791 1951744 953M fd Linux raid autodetect /dev/sda2 1953792 197265407 195311616 93.1G fd Linux raid autodetect /dev/sda3 197265408 488396799 291131392 138.8G 83 Linux Disk /dev/sdb: 298.1 GiB, 320072933376 bytes, 625142448 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00045632 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 1953791 1951744 953M fd Linux raid autodetect /dev/sdb2 1953792 197265407 195311616 93.1G fd Linux raid autodetect /dev/sdb3 197265408 625141759 427876352 204G 83 Linux these is mdadm.conf: DEVICE containers partitions ARRAY /dev/md/lvm metadata=1.2 UUID=c597d138:e1f2e5d4:1c3b402c:a50dde86 name=bacula:lvm ARRAY /dev/md/boot metadata=1.2 UUID=0785bc0e:391029e5:02bbf14b:5c653ae9 name=bacula:boot and this is the lvm table: PV /dev/md/lvm VG raid lvm2 [93.13 GiB / 43.13 GiB free] PV /dev/sda3 VG nonraid lvm2 [138.82 GiB / 106.82 GiB free] PV /dev/sdb3 VG nonraid lvm2 [204.02 GiB / 197.02 GiB free] and logical volumes: ACTIVE '/dev/raid/mysql' [40.00 GiB] inherit ACTIVE '/dev/raid/ROOTHOME' [10.00 GiB] inherit ACTIVE '/dev/nonraid/swap' [4.00 GiB] inherit ACTIVE '/dev/nonraid/rootfs' [25.00 GiB] inherit ACTIVE '/dev/nonraid/tmp' [10.00 GiB] inherit This are related mountpoints: /dev/mapper/raid-ROOTHOME on /root type ext4 (rw,relatime,data=ordered) /dev/mapper/raid-mysql on /var/lib/mysql type ext4 (rw,relatime,data=ordered) /dev/md127 on /boot type ext4 (rw,relatime,data=ordered) /dev/mapper/nonraid-tmp on /tmp type ext4 (rw,relatime,stripe=32,data=ordered) The issue is that initrd don't seem to activate the mdraid device containing the lvm "raid" volumegroup ('/dev/raid/mysql', '/dev/raid/ROOTHOME') if I boot to shell passing "shell" to cmdline (/proc/cmdline is BOOT_IMAGE=/vmlinuz-3.16.7-7-default root=UUID=0edae592-0c1c-48e4-82a0-03a6549def3d resume=/dev/nonraid/swap nomodeset vga=0 shell) the situation is that only /dev/md127 (/dev/md/boot) is enabled and I have to manual enable /dev/md/lvm with "mdadm --assemble /dev/md/lvm" and activate the logical volumes with "lvm lvchange -ay /dev/raid/mysql; lvm lvchange -ay /dev/raid/ROOTHOME" before exit the initrd shell and continuing the boot process -- You are receiving this mail because: You are on the CC list for the bug.