14.01.2017 21:31, Andrei Borzenkov пишет:
Could you once more try both good and bad cases with udev debugging, but now using
udev.log-priority=debug systemd.log_target=kmsg log_buf_len=16M printk.devkmsg=on
OK, this was more successful. Now we at least see [ 23.647300] systemd-udevd[623]: IMPORT '/sbin/mdadm --incremental --export /dev/sdc21 --offroot ${DEVLINKS}' /usr/lib/udev/rules.d/64-md-raid-assembly.rules:33 [ 26.224213] systemd-udevd[623]: Process '/sbin/mdadm --incremental --export /dev/sdc21 --offroot ${DEVLINKS}' failed with exit code 1. for all components. This proves that startup sequence is correct. What you can try next - insert "-vvv" into mdadm invocation in udev rules; something like ACTION=="add|change", IMPORT{program}="BINDIR/mdadm -vvv --incremental --export $devnode --offroot ${DEVLINKS}" This hopefully will provide some additional output when mdadm fails and this output should be logged by udev. Run bad case with the same kernel parameters. There is no need to run good case as we know where it fails now. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org