You are not logged in.
Pages: 1
I'm having the weirdest issue booting my laptop. After a regular reboot it just sat at the bgrt screen doing nothing. There's nothing in the logs after the reboot either.
My system is a 9-year-old i5 ideapad with integrated Intel graphics and a single SATA SSD split between Windows and Arch, which is installed across btrfs subvolumes (@root, @var & @home) on a LUKS encrypted partition. My set up works on systemd and systemd-boot.
What I'm able to do:
- Select the Windows Bootloader from the UEFI boot menu and boot into Windows.
- Select the Arch ISO USB drive and boot into Arch
- Switch between systemd-boot, GRUB and Windows boot entries
- From the archiso, decrypt the LUKS partition, mount all the 3 subvolumes and the EFI partition, arch-chroot into my system, run pacman and any other cli packages, edit configs, su into my user, etc.
What I've tried/checked:
- fstab is fine
- reinstalled systemd with deps
- reinstalled plymouth
- upgraded kernel
- installed and configured GRUB
- removed systemd-boot from the EFI partition and ran `bootctl install`
- checked with efibootmgr, removed and readded boot entry
- removed `retbleed=stuff quiet splash` from the kernel parameters
- checked the EFI partition for errors
- obviously, ran mkinitcpio several times in the process
Nothing helped and nothing changed. Neither systemd-boot nor GRUB manage to boot the system. However, at one point I booted without a `grub.cfg` and was presented with the GRUB console, and was able to type.
Trying to boot from there by hand actually launches the boot process, but it breaks on switching root and throws me into emergency mode in a looped state where it says it can't open the console because the root account is locked. Changing root's password in chroot didn't help. I've yet to try fixing the cryptomount modules issue in GRUB and to make sure I enter all the necessary parameters with no typos in the boot command in the GRUB console, but I'm eager to understand where this whole story is stemming from. Especially since it doesn't even reach the stage where it starts logging anything without manual intervention.
Any suggestions greatly appreciated. Thank you.
Last edited by somepaulo (2025-09-21 17:39:49)
Offline
Interesting. I experienced the exact same symptoms after trying to reboot after upgrading systemd 258-1 -> 258-2
Also using systemd-boot as bootloader. Like you, able to boot from the archiso without any problems. arch-chroot fine.
Reinstalled systemd, kernel, reinstalled systemd-boot using 'bootctl install' without any changes.
Installed GRUB, only to find it failed also.
Installed and configured refind. And the PC boots up just fine...
I haven't had the time to start rolling back packages yet as I have some real-life issues to work on. But somewhat reassuring to know that somebody else is experiencing similar issues.
Offline
It may well be this issue
Offline
It may well be this issue
Yes, seems like it.
Downgrading systemd, systemd-libs and systemd-sysvcompat to version 257.9-1 solves the issue for me. Holding these back until the fix gets merged and trickles down to the repos.
Last edited by somepaulo (2025-09-21 17:39:08)
Offline
Pages: 1