Arch Linux

baconStrips

Member

Registered: 2022-09-28

Posts: 2

[SOLVED] Suspected Kernel - loading failure after botched upgrade.

Hello,
I am very, very new to Arch Linux, yet I already managed to screw up my kernel.
I have Arch installed on a separate nvme-drive in my machine and after the last pacman kernel - update I somehow managed to trip up the kernel.
After selecting the Arch distro - in grub I was greeted with the following message:

Loading Linux linux error: invalid cluster 0 
Loading initial ramdisk error you need to load the kernel first

After some digging I was able to successfully mount the filesystem with the live-usb stick and got the internet to work.
However after attempting to reinstall the kernel using:

sudo pacman -S linux

I get an error:

install: cannot create regular file '/boot/vmlinuz-linux': Read-only file system
error: command failed to execute correctly

This is strange since the root-user should have permissions to r/w after mounting right?
Any suggestions would be helpful Thank you.

Last edited by baconStrips (2022-09-30 23:02:07)

astralc

Member

Registered: 2022-09-17

Posts: 127

Re: [SOLVED] Suspected Kernel - loading failure after botched upgrade.

I somehow managed to trip up the kernel.

HOW?

Also:
* Is grub from installed Arch, or from other OS?
* What is the filesystem for /boot? is it the same partition as /?
* Did you try to fsck the filesystem?

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 76,485

Re: [SOLVED] Suspected Kernel - loading failure after botched upgrade.

I was able to successfully mount the filesystem with the live-usb stick

Also check the dmesg/journal for IO errors leading to a ro re-mount and https://wiki.archlinux.org/title/SMART

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

baconStrips

Member

Registered: 2022-09-28

Posts: 2

Re: [SOLVED] Suspected Kernel - loading failure after botched upgrade.

Thank you @astralc and @seth, for the quick response.
fsck-ing the filesystem after mounting it was the way to go - there was a faulty sector that was updated.

Thanks!