Shutdown:Failed to unmount /oldroot

General system Kernel, boot, graphics & hardware
1

when I shutdown the shutdown process hangs permanently (at the end) it shows following error

Shutdown:Failed to unmount /oldroot

any idea?

Operating System: EndeavourOS
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
Kernel Version: 5.8.5-arch1-1
OS Type: 64-bit
Processors: 8 × AMD FX™-8350 Eight-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: GeForce GT 630/PCIe/SSE2
GPU Driver: nvidia-dkms (450.661)

journalctl -b -1 (relevant logs)
Sep 04 19:45:16 user sddm[818]: Authentication error: “Process crashed”
Sep 04 19:45:16 user sddm[818]: Auth: sddm-helper crashed (exit code 15)
Sep 04 19:45:16 user sddm[818]: Authentication error: “Process crashed”
Sep 04 19:45:16 user sddm[818]: Auth: sddm-helper exited with 15
Sep 04 19:45:16 user kiod5[21537]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule*
Sep 04 19:45:17 user sddm[818]: Signal received: SIGTERM
Sep 04 19:45:18 user sddm[818]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
Sep 04 19:45:18 user systemd[1]: sddm.service: Succeeded.
Sep 04 19:45:18 user systemd[1]: Stopped Simple Desktop Display Manager.
Sep 04 19:45:19 user systemd[1159]: at-spi-dbus-bus.service: Succeeded.
Sep 04 19:45:19 user systemd[1159]: Stopped Accessibility services bus.
Sep 04 19:45:19 user org.gna.home.a2jmidid[1415]: Cannot read socket fd = 12 err = Success
Sep 04 19:45:19 user org.gna.home.a2jmidid[1415]: CheckRes error
Sep 04 19:45:19 user org.gna.home.a2jmidid[1415]: JackSocketClientChannel read fail
Sep 04 19:45:19 user org.gna.home.a2jmidid[1415]: Server is not running
Sep 04 19:45:20 user systemd[1]: Reached target Unmount All Filesystems.
Sep 04 19:45:20 user systemd[1]: Reached target Power-Off.
Sep 04 19:45:20 user systemd[1]: Shutting down.
Sep 04 19:45:20 user systemd-shutdown[1]: Syncing filesystems and block devices.
Sep 04 19:45:20 user systemd-shutdown[1]: Sending SIGTERM to remaining processes…
Sep 04 19:45:20 user systemd-journald[282]: Journal stopped

2

It looks like the PC is shutting down, just not powering off:

Possibly you have a process which is refusing to quit, or, if this worked previously, there may be a regression in the kernel/systemd/etc.

To try and rule out the kernel, try linux-lts and see what happens.

1 Like
3

strange, with the LTS kernel the error is gone but my network adapter is no longer available …
same thing happens with linux-zen shutdown error is gone but no network

ifconfig shows only lo:
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536

adapter:
Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

log:
Sep 06 13:38:29 hounddog systemd[1154]: eos-update-notifier.service: Main process exited, code=exited, status=1/FAILURE
Sep 06 13:38:29 hounddog systemd[1154]: eos-update-notifier.service: Failed with result ‘exit-code’.
Sep 06 13:38:29 hounddog systemd[1154]: Failed to start EOS update notifier service.

current 5.8.7-arch1-1 has no problems with the network even after yesterday’s update there were no problems except the shutdown bug

after intallation I already did:
sudo mkinitcpio -p linux-lqx
sudo grub-mkconfig -o /boot/grub/grub.cfg
headers are installed for both

how do I get the network working for LTS or ZEN (official)?

4

got it … solved by using the r8168-dkms driver from aur
yay -S r8168-dkms

5

now, the error also occurred with a different kernel
it seems this was caused by my swapfile …
after i removed it the error has disappeared

is a system swap still useful (16GB ram)?

that’s how I created my swapfile
dd if=/dev/zero of=/swapfile bs=10M count=512 status=progress
chmod 600 /swapfile
mkswap /swapfile
swapon /swapfile

/etc/fstab
/swapfile none swap defaults,noatime 0 0