http://bugzilla.opensuse.org/show_bug.cgi?id=905746 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #1 from Neil Brown --- That is strange. the "dmraid.sh" script in dracut which runs "dmraid -ay" to activate the array then runs "kpartx -a /dev/mapper/..." which should create the partitions. Some step there is presumably going wrong. Maybe there needs to be a 'udevadm settle' between the 'dmraid -ay' and the 'kpartx' to make sure the /dev/mapper/XX device does exist. Can you experiment? It would require: - update back to 13.2 - when dracut gives you a shell, check the expected devices are missing - run kpartx -a /dev/mapper/ddf1_System - check that the expected devices now appear - 'exit' - I think that will allow the 'boot' to continue - edit /usr/lib/dracut/modules.d/90dmraid/dmraid.sh and insert 'udevadm settle' after each 'dmraid...' command. - run mkinitrd - reboot And let me know how far you get. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905746 --- Comment #3 from Tim Nicholson --- Created attachment 614666 --> http://bugzilla.opensuse.org/attachment.cgi?id=614666&action=edit Screenshot of dracut status Showing how dmraid is using a different naming convention to what the boot up process expects /dev/mapper/ddf1_System_part1 <-> /dev/mapper/ddf1_System1 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905746 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hare@suse.com Flags| |needinfo?(hare@suse.com) --- Comment #5 from Neil Brown --- I'm sure I've seen this before..... When kpartx makes partitions, it defaults to using 'p' to separate the partition number from the device name if the latter ends in a digit, and an empty string otherwise. That is why you see "ddf1_System1". - dracut is letting kpartx use the default. When udev triggers the creation of paritions via /usr/lib/udev/rules.d/66-kpartx.rules, kpartx is run as kpartx -u -p -part /dev/$name The "-p -part" should tell it to use "-part" as the separator resulting in /dev/mapper/ddf1_System-part1 So why dracut is waiting for /dev/mapper/ddf1_System_part1 (underscore instead of hyphen) I don't know. This is probably related to /lib/udev/rules.d/67-kpartx-compat.rules which should create symlinks with the "_part1" name. That seems to only work if "DM_PART" is set, and I cannot see where it gets set. So if you modify /usr/lib/dracut/modules.d/90dmraid/dmraid.sh to add "-p _part" to the options to kpartx, and then "mkinitrd", it might work. But it is at least a little confusing. Hannes: do you know what is meant to happen here? In particular, what sets DM_PART, and why isn't it being setting inside dracut? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905746 --- Comment #7 from Neil Brown --- No "-p -part" doesn't get confused by the "-" - is used "-part" literally as the separator (I just tested to double-check). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905746 http://bugzilla.opensuse.org/show_bug.cgi?id=905746#c13 Hannes Reinecke changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(hare@suse.com) | --- Comment #13 from Hannes Reinecke --- Created attachment 638240 --> http://bugzilla.opensuse.org/attachment.cgi?id=638240&action=edit 0001-dmraid-rely-on-kpartx-udev-rules.patch dmraid: rely on kpartx udev rules to generate partitions. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905746 http://bugzilla.opensuse.org/show_bug.cgi?id=905746#c15 --- Comment #15 from Iakov Karpov --- (In reply to Hannes Reinecke from comment #14)

Please test with the above patch.

The patch does the trick, many thanks! OS starts flawlessly, with all partitions mounted. "Bootloader" module in YaST works too (workaround in #c5 did break it). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=905746 http://bugzilla.opensuse.org/show_bug.cgi?id=905746#c18 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #18 from Thomas Renninger --- see last autobot comment.. -- You are receiving this mail because: You are on the CC list for the bug.