On 03/12/2015 12:51 PM, David Wright wrote:
If I don't have "quiet" in the kernel parameters line, I get something that looks like dmesg on steroids, and it's impossible to tell what's going on at all. OTOH with it, and I'm lucky to get anything at all. I just sit and wait for a "clear-screen" (why does it do that and how do I stop it? Is there a dont-clear-screen.service?) and a login prompt. On random occasions, some messages do appear, just a little more verbose than is convenient, but an improvement. However, these messages usually mean trouble, and I finish up waiting for some service to start, with no limit on the wait (Bug#778881) and have to reboot.
I run into this issue on a fairly regular basis with one of my systems. Fortunately, it's a local system. It'd be pretty annoying if it was one of the remote systems.
Sometimes, I get a stalled shutdown in a similar manner, so I have to hard-reset. If, as a result, the system decides to fsck the disk, systemd gives no indication of the fact. Actually it's the same if you force a full fsck with the kernel parameter: when systemd fscks the root filesytem, all you see is that the disk is busy. You only get progress % when it checks the other filesystems later on.
And again, I have seen the stalled shutdown once-in-a-while on all of the local systems (and presumably on some of the remote ones). However, the fact that the remote systems all eventually became reachable again goaded me into simply waiting on the local ones that were stalled. In my case the stalled machines have all eventually proceeded with the shutdown or reboot. I have waited as long as six minutes. I have wondered how long the delay might get on a system that was running a lot of services.
I have seen an improvement in this behavior recently so that shutdown or reboot are almost always practically instant. The only remaining holdout has been my personal system -- the one from which I perform all the maintenance. If I just manually shut down a bunch of apps and the VPN connection and shut down or reboot immediately sometimes I'll see a minute's delay in the shutdown on that system.
Best, JP