Possible Kernel/Grub/systemd Shutdown Error Message

I’m still able to reboot just fine, but I still see these messages show, specifically the last 3 lines only started to display after a systemd update. The watchdog messages I’m not concerned about. It’s a random issues I’ve seen people report earlier this year and last year and ever before that, but for whatever reason it only started to show up for me this year.

[     40.550004] watchdog: watchdog0: watchdog did not stop!
[     40.719409] watchdog: watchdog0: watchdog did not stop!
[     40.769894] sd-unmoun[1704]: Failed to unmount /oldroot: Device or resource busy
[     40.770754] sd-unomun[1785]: Failed to unmount /oldroot/sys: Device or resource busy
[     40.771918] shutdown[1]: Failed to finalize file systems, ignoring.

Yeah, systemd just updated yesterday, and /oldroot is a systemd thing. There have been several times in the past few years that systemd has had bugs involving the unmounting of /oldroot.

If you’re not seeing any specific issues, if it were me, I would wait and see if there is a systemd update in the next few days. I would suspect a bug that has been around in the past has shown its head again. That’s just what I would do, feel free to do whatever you feel is best for your system.

If it persists, and there are no bug reports on systemd’s github site, then you might want to dig in deeper.

2 Likes

Yeah that’s some pretty solid advice, thank you. There’s been maybe one or two systemd updates since then, but it has’t removed these messages. Luckily I haven’t noticed any issues at all other than these shutdown messages.

Just checked out the systemd github, they’ve got over 1.5k issues at the moment. I’ll see if my issue has already been reported recently and if not I’ll create a new issue if need be and just go from there. In the meantime, thanks again for all your help, very much appreciate it and I learned a little bit more today so thank you :slight_smile:

1 Like

The messages suggest that your / partition may not be unmounted cleanly before shutdown. This could prove problematic, causing corruption; assuming it is a temporary issue, though, I personally wouldn’t sweat it. If you get fsck warnings, or you see a list of orphaned inodes on your boot, then you may want to dig deeper, like, right away :laughing:.

I have learned that systemd bugs generally tend to get sorted out pretty quickly, and again, if it were me, I would assume that the fact that these warnings first appeared after a systemd update means it’s probably a systemd bug.

2 Likes

I’ll for sure keep an eye on any boot messages like that and let y’all know. I think I’ll wait for the next systemd update and if I still see it I’ll report it to them upstream. Thanks again!

2 Likes

@Stagger_Lee

Hi Guys,

I did an update last night of my system and my system is showing two symptoms which maybe simlar to yours:

  • Kernel sporadically taking over 20 seconds to loads (vs under 5s normally).
  • I’m also seeing “Watchdog did not stop” messages on shutdown if I have a slow boot up time.

I posted my notes here just in case you guys hear anything new:

No shutdown issues on my Nvidia :wink:

https://clbin.com/27eWl

Hi Rick,

Did you run “journalctl -e -b-1” to capture the shutdown logs?

Thanks.

yes…

Generally in my case (no Nvidia) the system only hangs on shutdown if i have a long kernel boot time. Otherwise my laptop shutsdown gracefully.

I’m not confident Nvidia is related to what @Scotty_Trees is experiencing.

It’s more than likely related to systemd

More than likely it’s Gnome thing! :laughing: Touche’

It’s probably because I have a bunch of KDE packages install!

:wink:

What you converted? :scream:

To put an end to this eternal DE feud, there should be a new DE: Knome or Glasma or some such :stuck_out_tongue_winking_eye:

1 Like

No feud. It’s just a little bit oh fun! :wink: :innocent:

So to recap, we all agree Gnome is okay and this shutdown error is more than likely systemd related :wink:

There’s not much else to do or try right now, but if any new systemd updates fix this issue, I’ll be sure to let this thread know.

1 Like

Hello!

First of all, sorry for raising this thread.
I also had the same problem when shutting down the OS.
I use the latest version of Endeavouros+Kde-Plasma and sometimes I get these messages when shutting down.

My computer does not have NVDIA graphics card, do you know why this can happen?

Attached is this photo with evidence of the shutdown.
Failshutdown

Regards

I’m not sure how having an Nvidia card is related? My shutdown log on kde.

[ricklinux@kde-plasma ~]$ journalctl -e -b-1
Oct 09 13:08:48 kde-plasma systemd[1]: Stopping Record System Boot/Shutdown in UTMP...
Oct 09 13:08:48 kde-plasma systemd[1]: systemd-timesyncd.service: Deactivated successfully.
Oct 09 13:08:48 kde-plasma systemd[1]: Stopped Network Time Synchronization.
Oct 09 13:08:48 kde-plasma audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=system>
Oct 09 13:08:48 kde-plasma audit[14291]: SYSTEM_SHUTDOWN pid=14291 uid=0 auid=4294967295 ses=4294967295 msg='>
Oct 09 13:08:48 kde-plasma systemd[1]: systemd-update-utmp.service: Deactivated successfully.
Oct 09 13:08:48 kde-plasma systemd[1]: Stopped Record System Boot/Shutdown in UTMP.
Oct 09 13:08:48 kde-plasma audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=system>
Oct 09 13:08:48 kde-plasma systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully.
Oct 09 13:08:48 kde-plasma systemd[1]: Stopped Create Volatile Files and Directories.
Oct 09 13:08:48 kde-plasma audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=system>
Oct 09 13:08:48 kde-plasma systemd[1]: Stopped target Local File Systems.
Oct 09 13:08:48 kde-plasma systemd[1]: Unmounting /boot/efi...
Oct 09 13:08:48 kde-plasma systemd[1]: Unmounting /home...
Oct 09 13:08:48 kde-plasma systemd[1]: Unmounting /run/credentials/systemd-sysusers.service...
Oct 09 13:08:48 kde-plasma systemd[1]: Unmounting Temporary Directory /tmp...
Oct 09 13:08:48 kde-plasma systemd[1]: Unmounting /var/cache...
Oct 09 13:08:48 kde-plasma systemd[1]: Stopping Flush Journal to Persistent Storage...
Oct 09 13:08:48 kde-plasma systemd[1]: boot-efi.mount: Deactivated successfully.
Oct 09 13:08:48 kde-plasma systemd[1]: Unmounted /boot/efi.
Oct 09 13:08:48 kde-plasma systemd[1]: home.mount: Deactivated successfully.
Oct 09 13:08:48 kde-plasma systemd[1]: Unmounted /home.
Oct 09 13:08:48 kde-plasma systemd[1]: run-credentials-systemd\x2dsysusers.service.mount: Deactivated success>
Oct 09 13:08:48 kde-plasma systemd[1]: Unmounted /run/credentials/systemd-sysusers.service.
Oct 09 13:08:48 kde-plasma systemd[1]: tmp.mount: Deactivated successfully.
Oct 09 13:08:48 kde-plasma systemd[1]: Unmounted Temporary Directory /tmp.
Oct 09 13:08:48 kde-plasma systemd[1]: var-cache.mount: Deactivated successfully.
Oct 09 13:08:48 kde-plasma systemd[1]: Unmounted /var/cache.
Oct 09 13:08:48 kde-plasma systemd[1]: Stopped target Swaps.

Hello,
In my case the shutdown stays frozen, I have to press the button to turn it off.