shutdown hangs - umount: /oldroot/sys: target is busy.

ooXei1sh · 2022-01-16 06:38:29

I've installed arch on a new pc build but I'm unable to shutdown.
It hangs with output:

Unmounting all devices.
umount: /oldroot/sys: target is busy.
Detaching loop devices.
Disassembling stacked devices.
[ XXX.XXXXXX] reboot: Power down

At this point it freezes and I have to press and hold the power button until the pc turns off.

I've found a similar looking issue here: https://bbs.archlinux.org/viewtopic.php?id=260113

I think I am also using the proprietary nvidia drivers but I'm not sure what that has to do with the shutdown routine.

Any help trouble shooting this would be much appreciated.

Last edited by ooXei1sh (2022-01-16 06:42:25)

seth · 2022-01-16 08:36:49

I think I am also using the proprietary nvidia drivers

Did you install them? Are they loaded? What makes you "think" but not "certain"?
Let's assume you looled at lsmod and figured that the nvidia modules are loaded: does unloading them (from the mutli-user.target/console) before shutting down allow you to shutdown/reboot?

ooXei1sh · 2022-01-16 15:38:04

Yes I installed nvidia by running "pacman -Syu --noconfirm nvidia". I installed that one based on what I read here: https://wiki.archlinux.org/title/Xorg#Installation

I wasn't sure how to tell if a module is actually loaded or not but assuming the output of lsmod shows loaded modules I do get some nvidia results:

~ $ lsmod |grep [n]vi
nvidia_drm 73728 5
nvidia_uvm 2560000 0
nvidia_modeset 1155072 7 nvidia_drm
nvidia 36970496 296 nvidia_uvm,nvidia_modeset
i2c_nvidia_gpu 16384 0

I wasn't certain if just installing the nvidia package actually installed/loaded the needed drivers/modules.
I thought maybe I would need to configure something or run a command to activate them.

I'm not very familiar with unloading modules. Do I just run `modprobe -r nvidia` from a terminal and try a restart?
Will I need to reload those modules later? What is the mutli-user.target/console?

seth · 2022-01-16 16:54:50

Do I just run `modprobe -r nvidia` from a terminal and try a restart?

Yes, but there must be no display server running, otherwise this is going to fail (see the 2nd link below on how to isolate or boot the multi-user.target)

Will I need to reload those modules later?

No, that's a transient change and the module will automatically be reloaded w/ the next boot.

ooXei1sh · 2022-01-16 17:48:20

Ok, from my GUIs terminal emulator I ran:

systemctl set-default multi-user.target

Then I forced a restart and it booted w/o GUI into the multi-user.target/console terminal. No prob.

Then I ran these commands:

sudo modprobe -r nvidia_drm
sudo modprobe -r nvidia_uvm
sudo modprobe -r i2c_nvidia_gpu

Then checked that no nvidia modules in the output from running:

lsmod |grep [n]vid

This checked out as no nvidia modules were displayed.
Then I set the target back to graphical are restarted:

systemctl set-default graphical.target
sudo shutdown -Hr now

Upon restart I see these lines at the bottom of my screen and it freezes again:

[ OK ] Finished System Reboot.
[ OK ] Reached target System Reboot.
Unmounting all devices.
Detaching loop devices.
Disassembling stacked devices.
[ XXX.XXXXXX] reboot: Restarting system

It hangs here and fails to reboot. So this appears to be some progress as the "/oldroot/sys: target is busy" message is no longer displayed.
But the system still freezes requiring me to press the reset button or press and hold the power button.

Is there any way to figure out what is causing it to hang up there?

seth · 2022-01-16 21:05:37

Smells acpi…
https://wiki.archlinux.org/title/Kernel_parameters
You could try eg. "reboot=bios", "reboot=efi" or "reboot=pci", see https://raw.githubusercontent.com/torva … meters.txt

