Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

j-james · 2021-09-05 03:23:10

Upon updating and rebooting my system today, I was greeted with this after systemd-boot:

EFI stub: ERROR: Failed to read file
EFI stub: ERROR: Failed to load initrd!
EFI stub: ERROR: efi.main() failed!

Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

Surprisingly, I haven't done anything out of the ordinary recently, or at least that would mess with my boot. It appears to be the same problem as here: https://bbs.archlinux.org/viewtopic.php?id=266802 which was solved by wiping and reinstalling.

I don't have a recent backup of my system, unfortunately. Could I have help in getting my system back to a usable state, or at least usable enough to copy off my home directory?

If it's helpful, I installed Arch using the official installer on a ThinkPad that had shipped with Fedora.

Last edited by j-james (2021-09-07 06:05:34)

Raynman · 2021-09-05 09:49:27

j-james wrote:

Could I have help in getting my system back to a usable state, or at least usable enough to copy off my home directory?

As mentioned in the linked thread: boot "using USB with ISO and arch-chroot". Well, you don't need to chroot if you only want to access the files; to copy /home and maybe look at the EFI system partition and pacman.log for clues on what went wrong, just mount the relevant partitions. If you want to try fixing it, chrooting is often useful.

Khere · 2021-09-05 11:38:15

You can chroot from a live usb into your Arch O.S. and then launch a full system upgrade and recompile the kernel by reinstalling the linux kernel package

Last edited by Khere (2021-09-05 11:38:30)

Dante777 · 2021-09-05 13:23:46

j-james wrote:

Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

Shouldn't this be:

/vmlinuz-linux

?
I'd just chroot im my system and double check /boot/loader/entries/arch.conf, just to be sure.

title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img      # or /amd-ucode.img
initrd /initramfs-linux.img
options rw root=PARTUUID=$(blkid -s PARTUUID -o value /dev/your-root-partition-here)

And probably also run

sudo bootctl update

Raynman · 2021-09-05 15:29:55

EFI uses backslash; systemd-boot handles conversion from (forward) slash in loader entries.

j-james · 2021-09-05 17:04:27

You can chroot from a live usb into your Arch O.S. and then launch a full system upgrade and recompile the kernel by reinstalling the linux kernel package.

Just with `pacman -S linux`? Now I'm getting a different error message:

Error loading \vmlinuz-linux:  Not Found
Failed to execute Arch Linux (\vmlinuz-linux): Not Found

I'd just chroot im my system and double check /boot/loader/entries/arch.conf, just to be sure.

What should I be looking for? `/boot/loader/entries/2021-07-27_02-23-07.conf`:

# Created by: archinstall
# Created on: 2021-07-27_02-23-07
title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode
initrd /initramfs-linux.img
options root=PARTUUID=long-identifier rw intel_pstate=no_hwp

sudo bootctl update

I got

Failed to copy data from "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/systemd/.#systemd-bootx64.efilongidentifier": Input/output error
Failed to copy data from "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/EFI/BOOT/.#BOOTX64.EFIlongidentifier": Input/output error

Maybe I messed up my mounts? I mounted `/dev/nvmen1p2` to `/mnt`, and `/dev/nvmen1p1` to `/mnt/boot`, then chrooted in with `arch-chroot /mnt`.

Last edited by j-james (2021-09-07 06:06:30)

Khere · 2021-09-06 07:00:51

j-james wrote:

Just with `pacman -S linux`? Now I'm getting a different error message:

Yes reinstalling the linux kernel package would recompile the kernel and the modules with mkinitcpio and it will regenerate the vmlinuz.

Last edited by Khere (2021-09-06 07:01:03)

j-james · 2021-09-06 08:04:59

Khere wrote:

Yes reinstalling the linux kernel package would recompile the kernel and the modules with mkinitcpio and it will regenerate the vmlinuz.

That seems to have broken things further, the computer is telling me that \vmlinuz-linux can't be found.

Khere · 2021-09-06 10:25:08

So you chroot into your O.S. , you did a full system ugprade, you have reinstalled the kernel package and still not founding vmlinuz-linux? vmlinuz_linux is the compressed kernel so If you have done what I said the problem is the location of vmlinuz-linux.
Probably the boot partition is not mounted.
Can you chroot in your system and then post the output of :

lsblk 
cat /etc/fstab

Last edited by Khere (2021-09-06 16:03:12)

erdem.agaoglu · 2021-09-06 14:48:20

Happened to me today after linux 5.13.13.arch1-1 upgrade. Downgrading to an earlier kernel fixed it.

