"Failed to unmount /oldroot/..." when shutting down

loqs · 2018-03-25 10:02:23

berbae wrote:

The 'shutdown' hook didn't work for me either.
I choose instead to mask 'mkinitcpio-generate-shutdown-ramfs.service', but I still get:
...
mars 24 23:24:54 arch64 systemd[1]: Shutting down.
mars 24 23:24:54 arch64 kernel: systemd-shutdow: 32 output lines suppressed due to ratelimiting
...
So something is still not normal here.

You could open a new issue upstream if you think it is important enough. I see the same with the patches cherry-picked from 239 for the original issue.

Batou · 2018-03-26 18:34:04

I'm not sure if my bug is related to this one but on my machine a shutdown results in a restart about 50% of the time.

This has been bothering me for about a week and I cannot figure out what's going on. In a nutshell, if I initiate a shutdown from DE or from the tty, about 50% of the time my computer will restart instead of powering down. To make sure that my HW isn't at fault, I tried shutting down from Windows and (older) Ubuntu and they shut down fine.

During the shutdown sequence, I see a bunch of "shutdown .... failed to unmount ... " error messages pass quickly (as many have reported here).

Are the two related?

I only have 4 ACPI errors in the logs (those have been around since 4.14.xx) and don't have any other issues.

loqs · 2018-03-26 18:38:34

@Batou use the systemd PKGBUILD from testing add the commits from https://bbs.archlinux.org/viewtopic.php … 2#p1775582 that should stop the messages from appearing then you can see if the other issues still remains.

Batou · 2018-03-26 19:01:33

loqs wrote:

@Batou use the systemd PKGBUILD from testing add the commits from https://bbs.archlinux.org/viewtopic.php … 2#p1775582 that should stop the messages from appearing then you can see if the other issues still remains.

Thanks Ioqs! Will give that a try when I get home.

Batou · 2018-03-26 22:32:54

loqs wrote:

@Batou use the systemd PKGBUILD from testing add the commits from https://bbs.archlinux.org/viewtopic.php … 2#p1775582 that should stop the messages from appearing then you can see if the other issues still remains.

Well, just compiled everything and tried shutting down twice... it works as intended! Fingers crossed that this fixed it. Hope this stuff rolls back into core packages. Thanks again Ioqs... your help and expertise is much appreciated!

darose · 2018-04-24 01:04:18

What's the final resolution on this issue? Fixed upstream and we're waiting for a new release of systemd?

I'm still seeing loads of these unnecessary oldroot messages every time I shut down, and would like to be rid of them. Although it seems from reading this thread that adding a "shutdown" hook to mkinitcpio could accomplish this, that's not really the proper way to handle it. (The "shutdown" hook is deprecated, IIUC.)

Anyone know the final word on this?

Pryka · 2018-04-24 06:16:33

darose wrote:

Fixed upstream and we're waiting for a new release of systemd?

Yep, wait for version with included fix. 239 probably.

Last edited by Pryka (2018-04-24 06:16:45)

ratcheer · 2018-04-24 19:22:17

Well, I've been getting the same messages at shutdown for the past several weeks, but since there appears to be no harm done, I just ignore them.

Tim

Cknight70 · 2018-06-07 16:42:41

238.133 came out a few days ago and this bug is still present.
Reading the GitHub thread, did Arch never add the shutdown improvements patch or is it something else?

https://github.com/systemd/systemd/issu … -394269363

loqs · 2018-06-07 17:27:21

@Cknight70 no one asked for the commits to be included and upstream has not ported them to the systemd-stable as the issues are cosmetic. https://bugs.archlinux.org/task/58867
I expect those concerned about the issue from this thread or https://bbs.archlinux.org/viewtopic.php?id=234329 would have asked the maintainers to cherry-pick the commits.
I finally did it as there seems to be a duplicate thread about it every few weeks and a definitive will fix or will not fix from the maintainers will hopefully stop users asking why is it not fixed.
Edit:
Fixed in systemd 238.133-2

Last edited by loqs (2018-06-08 22:21:59)

papavlos · 2018-06-11 18:44:57

loqs wrote:

Fixed in systemd 238.133-2

Not completely. From a dozen of lines of errors still two remain, both in my desktop install as well as in virtualbox machine:

sd-umount[466]: Failed to unmount /oldroot: Device or resource busy
shutdown[1]: Unmounting '/oldroot' failed abnormally, child process 466 aborted or exitet non-zero.

The workaround of adding 'shutdown' to HOOKS still applies, unfortunately...

Last edited by papavlos (2018-06-11 18:45:31)

loqs · 2018-06-11 20:27:08

456b2199f6ef0378da007e71347657bcf83ae465 ~~and b93618644bf24bc0cd87adb1346955d783f6f9b8~~ were not included in the cherry-picks arch applied.
Edit:
only 456b2199f6ef0378da007e71347657bcf83ae465 is missing.

