System/Computer won't fully shutdown

[nmonic]

Intro

Hello.

Yesterday, I noticed that after shutting down my system, the shutdown process follows normally but the computer does not fully/completely shut down, it remains in a blackscreen with only the “on” LED turned on, the PC itself being completely unresponsive.

I have to “force” a shutdown by keeping the computer’s physical switch pressed for 3 seconds or so in order to turn off the computer.

Today I tried updating the kernel with the steps in the forum’s pinned message, but that didn’t fix the issue.

Restarting works with no problems.

List of things I have tried, but didn’t work:

• Installing the LTS Kernel, booting in it and shutting down. Same issue occurs.
• Using commands like sudo shutdown -h now and systemctl poweroff.
• Shutting down from KDE’s “log out” menu (the one that appears after pressing the physical shutdown button.

System Information

journalctl -b -1: https://pastebin.com/y0CiPKMz (last “shutdown” I did)

/etc/kernel/cmdline: nvme_load=YES nowatchdog rw rootflags=subvol=/@ root=UUID=bdf7b4cc-0758-443b-bc08-73171a3841ca amdgpu.ppfeaturemask=0xffffffff

$ fastfetch

OS: EndeavourOS x86_64
Kernel: Linux 6.15.3-arch1-1
DE: KDE Plasma 6.4.0
WM: KWin (Wayland)
WM Theme: Breeze
Theme: Breeze (Dark) [Qt], Breeze-Dark [GTK2], Breeze [GTK3]
Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
CPU: Intel(R) Core(TM) i7-2600 (8) @ 3.80 GHz
GPU: AMD Radeon RX 580 Series [Discrete]
Memory: 2.76 GiB / 7.70 GiB (36%)
Swap: 0 B / 8.80 GiB (0%)

[thefrog]

@nmonic

I have to “force” a shutdown by keeping the computer’s physical switch pressed for 3 seconds or so in order to turn off the computer.

Try doing this to turn off your system instead of physically doing so.

[Tip] Enable Magic SysRq Key (REISUB)

The Linux kernel authors have provided a very nice feature of issuing low-level commands to the kernel directly, regardless of the state the system is in. This is called the “Magic SysRq Key”, because these commands are issued by pressing the SysRq key on the keyboard (if you can’t find it, typically, it shares the same physical key as the Print Screen key, but on some laptops it can be elsewhere). A common use is to reboot when the computer freezes and becomes unresponsive due to some software…

@nmonic

Using commands like sudo shutdown -h now and systemctl poweroff.

perhaps if you could show/tell us what its telling you?

I notice you have as much swap as ram so do you hibernate with this system?

[nmonic]

I am currently writing in my phone.

Using REISUB seems to have caused the “root account” to be locked, and now I can’t access the system from any Kernel.

Well, I don’t usually hibernate. I read somewhere that the recommended swap was about this amount in case the system were to become unstable, if that could be the problem I am willing to disable it.

The booting sequence says:

Failed to mount /sysroot. 
Dependency failed Initrd Root File System. 
Dependency failed Mountpoints Configured in the Real Root. 

... [ok messages] ...

[Generating some error report]

Entering emergency mode... 

...

Cannot open access to console, the root account is locked. 

[thefrog]

@nmonic

if that could be the problem I am willing to disable it.

I doubt that has anything to do with your issue. I would leave it. I was just curious if maybe hibernation could be trying to happen when you shutdown.

maybe need to chroot into the system and see if you can post the journal. maybe something in there will help guide us to what the issue could be.

[nmonic]

The system is currently innaccessible.

I can’t mount the root partition in the Live USB I have. It results in a “can’t read superblock” error.

[thefrog]

@nmonic

I have. It results in a “can’t read superblock” error.

you should run a disk check on the system sounds like you could have a corrupt file system or a failing disk. this can happen when you physically power off your machine which is why I suggested to use reisub

[nmonic]

This sub-issue was fixed after running sudo btrfs rescue zero-log /dev/sda2.

Shutdown issue persists.

---

This problem occurred after I used REISUB.

I have ran btrfs check --readonly /dev/sda2.

It resulted in no errors. I am not sure which other command can repair filesystem errors in BTRFS.

Edit:

I have tried running sudo btrfs rescue super-recover /dev/sda2 and it says “all supers are valid”.

[nmonic]

After fixing the booting issue, I tried REISUB, but it did nothing; the computer restarted as normal.