# /boot/vmlinuz-linux not found

**URL:** <https://forum.endeavouros.com/t/boot-vmlinuz-linux-not-found/37519>\
**Category:** EndeavourOS installation\
**Created:** [February 20, 2023, 10:54am UTC](https://forum.endeavouros.com/t/boot-vmlinuz-linux-not-found/37519 "2023-02-20T10:54:15Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![erw1](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/e/97f17d/32.png) [@erw1](https://forum.endeavouros.com/u/erw1)\
**Post date:** [February 20, 2023, 10:54am UTC](https://forum.endeavouros.com/t/boot-vmlinuz-linux-not-found/37519/1 "2023-02-20T10:54:15Z")

</div>

Continued from here ([upgrade](https://forum.endeavouros.com/t/warning-too-many-errors-from-mirror/37499/4)). On startup, I get this:

GNU GRUB 2:2.06.r380.g151467888-1

Loading linux linux  
error file /boot/vmlinuz-linux not found  
loading initial ramdisk…  
error: you need to load the kernel first.

Minimal bash editing is supported. Is there anything I could do with that?

I’ve got a not too old timeshift bkup, if it comes to that.

---

<div class="post-metadata">

**Author:** ![pebcak](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pebcak/32/100472_2.png) [@pebcak](https://forum.endeavouros.com/u/pebcak)\
**Post date:** [February 20, 2023, 12:10pm UTC](https://forum.endeavouros.com/t/boot-vmlinuz-linux-not-found/37519/2 "2023-02-20T12:10:37Z")

</div>

You might need to arch-chroot into your installed system and update your system and perhaps also reinstall your kernels.

Please consult the wiki for how-to: [https://discovery.endeavouros.com/](https://discovery.endeavouros.com/)

---

<div class="post-metadata">

**Author:** ![erw1](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/e/97f17d/32.png) [@erw1](https://forum.endeavouros.com/u/erw1)\
**Post date:** [February 20, 2023, 10:00pm UTC](https://forum.endeavouros.com/t/boot-vmlinuz-linux-not-found/37519/4 "2023-02-20T22:00:53Z")

</div>

This is continued from [here](https://forum.endeavouros.com/t/boot-vmlinuz-linux-not-found/37519/2). Basically, I can’t boot, so I’m following the suggestion to try [arch-chroot](https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/). But apparently I’m not doing it right. Any suggestion?

```auto
$ sudo lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0
     squash 4.0 0 100% /run/archiso/airootfs
sda                                                                         
└─sda1
     crypto 1 eb5e7c19-f213-4e7e-8e9c-ca078478ffa2                
  └─luks-eb5e7c19-f213-4e7e-8e9c-ca078478ffa2
     ext4 1.0 9f33797e-8d9a-49c8-8c31-65b8bcc228fa 234.4G 44% /run/media/liveuser/9f33797e-8d9a-49c8-8c31-65b8bcc228fa
$ sudo arch-chroot run/media/liveuser/9f33797e-8d9a-49c8-8c31-65b8bcc228fa
==> ERROR: Can't create chroot on non-directory run/media/liveuser/9f33797e-8d9a-49c8-8c31-65b8bcc228f

```

---

<div class="post-metadata">

**Author:** ![dalto](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/dalto/32/5577_2.png) [@dalto](https://forum.endeavouros.com/u/dalto)\
**Post date:** [February 20, 2023, 10:06pm UTC](https://forum.endeavouros.com/t/boot-vmlinuz-linux-not-found/37519/5 "2023-02-20T22:06:57Z")

</div>

First, please don’t keep creating new topics that are “continued”. Just use the existing topic. I merged these back together.

It should be:

```plaintext
sudo arch-chroot /run/media/liveuser/9f33797e-8d9a-49c8-8c31-65b8bcc228fa

```

You omitted the leading slash.

---

<div class="post-metadata">

**Author:** ![erw1](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/e/97f17d/32.png) [@erw1](https://forum.endeavouros.com/u/erw1)\
**Post date:** [February 20, 2023, 10:11pm UTC](https://forum.endeavouros.com/t/boot-vmlinuz-linux-not-found/37519/6 "2023-02-20T22:11:19Z")

</div>

OK.

Having chrooted into my installed system, is there any diagnostic I could run to decide what to do next?

```auto
$ sudo arch-chroot /run/media/liveuser/9f33797e-8d9a-49c8-8c31-65b8bcc228fa
# ls
bin crypto_keyfile.bin etc	lib lost+found opt root sbin sys	tmp var
boot dev home	lib64 mnt proc run srv timeshift	usr
# ls home
user

```

---

<div class="post-metadata">

**Author:** ![dalto](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/dalto/32/5577_2.png) [@dalto](https://forum.endeavouros.com/u/dalto)\
**Post date:** [February 20, 2023, 10:12pm UTC](https://forum.endeavouros.com/t/boot-vmlinuz-linux-not-found/37519/7 "2023-02-20T22:12:23Z")

</div>

You probably need to use:

```plaintext
pacman -Syu linux

```

That will reinstall the kernel and trigger all the hooks which create the kernel image and the boot images.

---

<div class="post-metadata">

**Author:** ![system](https://forum.endeavouros.com/uploads/default/original/2X/9/9ea52f9fd5ef8e609e593c362d61a36295f48be8.png) [@system](https://forum.endeavouros.com/u/system)\
**Post date:** [February 22, 2023, 10:12pm UTC](https://forum.endeavouros.com/t/boot-vmlinuz-linux-not-found/37519/8 "2023-02-22T22:12:52Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.