В Mon, 30 Mar 2015 18:46:16 +0200 Manfred Hollstein <mhollstein@t-online.de> пишет:
Hi there,
I first observed $SUBJECT when I upgraded to 20150327, but another upgrade to snapshot 20150328 did not help either.
My system uses one SSD for the root fs, four disks in soft-mdraid10 mode for various LVs. When the system hangs (sort of), having to Ctrl-Alt-SysRq "s", followed by "u" followed by "b" is not really fun, because the mirror will then resync afterwards (for appr. 6 hours).
I saw some dependency cycles with AppArmor and disabled apparmor.service, hoping this would help (AppArmor is not installed, only the stuff which is actually really required), but it didn't. What's really surprising me is, the system boots properly every second time, but hangs after the "Started D-Bus System Message Bus."
How long did you wait? Default timeout for starting services is 90 seconds. Please try without "quiet" on kernel command line (and plymouth disabled) - systemd should display animation when service takes too much time.
during the other boot attempts. Switching to console 10 is still possible, so is the usage of the Ctrl-Alt-SysRq's... hmm, maybe I should look into the current task list to see which process is making trouble... (followed by another resync for 6 hours...).
Anyway, this problem cannot be seen on a laptop with only one disk. I'm suspecting the upgrade to udev-219, as a lot of "waiting for ..." messages now appear on the multi-disk system, while nothing like that could be seen with the udev version before that (-210?).
Is anybody else seeing similar strange behaviour?
TIA, cheers.
l8er manfred