Error: premature end of file /vmlinuz-linux

General system Newbie
1

Hello Everyone I’m relatively new to using linux, and after doing pacman -Syu the system crashed and on reboot I’ve been getting this error.

IMG_20230717_100817
IMG_20230717_1008171920×1442 196 KB

After reading the forum, some people had similar issues so I followed these steps:

  1. Live boot into EOS.
  2. sudo lsblk -f
  3. sudo mount /dev/sda11 /mnt This is my root partition
  4. sudo mount /dev/sda9 /mnt This is my boot partition
  5. sudo arch-chroot /mnt

After this step I see [root@Endeavouros /] # but I do not know what is the correct step to fix the original error in the image above. If anyone could give me a command I can try it would be appreciated.

I apologize if its something trivial I’ve been using EndeavourOS for a year but never had any problems I’m really new to fixing things and I cannot do a fresh install as and my documents are in there.

If I can provide more info to explain my situation better on anything or screenshots please tell me.

Thank you.

1 Like
2

Try reinstalling your kernel when you are chrooted into your system, the exit the chroot root and reboot.
pacman -S linux

1 Like
3

Thank you trying it right now, will update you on the progress soon.

4

Screenshot_2023-07-17_11-21-15
I got this error, sorry again if these things are trivial I really do not know what I’m doing.

5

Try:

rm /var/lib/pacman/db.lck
1 Like
6

This looks wrong. You shouldn’t be mounting them to the same place.

Follow these instructions for how to chroot:
https://discovery.endeavouros.com/system-rescue/arch-chroot/2022/12/

7

Thank you so much!! It’s updating, I hope for no more errors. :smiling_face_with_tear:
Thanks again!!

Screenshot_2023-07-17_11-38-26
Screenshot_2023-07-17_11-38-26896×433 74.8 KB

3 Likes
8

Sorry for bothering again, I did the update it showed the following data.

Screenshot_2023-07-17_11-49-36
Screenshot_2023-07-17_11-49-361910×555 152 KB

After that I tried rebooting and it showed this new error.

IMG_20230717_135518
IMG_20230717_1355181920×1442 144 KB

9

Did you also mount your /boot or /efi partition before you chrooted into the system, the initramfs usually gets generated after you install the kernel and then gets placed along side the location where the kernel is installed whether that be under /boot or /efi.

1 Like
10

Yes, I mounted both by doing these.

  1. sudo mount /dev/sda11 /mnt
    2 sudo mount /dev/sda9 /mnt/boot

I understand this is what you meant by mounting the /boot partition before chrooting into the system.

11

I just did sudo mkinitcpio -p linux while chrooted cause I found someone saying it on the forum with similar problem.

Wish me luck :saluting_face:

12

With your system partition mounted, please post the content of /etc/fstab.

:bangbang:
Please don’t post screenshots.
Copy the text, paste it to your reply and press Ctrl-E to format

13

I don’t know how old your install is but there is a chance your system is already using dracut since it became the default about a year ago or less.

1 Like
14

Sorry I didn’t know won’t do it again.

15

Thank you everyone, after all your help and all these commands it’s finally working again!

For anyone facing the same problem,

sudo mkinitcpio -p linux

This was the last piece of command I used.
After doing all of the above.

1 Like
16

Then your install was from before the installer switched to dracut, although I’m surprised that doesn’t automatically get run with reinstalling a kernel. Glad that it is fixed!

1 Like
17

Ohh I really don’t know what dracut means, but I’m happy it’s updated and working.
Thanks again!

1 Like
18

https://discovery.endeavouros.com/installation/dracut/2022/12/

1 Like
19

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