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

General system Kernel, boot, graphics & hardware
1

While updating the system, I noticed some of the packages were the kernel (such as linux and linux-lts), while the update was happening power was knocked out, now I can’t boot back in and 2 errors appears:
image

So far, I have tried archrooting into it, removing the pacman lock and doing the update again (pacman -Syu) The linux package was spitting out errors, so I removed it (pacman -R linux linux-headers) and ran the update again, updating linux-lts and linux-lts-headers and some other software, afterwards I ran grub-mkconfig -o /boot/grub/grub.cfg and grub-install --target=i386-pc /dev/sda6, but that didn’t solve anything and the same error message appears.

2

Reinstalling linux-lts should fix that error.

If it didn’t, perhaps you weren’t in the chroot when you did it?

1 Like
3

Just tried it, and I still get the same error. I did the chroot following Discovery guide for bios system.

4

Can you share all the terminal output from that session so we can see what is happening?

Can we also see lsblk -o name,type,fstype,size,uuid

2 Likes
5

Won’t that install the bootloader at the (system?) partition instead of the disk /dev/sda in this case for Legac/Bios install?

2 Likes
6

How can I find the terminal output from that session?

sblk -o name,type,fstype,size,uuid output

[liveuser@eos-2021.12.17 ~]$ lsblk -o name,type,fstype,size,uuid
NAME TYPE FSTYPE SIZE UUID
loop0 loop squashfs 1.7G
sda disk 931.5G
├─sda2 part btrfs 722.7G efb2075f-dd6e-4b51-8fca-e7da98288973
├─sda3 part 1K
├─sda5 part swap 3.7G 894c3dea-03bc-44f7-907a-71be46cfaf8a
└─sda6 part ext4 150.7G 1e646f24-d166-4a61-a478-4f7b5c9ea6ed
sdb disk 14.5G
├─sdb1 part exfat 14.4G 3D11-336B
│ └─ventoy dm iso9660 1.9G 2021-12-17-11-32-24-00
└─sdb2 part vfat 32M 301E-EA1C

7

If you already closed the terminal, you may have to do it again and save the output before closing the terminal.

1 Like
8

It looks to me like grub is working fine. But yeah, it is probably the original grub install still.

2 Likes
9

I think I indeed typed it wrong, should I re-do it and then restart?

10

Right. It gets to loading the kernel but it was just “a bit deviating from the norm” to install it to the partition for a MBR disk.

This^^

2 Likes
11

Yeah, it is wrong. I am just not sure it matters :wink:

1 Like
12

I closed the terminal and restarted the PC to see if it worked. Running the command again:

[root@EndeavourOS home]# pacman -S linux-lts
warning: linux-lts-5.15.38-1 is up to date – reinstalling
resolving dependencies…
looking for conflicting packages…

Package (1) Old Version New Version Net Change

core/linux-lts 5.15.38-1 5.15.38-1 0.00 MiB

Total Installed Size: 128.43 MiB
Net Upgrade Size: 0.00 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [--------------------------------] 100%
(1/1) checking package integrity [------------------------------------------------------------------------] 100%
(1/1) loading package files [------------------------------------------------------------------------] 100%
(1/1) checking for file conflicts [------------------------------------------------------------------------] 100%
:: Processing package changes…
(1/1) reinstalling linux-lts [------------------------------------------------------------------------] 100%
:: Running post-transaction hooks…
(1/5) Arming ConditionNeedsUpdate…
(2/5) Updating module dependencies…
(3/5) Updating linux initcpios…
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: ‘default’
→ -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
==> Starting build: 5.15.38-1-lts
→ Running build hook: [base]
→ Running build hook: [udev]
→ Running build hook: [autodetect]
→ Running build hook: [modconf]
→ Running build hook: [block]
→ Running build hook: [keyboard]
→ Running build hook: [keymap]
→ Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-lts.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-lts.preset: ‘fallback’
→ -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
==> Starting build: 5.15.38-1-lts
→ Running build hook: [base]
→ Running build hook: [udev]
→ Running build hook: [modconf]
→ Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: wd719x
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: xhci_pci
→ Running build hook: [keyboard]
→ Running build hook: [keymap]
→ Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-lts-fallback.img
==> Image generation successful
(4/5) Check if user should be informed about rebooting after certain system package upgrades.
(5/5) Checking which packages need to be rebuilt

13

Probably not.
Better to get the kernel sorted out first.

1 Like
14

What does ls /boot show?

1 Like
15 
[root@EndeavourOS home]# ls /boot
bin   grub				initramfs-linux-zen.img  mnt   sbin  var
boot  home				intel-ucode.img		 opt   srv   vmlinuz-linux-lts
dev   initramfs-linux-lts-fallback.img	lib			 proc  sys   vmlinuz-linux-zen
etc   initramfs-linux-lts.img		lib64			 root  tmp
gnu   initramfs-linux-zen-fallback.img	lost+found		 run   usr
16

Uhh…

What does ls -ld /boot show?

2 Likes
17 
[root@EndeavourOS home]# ls -ld /boot
drwxr-xr-x 19 root root 4096 May 11 17:03 /boot
18

Why do you have an entire install inside /boot?

3 Likes
19

I have no idea what is even going on

20

Can I see df -h from inside the chroot?

2 Likes