Recovering journal, OS not booting

vCordero · 2024-10-05 20:26:04

The OS is currently not booting, as it stays constantly showing

/dev/nvmeXXXX: recovering journal
/dev/nvmeXXXX: clean, (number)/10240000 files, (number)/40960000 blocks

When I use non-quiet booting, it says

[ OK ] ...
...
[ OK ] Reached target Trusted Platform Module.
[ OK ] Finished Coldplug All udev Devices.

And gets stuck there.

I have dual boot with Windows, and booting with Windows have no problems.
Also, this is on a laptop.

The last thing I did was a general package update with

 sudo pacman -Syu

And I don't remember any difficulties in the shutdown.

I'd appreciate some help!

seth · 2024-10-05 20:39:26

I have dual boot with Windows, and booting with Windows have no problems.

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Can you still boot the multi-user.target (2nd link below)?

vCordero · 2024-10-05 20:59:51

I disabled the hibernation and fast-start, but the outcome is the same.

I noticed that de underscore starts blinking when showing "recovering journal", but after some seconds it stops, as it is stuck.

When applying the multi-user.target kernel parameter it happens the same, so the problem persists.

Last edited by vCordero (2024-10-05 22:38:22)

gromit · 2024-10-05 23:45:12

Do you happen to have a nvidia card in your system that uses the proprietary drivers?

vCordero · 2024-10-06 00:34:22

no, my laptop does not have a GPU, just integrated intel graphics (i7 13th gen)

Last edited by vCordero (2024-10-06 00:34:38)

gromit · 2024-10-06 00:46:09

Does it work again after you downgrade the kernel or switch to linux-lts?

vCordero · 2024-10-06 02:59:19

I downgraded from linux 6.11.1 to linux 6.10.6 (the same with linux-headers) and now it works as normal. Thank you!

I might ask one more question, is there a way to know when this problem will "be gone"? Like, when I will be able to update to a new version safely? Or just trial and error?

Thanks again for your time

seth · 2024-10-06 06:16:44

We first need to know what the problem actually is.
Enable the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) and use it to reboot the failing system (or frenetically press ctrl+alt+del but don't push the power button until the system restarts) and post the journal of such failing boot, eg.

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

for the previous ("-1") one.

Arch Linux

#1 2024-10-05 20:26:04

Recovering journal, OS not booting

#2 2024-10-05 20:39:26

Re: Recovering journal, OS not booting

#3 2024-10-05 20:59:51

Re: Recovering journal, OS not booting

#4 2024-10-05 23:45:12

Re: Recovering journal, OS not booting

#5 2024-10-06 00:34:22

Re: Recovering journal, OS not booting

#6 2024-10-06 00:46:09

Re: Recovering journal, OS not booting

#7 2024-10-06 02:59:19

Re: Recovering journal, OS not booting

#8 2024-10-06 06:16:44

Re: Recovering journal, OS not booting

Board footer