Lost power during upgrade now says vmlinuz-linux can not be found

ggbc11 · 2021-02-05 10:23:49

Is it just a matter of copying this from a boot usb to my system?
Or could it point to another issue?
What checks should I do?
I have chroot into the installed system from a USB but not sure where to go from there.
Would greatly appreciate a point in the right direction.

V1del · 2021-02-05 10:39:42

For this particular message reinstall the linux package from the chroot (with all partitions properly mounted), however, check your pacman.log and reinstall everything that was part of the failed update.

Maybe also check with

pacman -Qkk > /dev/null

for modified files but that's likely to contain a few false positives

Last edited by V1del (2021-02-05 11:01:26)

graysky · 2021-02-05 10:40:05

Might be good idea to reinstall the kernel package from your chroot. I assume you're using the standard one: linux. If applicable, make sure you have system-critical partitions such as /boot properly mounted in the chroot before you try.

Xyne · 2021-02-05 11:51:49

If the power went out, there may be other errors as well. To ensure that all critical packages are installed correctly, mount the installed system as you would to chroot into it, but instead of chrooting, use pacstrap from the live medium to re-install the base group and linux:

pacstrap -M -G -i -C /mnt/etc/pacman.conf /mnt base linux

The M, G and C flags will use the pacman configuration files already on the host instead of copying the ones from the live medium. If any of those files are corrupted though, you will need to fix them (or copy them from the live medium by removing the appropriate flag from the command above).

Using pacstrap may be unnecessary, but I think it's better to be sure that the base system is correctly installed before relying on it.

ggbc11 · 2021-02-06 19:56:02

Thank you all for your time and help.

Booted into usb
Iwctl to connect to internet
Station wlan0 scan
Station wlan0 get-networks
Station wlan0 connect...
fdisk - l
sda1 is boot partition (dual boot win7)
Sda2 win7
sda4 is main Linux root
sda3 recovery (?) (260M)
Mounted sda4 /mnt
Mounted sda1 /mnt/boot
Arch-chroot
pacman -Qkk > /dev/null [returns two screens worth of mismatches, first couple of lines include /boot permissions mismatch, /mnt gid and permissions mismatch. Alot of size mismatches in man]
pacman -S linux [seems to install OK. Builds images successfully vmlinuz-linux, mkinitcpio, initramfs-linux. Mentions that theres firmware missing for various modules]
ls /boot [has vmlinuz-linux, initramfs-linux, and initramfs-linux-fallback]
pacman -Syu [downloads remainder of the updates from previous session but fails to commit transaction due to conflicting files, including power off, reboot and shutdown in systemd-sysvcompat and Xterm]
Exit chroot
Reboot
Same issue: boot/vmlinuz-linux not found

Reload from usb
Remount as before
pacstrap -M -G -i -C /mnt/etc/pacman.conf /mnt base linux [installs 2 packages, base and linux - same output as pacman linux]
Reboot
Same issue

So I've either put the boot files in the wrong place or the boot sequence is looking in the wrong place?

It's been a while since I set this up, it might be best to reinstall the system but I'd like to understand what's gone wrong as a learning excersize.

Xyne · 2021-02-09 10:30:46

Check your boot loader's configuration to make sure that it's looking in the right place and check the system configuration (e.g. fstab) to make sure that you're installing everything in the right place.

ggbc11 · 2021-02-12 08:52:16

Xyne wrote:

Check your boot loader's configuration to make sure that it's looking in the right place and check the system configuration (e.g. fstab) to make sure that you're installing everything in the right place.

Thanks, I checked fstab and there was one line sda4
Ran genfstab now have 4 lines corresponding to lsblk but hadn't made a change on reboot.

When run pacman - Syu, it was failing due to file conflicts of systemd-sysvcompat, Xterm, vim-runtime, vim. I ran pacman - Qo on each one, none have owners, removed all except systemd-sysvcompat due to dependency on base. I also tried pacman - Sf but said option invalid?
Ran - Syu with ignore flag for systemd-sysvcompat and has updated.

How can I update, or link systemd-sysvcompat to base?

ggbc11 · 2021-02-12 12:39:12

ggbc11 wrote:

Xyne wrote:
Check your boot loader's configuration to make sure that it's looking in the right place and check the system configuration (e.g. fstab) to make sure that you're installing everything in the right place.
Thanks, I checked fstab and there was one line sda4
Ran genfstab now have 4 lines corresponding to lsblk but hadn't made a change on reboot.
When run pacman - Syu, it was failing due to file conflicts of systemd-sysvcompat, Xterm, vim-runtime, vim. I ran pacman - Qo on each one, none have owners, removed all except systemd-sysvcompat due to dependency on base. I also tried pacman - Sf but said option invalid?
Ran - Syu with ignore flag for systemd-sysvcompat and has updated.
How can I update, or link systemd-sysvcompat to base?

So I renamed each file within systemd-sysvcompat and the package updated, the system is now completely updated. I hoped that update init would resolve this but I still have the same issue on reboot.

seth · 2021-02-12 15:21:04

See https://wiki.archlinux.org/index.php/Pa … an_upgrade
Use the --sysroot approach, do NOT chroot into the installation.

There's a chance you're actually booting from the root partition, check /mnt/boot *before* you're mounting the boot partition there.
If there's a recent kernel or an initramfs or anything that looks like it's the actual boot partition and since sda1 wasn't in your fstab, try to update and explcitly install the kernel *without* mounting sda1 to /mnt/boot

If you need to resolve file conflicts because of untracked files on disk, the parameter you're looking for is "--override" (which takes a path pattern as parameter. You cannot unconditionally override stuff, --force was dropped)

ggbc11 · 2021-02-12 16:40:04

seth wrote:

See https://wiki.archlinux.org/index.php/Pa … an_upgrade
Use the --sysroot approach, do NOT chroot into the installation.
There's a chance you're actually booting from the root partition, check /mnt/boot *before* you're mounting the boot partition there.
If there's a recent kernel or an initramfs or anything that looks like it's the actual boot partition and since sda1 wasn't in your fstab, try to update and explcitly install the kernel *without* mounting sda1 to /mnt/boot
If you need to resolve file conflicts because of untracked files on disk, the parameter you're looking for is "--override" (which takes a path pattern as parameter. You cannot unconditionally override stuff, --force was dropped)

Thank you very much for explaining this. /boot only had grub in it. Followed - -sysroot method, rebooted back to normal.

I assumed the block with the asterisks had to be the boot partition. I'd going to look further into exactly how the boot loader works. Thanks again!

Arch Linux

#1 2021-02-05 10:23:49

Lost power during upgrade now says vmlinuz-linux can not be found

#2 2021-02-05 10:39:42

Re: Lost power during upgrade now says vmlinuz-linux can not be found

#3 2021-02-05 10:40:05

Re: Lost power during upgrade now says vmlinuz-linux can not be found

#4 2021-02-05 11:51:49

Re: Lost power during upgrade now says vmlinuz-linux can not be found

#5 2021-02-06 19:56:02

Re: Lost power during upgrade now says vmlinuz-linux can not be found

#6 2021-02-09 10:30:46

Re: Lost power during upgrade now says vmlinuz-linux can not be found

#7 2021-02-12 08:52:16

Re: Lost power during upgrade now says vmlinuz-linux can not be found

#8 2021-02-12 12:39:12

Re: Lost power during upgrade now says vmlinuz-linux can not be found

#9 2021-02-12 15:21:04

Re: Lost power during upgrade now says vmlinuz-linux can not be found

#10 2021-02-12 16:40:04

Re: Lost power during upgrade now says vmlinuz-linux can not be found

Board footer