[OPEN] Broke Install | unable to get vmlinuz-linux Kernel Image

Post Reply
jon5th5n
recruit crewman
Posts: 2
Joined: Fri Jun 21, 2024 6:59 pm

Hey there, this is my first time posting here.
I have a problem with my Arco install where I can't boot and get the error that the Kernel Images cannot be found. (I would guess this comes from a recent upgrade which failed because of a pre-transaction hook)
After first looking for the error on the internet I was pretty happy since it seemed you just had to chroot from a live image and reinstall the kernel with 'pacman -S(yu) linux'.
But I just couldn't get it fixed that way. I actually am not able to get the 'vmlinuz-linux' file or I am just to dumb to find it.

Here is what I have done:
- Got into a live environment
- mounted '/dev/nvme0n1p2' (root) to '/mnt' and '/dev/nvme0n1p1' (boot/efi) to '/mnt/boot/efi'
- 'sudo arch-chroot /mnt'
- I didn't find 'vmlinuz-linux' anywhere in the /boot/ folder hierarchy which in general seemed weirdly empty
- I tried 'pacman -S(yu) linux' but nothing changed at all
- I also tried many other things which where noted in pretty much all posts about this topic I was able to find but none of them were addressing the problem of the kernel file just completely missing

Now I am at the point where I would just do a big reinstall but to be honest I am just not in the mood for setting up everything all over again right now.

Some help would be really appreciated since I just can't seem to find anything on this exact issue.
Thanks in advance.

Here are some things that may be helpful:

- fdisk -l

Code: Select all

Disk /dev/nvme0n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: CT1000P1SSD8
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 93F98097-990E-4C94-A79B-20B2FDB04FB2

Device              Start        End    Sectors   Size Type
/dev/nvme0n1p1       4096     618495     614400   300M EFI System
/dev/nvme0n1p2     618496 1918840328 1918221833 914.7G Linux filesystem
/dev/nvme0n1p3 1918840329 1953520064   34679736  16.5G Linux swap
The backup GPT table is not on the end of the device.


Disk /dev/sda: 3.64 GiB, 3904897024 bytes, 7626752 sectors
Disk model: Storage Device
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 7E6D080D-05C4-4F12-A8F2-A2BDDB4A6DDF

Device       Start     End Sectors  Size Type
/dev/sda1     2048 7624587 7622540  3.6G Microsoft basic data
/dev/sda2  7624588 7626635    2048    1M Microsoft basic data


Disk /dev/loop0: 2.71 GiB, 2907348992 bytes, 5678416 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
- /boot/ folder:

Code: Select all

/boot/
├── efi
│   ├── EFI
│   │   └── arcolinux
│   │       └── grubx64.efi
│   └── grub
├── grub
│   ├── fonts
│   │   ...................
│   ├── grub.cfg
│   ├── grubenv
│   ├── locale
│   │   ....................
│   ├── themes
│   │   .....................
│   └── x86_64-efi
│       .......................
└── memtest86+
    ├── memtest.bin
    └── memtest.efi

Code: Select all

- pacman -S linux
warning: linux-6.9.5.arch1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (1)  Old Version    New Version    Net Change

core/linux   6.9.5.arch1-1  6.9.5.arch1-1    0.00 MiB

Total Installed Size:  134.14 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring                                                 [--------------------------------------------] 100%
(1/1) checking package integrity                                               [--------------------------------------------] 100%
(1/1) loading package files                                                    [--------------------------------------------] 100%
(1/1) checking for file conflicts                                              [--------------------------------------------] 100%
(1/1) checking available disk space                                            [--------------------------------------------] 100%
:: Processing package changes...
(1/1) reinstalling linux                                                       [--------------------------------------------] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) #### Important Linux packages have changed. Reboot is recommended. ####
User avatar
erikdubois
Captain
Posts: 5909
Joined: Tue Nov 07, 2017 3:45 pm
Location: Belgium
Contact:

I see you installed linux