diff --git a/trunk/PKGBUILD b/trunk/PKGBUILD
index 128af94..7a69905 100644
--- a/trunk/PKGBUILD
+++ b/trunk/PKGBUILD
@@ -76,6 +76,8 @@ _backports=(
   '8645ffd12b3cc7b0292acd9e1d691c4fab4cf409'
   # umount: Don't bother remounting api and ro filesystems read-only
   'e783b4902f387640bba12496936d01e967545c3c'
+  # umount: Reduce log level of unmount failures that will be attempted again later in shutdown
+  '456b2199f6ef0378da007e71347657bcf83ae465'
 )
 
 _reverts=(

Last edited by loqs (2018-06-11 20:51:19)

papavlos · 2018-06-15 09:05:38

After systemd 238.133-4 update all annoying messages have gone.
No need to keep 'shutdown' in HOOKS.

Thanks!

Last edited by papavlos (2018-06-15 09:06:42)

haigioli · 2019-09-09 21:57:39

After upgrading to systemd-243.0-1, the 'Failed to unmount /oldroot...' messages have come back. Has anyone else noticed this?

After checking around, it appears to be a regression.

Last edited by haigioli (2019-09-09 21:59:32)

TheAifam5 · 2019-10-04 10:39:16

Issue still present on version 243.51-1. Adding "shutdown" to HOOKS does not solve the issue.

jpegxguy · 2019-10-18 09:59:23

haigioli wrote:

After upgrading to systemd-243.0-1, the 'Failed to unmount /oldroot...' messages have come back. Has anyone else noticed this?
After checking around, it appears to be a regression.

I have noticed it and it was immediately apparent that it happened when I upgraded to 243.
I thought I'd be lost in threads with old instances of the bug, but Arch BBS did not disappoint.

I haven't found a workaround yet

The problem is that I can't see any logs. AFAIK journald gets sent SIGTERM before the /oldroot stuff happens

I see no open issue in systemd's github about it either.

Last edited by jpegxguy (2019-10-18 10:04:34)

d_fajardo · 2019-10-18 10:09:14

Bug has been reported for 243: https://bugs.archlinux.org/task/63697

jpegxguy · 2019-10-18 10:17:19

Thanks for finding that, I'll also keep an eye on it.

Also Manjaro thread here:
https://forum.manjaro.org/t/sd-umount-f … oot/102412

The ratelimiting is normal, I think. It's just a load of messages on shutdown about filesystem handling that you're not supposed to see. I'm not an expert though

dkadioglu · 2019-12-11 12:10:33

I have the same error messages regarding the failed unmount of /oldroot. I opened a bug report for systemd upstream: https://github.com/systemd/systemd/issues/14298
As mentioned there, Lennart Poettering assumes, that this should have something to do with initrd.
Are there any news about this? Was anyone able to fix this? What can I do to help debugging this?

V1del · 2019-12-11 12:17:56

This has heavily diverged from what the original topic was about, it's quite unlikely you still are affected by the same cause as what originally prompted this thread. If you still see something similar to this, please open up your own thread and post details about your setup (your initramfs/mkinitcpio config, enabled services, LVM/LUKS, journals after reproducing)

At the very least, follow this recent bug report: https://bugs.archlinux.org/task/63697

Closing

Arch Linux

#26 2018-03-25 10:02:23

Re: "Failed to unmount /oldroot/..." when shutting down

#27 2018-03-26 18:34:04

Re: "Failed to unmount /oldroot/..." when shutting down

#28 2018-03-26 18:38:34

Re: "Failed to unmount /oldroot/..." when shutting down

#29 2018-03-26 19:01:33

Re: "Failed to unmount /oldroot/..." when shutting down

#30 2018-03-26 22:32:54

Re: "Failed to unmount /oldroot/..." when shutting down

#31 2018-04-24 01:04:18

Re: "Failed to unmount /oldroot/..." when shutting down

#32 2018-04-24 06:16:33

Re: "Failed to unmount /oldroot/..." when shutting down

#33 2018-04-24 19:22:17

Re: "Failed to unmount /oldroot/..." when shutting down

#34 2018-06-07 16:42:41

Re: "Failed to unmount /oldroot/..." when shutting down

#35 2018-06-07 17:27:21

Re: "Failed to unmount /oldroot/..." when shutting down

#36 2018-06-11 18:44:57

Re: "Failed to unmount /oldroot/..." when shutting down

#37 2018-06-11 20:27:08

Re: "Failed to unmount /oldroot/..." when shutting down

#38 2018-06-15 09:05:38

Re: "Failed to unmount /oldroot/..." when shutting down

#39 2019-09-09 21:57:39

Re: "Failed to unmount /oldroot/..." when shutting down

#40 2019-10-04 10:39:16

Re: "Failed to unmount /oldroot/..." when shutting down

#41 2019-10-18 09:59:23

Re: "Failed to unmount /oldroot/..." when shutting down

#42 2019-10-18 10:09:14

Re: "Failed to unmount /oldroot/..." when shutting down

#43 2019-10-18 10:17:19

Re: "Failed to unmount /oldroot/..." when shutting down

#44 2019-12-11 12:10:33

Re: "Failed to unmount /oldroot/..." when shutting down

#45 2019-12-11 12:17:56

Re: "Failed to unmount /oldroot/..." when shutting down

Board footer