My pc dont boot today

General system Kernel, boot, graphics & hardware
21

I can’t notice anything suspicious in the log part.

Was it the complete log from the previous boot?

What utility do you use for updating your system? The proper update command is pacman -Syu, not pacman -Sy <package list>, even if it may not have to do with the current problem.

There are a couple of issues on Archlinux packaging currently, that may have hit you (and maybe others), so some more investigation would be necessary from EnOS devs. (I mean a recent mkinitcpio change, that could potentially break some hooks) :no_mouth:

22

neither do i, what i can make out with my modest knowledge

yes, the complete log from yesterday.

i use the endevouros tool update in terminal.
sometimes i use yay but not yesterday. yesterday i used update-in-terminal from eos.

what do you think i can do?
i really don’t feel like doing a complete reinstallation

23

This might (or not :upside_down_face:) help.

Depending on your boot mode and filesystem, follow the instructions given in Discovery articles to arch-chroot into your system.

Once in chroot:

  1. pacman -Syu
  2. mkinitcpio -P
  3. grub-install
  4. grub-mkconfig -o /boot/grub/grub.cfg
  5. exit

Cross your fingers and reboot!

:crossed_fingers:t5:

2 Likes
24

hey @pebcak thanks.
i followed your instructions until grub-install. grub-install gives the following error message

grub-install: error: cannot find EFI directory.

sudo fsblk -f
nvme0n1
nvme0n1p1 vfat FAT32 NO_LABEL 1166-16BF  /mnt/boot/efi
nvme0n1p2 ext4 1.0  UUID                 /mnt

what can i do?

25

Just to make sure: did you do this:

sudo arch-chroot /mnt

?

26

no, just

sudo mount /dev/nvme0n1p2 /mnt
sudo mount /dev/nvme0n1p1 /mnt/boot-efi

27

You need to run the arch-chroot command as well to change to the root of your installed system.

sudo arch-chroot /mnt

28

ok ill try it again. is this the right way then?

sudo arch-chroot mount /dev/nvme0n1p2 /mnt

and

sudo arch-chroot mount /dev/nvme0n1p1 /mnt/boot-efi

29

You have already mounted the partitions. So just:

sudo arch-chroot /mnt

30

I thought it was this or am i wrong?

sudo mount /dev/nvme0n1p1 /mnt/boot/efi

Not -efi???

31

Must be a typo.

Looking at lsblk output, they seem to be mounted correctly.

1 Like
32

@pebcak

that was it. thanks a lot. you are my hero for today :man_superhero:

1 Like
33

i’m really sorry that i had to ask so many times. but i’m not a specialist in this subject. thanks again to all of you

34

That’s great news!
Glad you could recover your system! It’s always a relief!

:enos_flag: :handshake:t5:

2 Likes
35

This same thing happened to me yesterday with respect to grub2-theme-endeavouros although mine booted. It was during the update that it said the package was missing. So in the instructions in another post it said to remove it and edit grub config file to not load the theme. When i removed it then it booted with an error and if i pressed enter i had the black themed menu. So i edited the grub file and then it only booted to firmware. I lost my dual boot windows but could get into Windows with F8 key. I had btrfs setup and i got annoyed and just reinstalled because i didn’t have the time to go through it. This was a bit quicker and easier to resolve. I’m just wondering what’s up with this grub2-theme-endeavouros package and grub?

1 Like
36

me too :wink:

1 Like
37

same here, i also read it in another thread and uninstalled grub2-theme-endeavouros. but i did not make any change in the boot config file.

I wonder about that, too.

1 Like
38

i really need to move some important data to an external hard drive. i can’t imagine not having access to it and my super important data would no longer be available.

1 Like
39

in the end thanks to @pebcak i am now expert in restoring the grub with chroot :laughing:

1 Like
40

This has happened to most of us.
When you do it once, you’ll get the hang of it.
When you do it twice, it’ll become your second nature :sweat_smile:

1 Like