Arch Linux

harubyy

Member

Registered: 2017-03-09

Posts: 26

[SOLVED]: after update, cannot boot: /boot/vmlinuz-linux not found

Hello,
After I updated my arch with "sudo pacman -Syyu" today on my virtualbox, I'm unable to boot it.

I receive the following error:
Loading Linux linux...
error file /boot/vmlinuz-linux not found
loading initial ramdisk
error: you need to load the kernel first

I downloaded the latest iso, using that I ch-rooted to my system. I don't have any separate boot partition. So I mounted both /mnt and /mnt/boot to my main partition (sorry I got screenshots forgetting that I cannot paste them here, if there's a way I appreciate if someone can tell me).

I ran the command
pacman -S linux

I confirmed that it successfully created the image and it ran mkiticpio. I have initframs too. /etc/mkinitcpio.d/linux.preset is created. And I do have vmlinuz-linux under my /boot.
But I'm still getting the same error and cannot boot my system.

I'm not sure what I'm missing. Thanks in advance.

Last edited by harubyy (2022-03-04 08:39:08)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,170

Re: [SOLVED]: after update, cannot boot: /boot/vmlinuz-linux not found

Mounting your root partition twice doesn't make sense and logically speaking you've now placed the vmlinuz-linux and initramfs-linux.img into the root of your root (... so /vmlinuz-linux and /initramfs-linux.img) I'm assuming this might well be your original issue as well. From the chroot what you think to be the correct mount setup post

lsblk -f
ls -l /boot
cat /boot/grub/grub.cfg #assuming you've used/are using GRUB
#If you actually mounted something on boot
umount /boot
ls -l /boot

there's no need for screenshots, post these to a pastebin: https://wiki.archlinux.org/title/List_o … n_services

PS: -Syyu is a waste of resources and only necessary in a select few cases, don't use it if you have no knowing reason to, -Syu is sufficient.

Last edited by V1del (2022-03-04 09:18:50)

harubyy

Member

Registered: 2017-03-09

Posts: 26

Re: [SOLVED]: after update, cannot boot: /boot/vmlinuz-linux not found

Mounting your root partition twice doesn't make sense and logically speaking you've now placed the vmlinuz-linux and initramfs-linux.img into the root of your root (... so /vmlinuz-linux and /initramfs-linux.img) I'm assuming this might well be your original issue as well. From the chroot what you think to be the correct mount setup post

lsblk -f
ls -l /boot
cat /boot/grub/grub.cfg #assuming you've used/are using GRUB
#If you actually mounted something on boot
umount /boot
ls -l /boot

there's no need for screenshots, post these to a pastebin: https://wiki.archlinux.org/title/List_o … n_services

PS: -Syyu is a waste of resources and only necessary in a select few cases, don't use it if you have no knowing reason to

Oh, I didn't know any other than pastebin and it didnt work yesterday, sorry I should have checked.

So here's what I did.
I only mounted my main partition to /mnt and ch-rooted.

Then

lsblk -f          : http://ix.io/3Rjj
ls -l /boot      : http://ix.io/3Rjm
cat /boot/grub/grub.cfg: http://ix.io/3Rjn

since I didnt mount /boot I skipped the last 2 command you listed.

aaand you're right. I see vmlinuz-linux and initramfs-linux.img under /: http://ix.io/3Rjt

Then I deleted vmlinuz-linux and initramfs-linux.img under / and then run pacman -S linux.
ls -l /boot gives me http://ix.io/3Rjw

I restarted my system and now it's booting, problem solved. Thank you very much

Last edited by harubyy (2022-03-04 08:35:31)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,170

Re: [SOLVED]: after update, cannot boot: /boot/vmlinuz-linux not found

Make sure you don't accidentally do a double mount of / in your fstab, which might be the reason why you had the issue in the first place.

harubyy

Member

Registered: 2017-03-09

Posts: 26

Re: [SOLVED]: after update, cannot boot: /boot/vmlinuz-linux not found

Thanks for the reminder, I checked the contents of my fstab, looks ok to me.

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda3
UUID=bb5c8b6f-8a66-4be4-bae8-0b9d46a90a74	/         	ext4      	rw,relatime	0 1

# /dev/sda2
UUID=03765eef-a299-4dd2-b150-f35e4cd4f52b	none      	swap      	defaults  	0 0