https://bugzilla.novell.com/show_bug.cgi?id=733283 https://bugzilla.novell.com/show_bug.cgi?id=733283#c3 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #3 from Neil Brown <nfbrown@suse.com> 2011-12-12 06:02:13 UTC --- Thanks for the report. I'm not sure how to proceed with this. I probably need to find someone with a good understanding of systemd.... We only include mdadm on the initrd if it will be needed to mount '/', '/usr' or swap. This is not the case for any of the systems described here as far as I can tell, so not including mdadm is correct. The intention is that initrd should just mount enough to get the root filesystem mount and the the scripts etc on the root filesystem get everything else mounted. Once '/' is mounted, "/sbin/udevadm trigger' is run (by /etc/init.d/boot.udev) to cause all devices to be 'discovered' again. This time mdadm will exist and the arrays will be created instead of reporting that 'mdadm does not exist'. Maybe systemd has the wrong idea about the ordering between mounting everything else in /etc/fstab, and running "udevadm trigger" or something. Frederic: can you shed any light on the systemd behaviour here? Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.