Vmlinuz-5.10-x86_84 not found

Wait, did pacman -Syyu successfully complete and update all packages?

yes
:: Starting full system upgrade…
there is nothing to do

Here’s what my linux510.preset looks like. It’s fairly standard across most installations:

# mkinitcpio preset file for the 'linux510' package

ALL_config="/etc/mkinitcpio.conf"
ALL_kver="/boot/vmlinuz-5.10-x86_64"

PRESETS=('default' 'fallback')

#default_config="/etc/mkinitcpio.conf"
default_image="/boot/initramfs-5.10-x86_64.img"
#default_options=""

#fallback_config="/etc/mkinitcpio.conf"
fallback_image="/boot/initramfs-5.10-x86_64-fallback.img"
fallback_options="-S autodetect"

You can create that file (while in chroot) under /etc/mkinitcpio.d/linux510.preset

I’m getting worried though. There’s quite a lot that isn’t working ever since you lost power during the update.

==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: ‘default’
→ -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64.img
==> ERROR: specified kernel image does not exist: /boot/vmlinuz-5.10-x86_64' ==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'fallback' -> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64-fallback.img -S autodetect ==> ERROR: specified kernel image does not exist: /boot/vmlinuz-5.10-x86_64’

when I run mhwd-kernel -li
it happens:
Currently running: 5.10.34-1-MANJARO (linux510)
The following kernels are installed in your system:
error: could not open file /var/lib/pacman/local/python-cryptography-3.4.8-2/desc: No such file or directory

  • linux510
    error: could not open file /var/lib/pacman/local/python-cryptography-3.4.8-2/desc: No such file or directory

Unless someone more versed knows otherwise, something appears to have really borked on your system.

Sudden power loss can cause unpredictable and “scattered” issues, especially during a system update.

At this point, personally, I would re-install from scratch, and import my /home/username/ data.


It sounds like you had your home folder on the same partition as the root system?

Do you have an extra drive, such as an external USB, that you can temporarily transfer your entire /home/username/ directory?

After which you can reinstall Manjaro from scratch and then re-transfer your home folder back to the internal HDD/SSD.

In the chroot, what are the contents of /boot and /boot/efi ?

sh-5.1# cd boot
efi grub intel-ucode.img linux510-x86_64.kver memtest86+

sh-5.1# cd efi
sh-5.1# ls
EFI

What about,

 pacman -Q linux510

sh-5.1# pacman -Q linux510
linux510 5.10.63-1

What happens if you clear the cache then try to force-reinstall linux510?

pacman -Scc

pacman -S linux510
sh-5.1# pacman -Scc

Cache directory: /var/cache/pacman/pkg/
:: Do you want to remove ALL files from cache? [y/N] y
removing all files from cache...

Database directory: /var/lib/pacman/
:: Do you want to remove unused repositories? [Y/n] y
removing unused sync repositories...
sh-5.1# pacman -S linux510
warning: downgrading package linux510 (5.10.63-1 => 5.10.61-1)
resolving dependencies...
looking for conflicting packages...
error: could not open file /var/lib/pacman/local/python-cryptography-3.4.8-2/desc: No such file or directory

Packages (1) linux510-5.10.61-1

Total Download Size:   73.84 MiB
Total Installed Size:  78.23 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 linux510-5.10.61...    73.8 MiB  6.34 MiB/s 00:12 [##################] 100%
error: failed retrieving file 'linux510-5.10.61-1-x86_64.pkg.tar.zst.sig' from manjaro.re : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.

@nihilistkaaos Try this:

  1. Remove this directory:
sudo rm -R /var/lib/pacman/local/python-cryptography-3.4.8-2/

(it is part of the database anyway, which will be updated)

  1. Retrieve a new mirrorlist:
sudo pacman-mirrors -c Germany && sudo pacman-mirrors -f 5

(replace Germany with your country)

  1. Update the database and upgrade:
sudo pacman -Syyuu
  1. Reinstall everything:
export pkg=( $(pacman -Qq) )
echo ${pkg[@]}
sudo pacman -S ${pkg[@]}
1 Like
Total Download Size:    294.31 MiB
Total Installed Size:  1271.07 MiB
Net Upgrade Size:       298.80 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
 linux510-5.10.61-1-x86_64 is up to date
 Total ( 1/80)         294.3 MiB  9.58 GiB/s 00:00 [##################] 100%
error: failed retrieving file 'linux510-5.10.61-1-x86_64.pkg.tar.zst.sig' from manjaro.re : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.

Is your internet connection working?

ping -4 -c1 manjaro.re

I had not changed the country in the pacman mirrors command
now updated

this command returns error

warning: zlib-1:1.2.11-4 is up to date -- reinstalling
error: target not found: 1:1.2.11-4
warning: zsh-5.8-1 is up to date -- reinstalling
error: target not found: 5.8-1
warning: zsh-autosuggestions-0.7.0-1 is up to date -- reinstalling
error: target not found: 0.7.0-1
warning: zsh-completions-0.33.0-1 is up to date -- reinstalling
error: target not found: 0.33.0-1
warning: zsh-history-substring-search-1.0.2-1 is up to date -- reinstalling
error: target not found: 1.0.2-1
warning: zsh-syntax-highlighting-0.7.1-1 is up to date -- reinstalling
error: target not found: 0.7.1-1
warning: zsh-theme-powerlevel10k-1.15.0-2 is up to date -- reinstalling
error: target not found: 1.15.0-2
warning: zstd-1.5.0-1 is up to date -- reinstalling
error: target not found: 1.5.0-1
warning: zvbi-0.2.35-4 is up to date -- reinstalling
error: target not found: 0.2.35-4
warning: zxing-cpp-1.2.0-1 is up to date -- reinstalling
error: target not found: 1.2.0-1
warning: zziplib-0.13.72-1 is up to date -- reinstalling
error: target not found: 0.13.72-1

upps sorry… i forgot to add quiet:

export pkg=( $(pacman -Qq) )

corrected above

reinstalled. now i run exit and reboot?

Check first if the file is there now:

ls /boot

There must be the file available. Then I guess you can reboot.