PC died during kernel update, now I can't boot anymore

General system Kernel, boot, graphics & hardware
21 
[root@EndeavourOS home]# df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda6       148G  127G   14G  91% /
udev            1.9G     0  1.9G   0% /dev
shm             2.0G     0  2.0G   0% /dev/shm
run             2.0G  176M  1.8G   9% /run
tmp             2.0G     0  2.0G   0% /tmp
airootfs         10G   89M   10G   1% /etc/resolv.conf
22

Try reinstalling grub the way @pebcak suggested. Maybe it is trying to boot from the wrong place?

I am little worried that something you did trying to fix it made it more broken.

2 Likes
23

Wouldn’t it be good to remove that “extra install” as well while @workingsea is at it ?

1 Like
24

I wouldn’t remove anything until we figure out what is going on. You wouldn’t want to accidentally delete the actual data due to a symlink or something.

It is also possible that is his install and something else is wrong.

3 Likes
25

Just to be sure this time, grub-install --target=i386-pc /dev/sda, right?

1 Like
26

Grub installing to the correct place fixed it

2 Likes
27

Sounds like an impossible possibility :sweat_smile:

1 Like
28

Now you should try to figure out why you have a /boot/usr and /boot/etc.

What is in those directories? Are they links to the main directories or separate copies?

2 Likes
29

Now it seems like there’s nothing unusual?

[lain@machine ~]$ ls /boot/
grub  intel-ucode.img
[lain@machine ~]$ ls -a /boot/
.  ..  grub  intel-ucode.img
[lain@machine ~]$
30

This happened to me on my Arch machine not too long ago. I had to use an “Arch based” boot usb so I could mount the hard drive your OS is on then arch-chroot into it so I could re-run pacman -Syu and let it reinstall the kernels. In the end, it didn’t take too long.

Along the way, I had to delete a log file as well, an error message directed me to do so.

1 Like
31

The fact that you have no kernels is unusual

How did you create that chroot?

1 Like
32

Where are the rest of it?

The kernel images and stuff? Did you remove them all?

Mine:

ls -a /boot/
.  ..  initramfs-linux-lts-fallback.img  initramfs-linux-lts.img  initramfs-linux-zen-fallback.img  initramfs-linux-zen.img  intel-ucode.img  vmlinuz-linux-lts  vmlinuz-linux-zen

No grub in mine, because systemd-boot.

1 Like
33

They are probably in /

2 Likes
34

I did mount /dev/sda6 /mnt, mount /dev/sda6 /mnt/boot and then arch-chroot /mnt, following this guide https://discovery.endeavouros.com/system-rescue/arch-chroot-for-bios-legacy-systems/2021/03/

I installed the other kernels using AKM, if that helps clarify anything.

35

Should not mount the same device to different mountpoints…

2 Likes
36

Ah, so You mounted your system partition first to /mnt then a second time to /mnt/boot?

The second time was not needed.

Wise words of experience!

3 Likes
37

That’s right. To be honest I was kind in panic and ignored the part that this is only if I have a separate boot partition.

1 Like
38

So…you should probably fix that.

Left as it is, kernel updates will break your system.

You should re-install all your kernels and then reinstall grub and run grub-mkconfig.

3 Likes
39

Make a backup of any data, and re-install?

2 Likes
40

That seems extreme to me.

1 Like