Arch Linux

cuteclown

Guest

Shutdown takes long screen shows empty console

For a couple of months now (estimated, I don't use this system very often), I have an issue where I often have to wait somewhere between 2 to 5 minutes before my system shuts down. I have upgraded and updated all packages in the meantime.

When I shut down, I see a blinking cursor on an otherwise empty console screen. This takes a couple of minutes before the system actually shuts down. I looked at the systemd log with journalctl, but nothing really caught my eye (I will post an excerpt if that's helpful). This delay before shutdown is not consistent; sometimes it does not happen. My suspicion was at first that the longer I use the system before shutdown, the longer the delay, but this is not true. I haven't seen a pattern yet, but it happened at least once that the delay was not there (or at least was short enough that it wasn't noticeable for me).

If anyone has a clue what can cause this, or how to diagnose this any better, I'd be very happy

mmdamin

Member

From: Iran

Registered: 2019-02-19

Posts: 205

Website

Re: Shutdown takes long screen shows empty console

remove 'quiet' kernel parameter to see what is it doing before "System reached target Shutdown"

---

github

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,425

Re: Shutdown takes long screen shows empty console

There are many threads on this, just randomly the first one for a search on long shutdowns: https://bbs.archlinux.org/viewtopic.php?id=245213 (though that "should" get fixed with the latest packages currently the -4 release in testing should contain a fix for this)

cuteclown

Guest

Re: Shutdown takes long screen shows empty console

There are many threads on this, just randomly the first one for a search on long shutdowns: https://bbs.archlinux.org/viewtopic.php?id=245213 (though that "should" get fixed with the latest packages currently the -4 release in testing should contain a fix for this)

Thanks! I couldn't find a thread with a usable solution (I think maybe I shouldn't have used 'console' when I was searching). Anyway, I'll try the suggested solution from that thread (set "use_lvmetad = 0" in /etc/lvm/lvm.conf) tonight.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,425

Re: Shutdown takes long screen shows empty console

Well if you want to actually diagnose this, after waiting out the shutdown, post

sudo journalctl -b-1

saavedra29

Member

Registered: 2018-06-01

Posts: 3

Re: Shutdown takes long screen shows empty console

There are many threads on this, just randomly the first one for a search on long shutdowns: https://bbs.archlinux.org/viewtopic.php?id=245213 (though that "should" get fixed with the latest packages currently the -4 release in testing should contain a fix for this)

Thanks! I couldn't find a thread with a usable solution (I think maybe I shouldn't have used 'console' when I was searching). Anyway, I'll try the suggested solution from that thread (set "use_lvmetad = 0" in /etc/lvm/lvm.conf) tonight.

I had the same problem. Reading this post and using the solution of "lvmetad = 0" in /etc/lvm/lvm.conf solved the problem

cuteclown

Guest

Re: Shutdown takes long screen shows empty console

There are many threads on this, just randomly the first one for a search on long shutdowns: https://bbs.archlinux.org/viewtopic.php?id=245213 (though that "should" get fixed with the latest packages currently the -4 release in testing should contain a fix for this)

Thanks! I couldn't find a thread with a usable solution (I think maybe I shouldn't have used 'console' when I was searching). Anyway, I'll try the suggested solution from that thread (set "use_lvmetad = 0" in /etc/lvm/lvm.conf) tonight.

I had the same problem. Reading this post and using the solution of "lvmetad = 0" in /etc/lvm/lvm.conf solved the problem

Glad to hear it helped you! The solution/workaround worked for me as well.

Well if you want to actually diagnose this, after waiting out the shutdown, post

sudo journalctl -b-1

I've had a quick look. The log only spans a time of about 30 seconds, which is shorter than I had to wait. There also seem to be some other problems I haven't looked at.

The log can be found here.