After upgrade on Fri 26 Jul 2019 my system don’t shutdown or reboot.
Occasionally, after an update, I find that I need to:
CTRL-ALT-F1 (get to a terminal)
login as root
shutdown -r now
After** shutdown -r now **my system remains stuck with a prompt.
I need to press reboot button from my case.
You can try CTRL-ALT-DEL
Around two weeks ago, I did run into a situation with Tumbleweed where nothing worked other than a forced power off. I don’t like doing that, because it can lead to file system corruption. But everything recovered correctly on reboot.
I’ve also been using
shutdown -r now, but the verbosity of it finally inspired me to revisit the subject.
JdeBP at https://unix.stackexchange.com/a/196014/ claims:
- systemctl isolate reboot.target has the shorthands:
- shutdown -r now
- telinit 6
- systemctl reboot
- plain unadorned reboot
reboot manpage says:
These commands are implemented in a way that preserves compatibility with the original SysV commands. systemctl(1) verbs halt, poweroff, reboot provide the same functionality with some additional features [e.g.
[systemctl reboot recovery](https://www.freedesktop.org/software/systemd/man/systemctl.html#reboot%20arg)].
So unless someone provides a compelling reason to keep using
shutdown -r now, I’ll probably just use
reboot from now on.
After CTRL-ALT-DEL nothing happens.
That should be fine.
reboot don’t solve the problem.
What desktop environment are you using? Can you log out?
Has happened to me several times recently. One of the suspects is VM software or usage of VM (host is Linux). The other suspect is a defect in kernel.
Shutdown and reboot didn’t work in any way besides hard shutdown by removing power.
However, minimizing damage to filesystems is possible. If possible, switch to runlevel 1 or 3 in virtual terminals 1, 2 or 10 after shutdown started. Kill the users’ processes that were using filesystems like editors. Unmount all possible partitions, which likely means all besides /. Say sync. Try to shutdown again from command line. If not successful, then remove power.
I don’t have trust in successful shutdown these says. Because of that, before shutdown, I close programs and then:
- switch to runlevel 3
- switch to runlevel 1
- unmount important but unused partitions like /home
- clean a few temporary locations like /tmp/
- shutdown or reboot from the command line.
I haven’t had any problems with shutting down or rebooting in a while.
Two old problems were:
- proprietary NVIDIA drivers (they eventually fixed whatever the problem was)
- forgetting to close all programs (ZStefan just reminded me of that)
Something else you can try is
systemctl reboot --force (or replace reboot with poweroff)
If combined with --force, shutdown of all running services is skipped, however all processes are killed and all file systems are unmounted or mounted read-only, immediately followed by the reboot.
Why to do
systemctl reboot --force
This is not a solution for my problem.
I don’t think is nvidia driver, maybe kernel or systemd.
How to view shutdown log ?
It’s not a solution, but it’s probably better than a hard shutdown (and easier than ZStefan’s manual approach) if it works.
If you want a solution, you need to provide more details. I asked you “What desktop environment are you using? Can you log out?”
You can use the journalctl command or Yast2’s “Systemd Journal” program to look for errors.
Without more details the only solution that can be blindly provided would be for you to rollback to before the update.
I use KDE.
If I want to log out, the display goes black for 30-40 sec.
Was ‘zypper dup’ used to upgrade?
I use only
sudo zypper dup
I don’t have a nfs server, it’s a desktop machine.
And after that, are you at the display manager (log in screen)?
Can you shut down from there?
It upgrades the kernel to 5.2.3 – maybe you will get lucky.