Fedora 42 won’t shut down properly, shows unmount and swap errors

Ask Fedora
, , , ,
1

Today I installed Fedora 42 but after a while I encountered a problem.

When I power on the laptop, it boots normally, but after about a minute, the Acer logo appears again, almost as if the system is trying to shut down on its own. At that point, it freezes and becomes unresponsive. The first time I hold the power button to force a shutdown this error appears on screen:

[FAILED] Failed unmounting boot-efi.mount – /boot/efi.
[FAILED] Failed unmounting var-lib-nfs-rpc_pipefs.mount – RPC Pipe File System.
[FAILED] Failed unmounting boot.mount – /boot. 
[FAILED] Failed to start plymouth-poweroff.service – Show Plymouth Power Off Screen.
[FAILED] Failed unmounting home.mount – /home.
[FAILED] Failed unmounting tmp.mount – Temporary Directory /tmp.
[FAILED] Failed to start systemd-vcosole-setup.service – Virtual Console Setup.
[FAILED] Failed deactivating swap dev-zram0.swap – Compressed Swap on/dev/zram0.
[FAILED] Failed deactivating swap dev-disk-by\x2ddiskseq-2.swap – /dev/disk/by-diskseq/2.
[!!!!!!] Failed to execute shutdown binary.

Then I have to press the shutdown button a second time to turn off the laptop.

Sorry for the formatting, I’m on my phone.

2

Try holding the shift key while powering-on the PC. You should see a boot menu appear with three kernel choices. You can try a different kernel and/or you can edit the kernel command line to remove rhgb quiet so that you can see what service is failing when you attempt to boot the computer.

You might also try adding systemd.unit=multi-user.target to the kernel parameter list. That might help if the login screen is preventing some important messages from showing. If you can get signed-in, then run sudo journalctl to review the system log messages or sudo systemctl --failed to see if there are any services that are reporting failures.

1 Like
3

I just tried a different kernel but I get the same problem. After a minute the laptop starts to shutdown and then freezes, and the error messages pop up when I try to shutdown manually.

I tried sudo journalctl but the output is several hundreds lines long and I can’t copy it or send it to my phone before the laptop freezes. I saw many many strange errors.

I think I found out why. I bought a new SSD for this laptop, the WD Blue SA510, and I just saw online that there is a flaw in the firmware that needs a critical update and may cause the drive to brick. I think this is the issue, so I’ll have to figure out how to update it. Thanks for your help.

1 Like
4

You can try something like sudo journalctl --since=-2min > bootlog.txt to save the output to a file. cat bootlog.txt | fpaste might work to upload the logs to a website where you would have time to inspect it (or you could use a Live image). That website will automatically delete anything uploaded after 24 hours.

For updating your SDD, you might try fwupdmgr:

5

I used a Live image and this is the output of sudo journalctl -b: "sudo journalctl -b" output - Pastebin

Ouput of sudo journalctl -k: "sudo journalctl -k" output - Pastebin

I’ll try fwupdmgr, thank you.

6

The journal collects massive amounts of detail. man journalctl will show you many “filter” options that (with some effort) should allow you to isolate entries relevant to your issue. See: Linux Handbook journalctl Command for examples.

7

Thank you for the tip. The problem is I don’t know what to look for or what could be relevant to my problem. I’ll edit my previous responce and add a link to the journalctl output with only kernel messages, that should make it shorter.

8

Sorry, I should have stated that more clearly. You could use the Live image to inspect the logs if you saved them to a text file previously.[1] Running sudo journalctl -b directly from the Live image won’t work because it will see the logs of the Live system, not the logs from your system.

  1. There is a way to access the logs of the real system from the Live image, but it is a little complicated. ↩︎

9

Oh, sorry for misunderstanding. I get it now, thanks.