1. Boot from USB
2. mount root dev to /mnt
3. mount boot dev to /mnt/boot
4. chroot to /mnt
5. pacman -U /var/cache/pacman/pkg/linux-5.13.12.arch1-1-x86_64.pkg.tar.zst

I guess I'll wait for the next update.

Ammako · 2021-09-06 15:06:19

j-james wrote:

Maybe I messed up my mounts? I mounted `/dev/nvmen1p2` to `/mnt`, and `/dev/nvmen1p1` to `/mnt`, then chrooted in with `arch-chroot /mnt`.

You're mounting both partitions onto the same mount point?

Khere · 2021-09-06 16:01:02

erdem.agaoglu wrote:

Happened to me today after linux 5.13.13.arch1-1 upgrade. Downgrading to an earlier kernel fixed it.
I guess I'll wait for the next update.

I also have the newest version of the kernel but i haven't problem with boot.
If it not appears to everyone who upgrade the kernel is not a kernel bug.

j-james · 2021-10-18 06:04:19

I encountered this issue again today with the latest kernel update. Mounting (/mnt and /mnt/boot), chrooting, and downgrading fixed it this time - I think I messed up the mount process before downgrading previously, which caused a cascade of more errors.

There is still an underlying issue causing these problems that I still haven't identified. I think it has something to do with using the new installer on a not-completely-wiped computer - there are a couple of extra entries in my boot menu (three titled "Linux" and one titled "Fedora").

Last edited by j-james (2021-10-19 23:52:17)

j-james · 2021-12-09 08:56:50

This happened again today. It's become enough of an inconvenience that I think I'm going to wipe and reinstall fresh, to see if I can get rid of those weird boot entries.

avakand · 2021-12-14 19:15:48

I am facing same problem - after some (but not all) kernel updates systemd-boot writes "Invalid parameter". After reinstalling linux package error switches to "not found". I tried creating a backup kernel boot entry with linux-lts package, but a few updates later both boot entries broke down. After last kernel update only "linux" boot entry fails to boot, "linux-lts" works fine.

Downgrading kernel package seems to fix the issue, but it is really inconvenient. Is there a way to look up boot loader logs?

Update: I managed to fix the issue without downgrading after cleaning up /boot folder from everything except systemd-boot configuration files (folders "loader", "EFI/BOOT" and "EFI/systemd") and files generated by linux / linux-lts packages. There were some files leftover from previous fedora installation, i.e file /boot/EFI/BOOT/fbx64.efi. I rebooted to firmware interface and tried toggling boot devices on/off because it shows two devices with same name. After that boot entry with "linux" kernel successfully booted.

Last edited by avakand (2021-12-14 19:39:57)

seth · 2021-12-15 08:16:49

I managed to fix the issue without downgrading after cleaning up /boot folder from everything except systemd-boot configuration files

# Created by: archinstall

https://bbs.archlinux.org/viewtopic.php?id=268040
https://github.com/archlinux/archinstall/issues/645
https://wiki.archlinux.org/title/Partitioning#/boot

avakand · 2021-12-15 15:47:48

Thanks for pointing to archinstall issue. It seems my problem was related to mismatch of boot partition size and vfat filesystem on it. The latter was almost 100 megabytes bigger.

# df -hT
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p1 vfat 599M 111M 488M 19% /boot
# fdisk -l
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System

I unmounted boot partition and recreated vfat filesystem, after that sizes are almost equal. I encountered this issue after installing Fedora and using archinstall later to install Arch.

Thinking back, I remember editing /boot/loader/loader.conf with vim one time and systemd-boot failed to boot after that because config file was corrupted and failed to open.

Last edited by avakand (2021-12-15 15:48:54)

Arch Linux

#1 2021-09-05 03:23:10

Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#2 2021-09-05 09:49:27

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#3 2021-09-05 11:38:15

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#4 2021-09-05 13:23:46

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#5 2021-09-05 15:29:55

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#6 2021-09-05 17:04:27

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#7 2021-09-06 07:00:51

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#8 2021-09-06 08:04:59

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#9 2021-09-06 10:25:08

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#10 2021-09-06 14:48:20

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#11 2021-09-06 15:06:19

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#12 2021-09-06 16:01:02

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#13 2021-10-18 06:04:19

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#14 2021-12-09 08:56:50

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#15 2021-12-14 19:15:48

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#16 2021-12-15 08:16:49

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

#17 2021-12-15 15:47:48

Re: Failed to execute Arch Linux (\vmlinux-linux): Invalid Parameter

Board footer