I will always install also linux-headers - virtualbox and other apps need it
Learn, have fun and enjoy.
But first use the power of the Arch Wiki
use the tutorials on https://www.youtube.com/erikdubois
then use the power of google
then use the power of our moderators.
User avatar
erikdubois
Captain
Posts: 5909
Joined: Tue Nov 07, 2017 3:45 pm
Location: Belgium
Contact:

installing the kernel is one thing

normally I will also type update-grub (when on grub)

I am assuming you are rolling - you gave no info on how old your OS is and if you followed the recommended updates.

We have been communicating for months that you need to install the required package for the bootloader

arcolinux-bootloader-grub-git
arcolinux-bootloader-refind-git
arcolinux-bootloader-systemd-boot-git

check you have one of those

type "boot" to know which bootloader you are using

When you know that, install the correct package
then install the kernel and kernel-headers

Those three will create the needed files to boot

Video the 10th of April

Learn, have fun and enjoy.
But first use the power of the Arch Wiki
use the tutorials on https://www.youtube.com/erikdubois
then use the power of google
then use the power of our moderators.
User avatar
erikdubois
Captain
Posts: 5909
Joined: Tue Nov 07, 2017 3:45 pm
Location: Belgium
Contact:

ERROR: mkdir /var/lock/dmraid

that is something we never see - maybe a motherboard setting on your end

You have an nvme...

I do not have one of those

maybe you need extra steps to take

I would investigate that

I am saying this because of this /usr/bin/grub-probe: warning: unknown device type nvme0n1.

Are all the motherboard settings correct?
Learn, have fun and enjoy.
But first use the power of the Arch Wiki
use the tutorials on https://www.youtube.com/erikdubois
then use the power of google
then use the power of our moderators.
jon5th5n
recruit crewman
Posts: 2
Joined: Fri Jun 21, 2024 6:59 pm

erikdubois wrote: Sat Jun 22, 2024 10:13 am ERROR: mkdir /var/lock/dmraid

that is something we never see - maybe a motherboard setting on your end

You have an nvme...

I do not have one of those

maybe you need extra steps to take

I would investigate that

I am saying this because of this /usr/bin/grub-probe: warning: unknown device type nvme0n1.

Are all the motherboard settings correct?
I'm on a Laptop (Asus Zenbook 14 Flip (UN5401QA)) so I never really had to do with its motherboard. Do you maybe have any idea on what I could do to try to investigate this further?

I will later take a look around the Internet to see if grub maybe has some problems with nvme drives and if this is a known issue.

Also as you may have noticed I really struggle to get behind the workings of the bootloader and it's setup process so I am really lost here.
User avatar
erikdubois
Captain
Posts: 5909
Joined: Tue Nov 07, 2017 3:45 pm
Location: Belgium
Contact:

We do have a lot of videos about bootloaders

We have pacman hooks to do the work for us. That might be also a reason why things go wrong when on nvme.

start there to learn about bootloaders and research other videos

certainly read the arch wiki
Learn, have fun and enjoy.
But first use the power of the Arch Wiki
use the tutorials on https://www.youtube.com/erikdubois
then use the power of google
then use the power of our moderators.
User avatar
fennec
Ensign
Posts: 178
Joined: Wed Dec 28, 2022 9:54 pm
Location: UK
Contact:

- I didn't find 'vmlinuz-linux' anywhere in the /boot/ folder hierarchy which in general seemed weirdly empty
- I tried 'pacman -S(yu) linux' but nothing changed at all
/usr/share/libalpm/hooks/90-mkinitcpio-install.hook runs whenever a kernel gets installed to /usr/lib/modules/*/vmlinuz by pacman. It calls /usr/share/libalpm/scripts/mkinitcpio-install, which installs the kernel to /boot for you. If this mechanism is broken on your system, check your pacman log inside /var/log/pacman.log and see if 90-mkinitcpio-install.hook was called at all following a kernel update, and what the output was.
User avatar
erikdubois
Captain
Posts: 5909
Joined: Tue Nov 07, 2017 3:45 pm
Location: Belgium
Contact:

Can we close this post?
Learn, have fun and enjoy.
But first use the power of the Arch Wiki
use the tutorials on https://www.youtube.com/erikdubois
then use the power of google
then use the power of our moderators.
Post Reply

Return to “Kernel & Hardware”