24.10.2017 12:31, Peter Suetterlin пишет:
Andrei Borzenkov wrote:
23.10.2017 20:16, Peter Suetterlin пишет:
So to sum up again:
If you want any useful help show full log (journal -b).
Oct 23 07:44:09 royac6 systemd[1]: Started Timer to wait for more drives before activating degraded array.. Oct 23 07:44:09 royac6 systemd[1]: Stopped Timer to wait for more drives before activating degraded array.. This was in initrd and is correct. Timer is started, array is assembled, device appears, timer is stopped. Oct 23 07:44:13 royac6 systemd[1]: Started Timer to wait for more drives before activating degraded array.. And that is unexpected. There should be no reasons to start timer at this point, unless there is some race condition or bug in mdadm. What happens further is probably direct consequence of this. Oct 23 07:44:43 royac6 systemd[1]: Starting Activate md array even though degraded... In Leap 42.2 this service has Conflicts against device node. When systemd attempts to start this service, it also attempts to "stop" device node. While this is not possible, it will cause anything depending on this device node (mount point in the first place) to be stopped as well. So you get Oct 23 07:44:43 royac6 systemd[1]: Started Activate md array even though degraded. Oct 23 07:44:43 royac6 systemd[1]: Stopped target Local File Systems. Oct 23 07:44:43 royac6 systemd[1]: Unmounting /home... Oct 23 07:44:43 royac6 systemd[1]: Stopped (with error) /dev/md1. Oct 23 07:44:43 royac6 systemd[1]: Unmounted /home. As for Postfix I suspect it has dependency on /home.
If you can reproduce this problem, boot without "quiet" on kernel command line, it will give more verbose and hopefully more useful log.
OK, I'll take the quiet out. Yes, I've seen it once before. But the machine is typically only booted once or twice a year....
Given that it is likely one-off condition rebooting once a year is unlikely to provide much useful information. Besides in 42.3 service was changed to not conflict, instead it is using conditional to skip starting. It would be interesting to (try to) understand how timer gets enabled. Could you provide output of "udevadm info --export-db" (not as compressed file, please)? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org