Arch Linux

Beuman

Member

Registered: 2018-06-10

Posts: 25

Cannot boot today : device /dev/ArchGroup/root NOT FOUND. skipping fsc

Hello. Today I couldn't boot, yesterday I just did an update, nothing wild.

Using GRUB, LVM on LUKS, Linux 6.4.4.
In Hooks, I moved 'block' before 'autodetect', then

mkinicpio -P

(first got an error, nothing in /boot, had to do a pacman -Syu). Rebooted : No success.

I can connect that computer to the internet to upload files but if you don't mind I have photo right now :

mkinitcpio.conf :
https://imgur.com/5PFdB9J.png

grub.cfg :
https://imgur.com/EVnzs3y.png

fstab :
https://imgur.com/tvN9oFn.png

Last edited by Beuman (2023-07-26 02:06:23)

Beuman

Member

Registered: 2018-06-10

Posts: 25

Re: Cannot boot today : device /dev/ArchGroup/root NOT FOUND. skipping fsc

So I did :

grub-install --target=x86_64-efi --efi-directory=esp --bootloader-id=GRUB

Rebooted : Same issue.

wanted to use mkinitcpio -P "
I get
/lib/modules/6.4.4-arch1-1' is not a valid directory

meanwhile when I do ls usr/lib/modules I get a different kernel version :
6.4.8-arch1-1

Doing :

mkinitcpio -p linux

Gives same error.
uname -r : 6.3.9-arch1-1
pacman -Q and ls /usr/lib/modules : 6.4.8-arch1-1

Last edited by Beuman (2023-08-07 03:16:15)

jonno2002

Member

Registered: 2016-11-21

Posts: 868

Re: Cannot boot today : device /dev/ArchGroup/root NOT FOUND. skipping fsc

(first got an error, nothing in /boot, had to do a pacman -Syu). Rebooted : No success.

what was the actual error ? if theres literally nothing in /boot then you didnt have your efi/boot partition mounted, and then when you did a Syu you would have populated the /boot on your encrypted root partition which is probably the cause of your kernel mismatch.

you need to boot off the install media and mount your encrypted root to /mnt then after that you need to mount your boot/efi partition to /mnt/boot and then 'arch-chroot /mnt' then run a Syu followed by 'mkinitcpio -P' and i guess for complete-ness install grub again

grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB

then reboot and hopefully all is well again.

EDIT: ive just realised after writing that and thinking about it for a while thats its highly unlikely that /boot could not have been mounted, but reguardless of that fact my instructions SHOULD still work, and i have no idea what you did to cause this problem....

EDIT2: you probably also want to re-generate your grub config too, totally forgot about that sorry...

grub-mkconfig -o /boot/grub/grub.cfg

Last edited by jonno2002 (2023-08-07 06:48:52)