[SOLVED] Error while boot: vmlinuz-linux: not found

palicao · 2023-09-03 14:59:54

Hi all
my system doesn't boot.I am able to get into grub command line after the boot failure, but I don't understand what to do next.
I tried to manually re-install grub following some steps which lead me to the assumption my boot/kernel disappeared.
while on grub command line _ls_ command gives me two possible locations for grub
1. (hd1,gpt1) which contains GRUB and EFI folders - I assume this is the uefi partition
2. (hd1,gpt2) which contain boot/ home/ var/ and other folders - I assume this is the system partition

the guide i found online suggested to do the following from grub command line

1. set root. in this case root should be (hd1,gpt2) meaning the second HD and the second partiton, correct?
it says also to check the files in this folder with 'ls (hd1,gpt2)/boot but the output is empty.the command shold beset root=(hd1,gpt2)/ root=/dev/sdb2

2. set kernelas i said before there is no files in the boot section so I stopped here because my boot section is emtpy and the command to set the kernel linux (hd1,gpt2)/boot/vmlinuz-linux gives me an error

At this point I can safely guess I need to reinstall somehow?

Also I tried to open with cat the grub.cfg into the /grub folder in order to understand something but the file but it's too big and I can't seem to find a way in grub to output the file page by page.

I also tried this guide to run an ISO via usb in order to try to reinstall the grub but I seems unable to mount as I get the error can't find in /etc/fstab/ there

At this stage I don't understand what happened and also I don't know how to fix it.
So how should I reinstall from scratch the GRUB and or kernel without formatting the disk it's in?
I had a look at the wiki and the GRUB folder contains already the x86_64-efi file so maybe I just need to add the Kernel back?
Or maybe shall I simply reinstall Arch from scratch but in this case there is a way to re-install but not go over all the aspects I personalized in these years of usage?

Thank you in advance, sorry but I am completey lost at the moment

thanks in advance. I am sorry but I am very noob :3

Last edited by palicao (2023-09-11 20:50:40)

palicao · 2023-09-03 19:03:29

I tried to boot a live USB image and mount what I believe is the root and then do _arch-chroot /mnt_ but it didn't help.
then I assumed for some reason my Kernel was disappeared and I followed these steps

# mkdir /mnt optional, you may also just use /mnt/arch
# mount /dev/sdax /mnt #substitute sdax with your root partition - to understand what is your root partition u need to check every partition with fdisk -l and then mount each of them to see what is inside. the umount if its' the wrong one
# mount /dev/sday /mnt/boot #only needed if you have a seperate partition sday for /boot which I did have
# mount -t proc proc /mnt/proc #mount system folders
# mount -t sysfs sys /mnt/sys
# mount -o bind /dev /mnt/dev

then you chroot into your installation
#chroot /mnt/

then i upddate the database
#sudo pacman -Syy

and finally updated/reistalled the kernel with
#sudo pacman -S linux

the forum post mentioned as well headers with this following command
#sudo pacman -S linux-headers

but I assumed I don't need to do it for it was my kernel to be missing not the headers.

Is it correct?
did i do weird things?

The system now it's working, now I would like to undersand in the log what happened. can I do it?

seth · 2023-09-03 19:34:07

* booting the install iso makes you root, no need for sudo
* "pacman -Syy" is a horrible idea, the extra "y" causes undue burden on the mirrors and you run arisk to compromise the package database; also you're setting yourself up for future partial updates (which you possibly conducted, just that this is relatively safe with the kernel)
==> run "sudo pacman -Syu" for a full system update; make sure the /boot partition is mouted (see below)
* the headers are mostly interesting if you're using some dkms module and in that cause would ideally be installed along the kernel, not afterwards
* the critical step was likely to mount the boot partition

To figure what went wrong previously, check the pacman log; the kernel is copied into location by an alpm hook which apparently failed?

palicao · 2023-09-03 21:10:27

seth wrote:

To figure what went wrong previously, check the pacman log; the kernel is copied into location by an alpm hook which apparently failed?

thank you!

I foun some of the instructions on a very old post here so I guess the instructions were a bit lacking.
Will run the correct update now!

Arch Linux

#1 2023-09-03 14:59:54

[SOLVED] Error while boot: vmlinuz-linux: not found

#2 2023-09-03 19:03:29

Re: [SOLVED] Error while boot: vmlinuz-linux: not found

#3 2023-09-03 19:34:07

Re: [SOLVED] Error while boot: vmlinuz-linux: not found

#4 2023-09-03 21:10:27

Re: [SOLVED] Error while boot: vmlinuz-linux: not found

Board footer