Also try the lts kernel (you'll also want the nvidia-lts package)

Ceterum censeo: if there's a parallel windows installation, see the 3rd link below…

ooXei1sh · 2022-01-16 23:03:32

Ok, a bit difficult to follow what you're saying I should try here.
I'm using systemd-boot so I updated the line with options here (assuming those options are the kernel parameters?):

sudo vim /boot/loader/entries/arch.conf

So now that file looks like this:
title Arch Linux
linux /vmlinuz-linux
initrd /amd-ucode.img
initrd /initramfs-linux.img
options root=PARTUUID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX reboot=efi

After that I forced a restart and then restarted again after the forced restart and it actually restarted without any manual interventions.

So the restart appears to be solved! But when I power down it still freezes with this output:

[ OK ] Finished System Power Off.
[ OK ] Reached target System Power Off.
[ XX.XXXXXX] ACPI CPPC: PPC check channel failed for ss: 0. ret=-110
[ XX.XXXXXX] ACPI CPPC: PPC check channel failed for ss: 0. ret=-110
[ XX.XXXXXX] sd-umoun[XXXX]: Failed to unmount /oldroot: Device of resource busy
[ XX.XXXXXX] sd-umoun[XXXX]: Failed to unmount /oldroot/sys: Device of resource busy
[ XX.XXXXXX] reboot: Power down

I'm only running arch linux there is no parallel windows installation.

Last edited by ooXei1sh (2022-01-17 01:57:36)

seth · 2022-01-17 15:05:57

I've installed arch on a new pc build

What board?
Are there BIOS updates available?
You could try to lie to the BIOS, try to pass

acpi_osi=! acpi_osi="Windows 2015"

to the kernel

ooXei1sh · 2022-01-17 17:04:02

The board I have now is a replacement for the exact same board that died last week after one day.

MB: X570 AORUS ELITE WIFI (rev. 1.1) (https://www.gigabyte.com/us/Motherboard … IFI-rev-1x)
CPU: AMD Ryzen 5 5600X
GPU: ASUS TUF Gaming GeForce GTX 1660 Super

I skipped updating the BIOs on the first board and my arch install was actually very smooth and seemed super stable.
Unfortunately when I left the machine on overnight and checked it in the morning the fans were spinning at full speed and the board was dead.
So probably some kind of suspend/hibernate issue that fried it? I dunno.

When I got the replacement board (same exact board) I Q-Flashed BIOS version "F30". That is the version listed next to my chip (Ryzen 5 5600X).
I re-partitioned my ssd and did a fresh install and made sure to setup a swap partition for suspend/hibernate but that still doesn't work right either.

Like I said I already updated the BIOS but there is a newer BIOS version.
Would you suggest trying to Q-Flash the newest BIOS version?

ooXei1sh · 2022-01-17 20:48:24

Adding the following to my arch.conf options resulted in a failed boot to blank screen didn't even see any [ OK ] type bootup spew, screen just goes blank after the systemd-boot options screen.

acpi_osi=! acpi_osi="Windows 2015"

I had to recover from my install medium and mount the ssd partitions so I could remove those options to get back to my desktop again.

seth · 2022-01-17 21:15:01

When trying kernel parameters you want to use the commandline editor of your bootloader - don't edit stuff on the disk
https://wiki.archlinux.org/title/Kernel_parameters

So probably some kind of suspend/hibernate issue that fried it?

That should™ not be possible, but did you expect the systmem to suspend or hibernate?
Also if "my arch install was actually very smooth and seemed super stable" does that mean "including shutdown and suspend"? Esp. since it "died last week after one day"??

For https://www.reddit.com/r/gigabytegaming … rus_elite/ it seems to have turned out to be an assembly issue and down to the CPU.
In light of your previous incident I wonder whether you might face a similar situation (maybe the board design is prone to such)

ooXei1sh · 2022-01-17 22:59:40

The issues appear to be resolved after updating to the latest BIOS (F36e). I unplugged the graphics card before q-flash but left everything else attached to the board.

I was able to remove reboot=efi kernel param and still the restart, shutdown, suspend and hibernate appear to be working as expected now!

For historical purposes I'll mention the three settings I've enabled in the BIOS (The only settings I touched in there):

Enable SVM
Enable ErP
Enable X.M.P.

Arch Linux

#1 2022-01-16 06:38:29

shutdown hangs - umount: /oldroot/sys: target is busy.

#2 2022-01-16 08:36:49

Re: shutdown hangs - umount: /oldroot/sys: target is busy.

#3 2022-01-16 15:38:04

Re: shutdown hangs - umount: /oldroot/sys: target is busy.

#4 2022-01-16 16:54:50

Re: shutdown hangs - umount: /oldroot/sys: target is busy.

#5 2022-01-16 17:48:20

Re: shutdown hangs - umount: /oldroot/sys: target is busy.

#6 2022-01-16 21:05:37

Re: shutdown hangs - umount: /oldroot/sys: target is busy.

#7 2022-01-16 23:03:32

Re: shutdown hangs - umount: /oldroot/sys: target is busy.

#8 2022-01-17 15:05:57

Re: shutdown hangs - umount: /oldroot/sys: target is busy.

#9 2022-01-17 17:04:02

Re: shutdown hangs - umount: /oldroot/sys: target is busy.

#10 2022-01-17 20:48:24

Re: shutdown hangs - umount: /oldroot/sys: target is busy.

#11 2022-01-17 21:15:01

Re: shutdown hangs - umount: /oldroot/sys: target is busy.

#12 2022-01-17 22:59:40

Re: shutdown hangs - umount: /oldroot/sys: target is busy.

Board footer