Grub-mkconfig fails on liveusb

Support
1

Hello
I suddenly ran into an issue with grub, it started showing black grub config screen. I followed the GRUB/Restore the GRUB Bootloader - Manjaro tutorial. When I get to the grub-mkconfig it returns the following error

image
image1137×346 43.8 KB

I had something very similliar to this when I tried running os-probe. I have a dual boot Linux/Windows. My lsblk looks as follows:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0    7:0    0 152.5M  1 loop 
loop1    7:1    0     1G  1 loop 
loop2    7:2    0   1.6G  1 loop 
loop3    7:3    0 814.8M  1 loop 
sda      8:0    0 238.5G  0 disk 
|-sda1   8:1    0   100M  0 part /boot/efi
|-sda2   8:2    0    16M  0 part 
|-sda3   8:3    0 106.6G  0 part 
|-sda4   8:4    0   768M  0 part 
|-sda5   8:5    0   106G  0 part /
|-sda6   8:6    0     4G  0 part 
|-sda7   8:7    0    20G  0 part 
`-sda8   8:8    0   522M  0 part 
sdb      8:16   1  14.4G  0 disk 
|-sdb1   8:17   1   3.7G  0 part 
`-sdb2   8:18   1     4M  0 part

cat /etc/lsb-release:

DISTRIB_ID="ManjaroLinux"
DISTRIB_RELEASE="24.0.3"
DISTRIB_CODENAME="Wynsdey"
DISTRIB_DESCRIPTION="Manjaro Linux"

Thank you!

2

It doesn’t fail on live usb - it throws an error in chroot, which is not the live system, but your actual system.

I say: ignore the errors - not important or fatal.

What is /dev/sdb1 and /dev/sdb2 which the errors are about?
Likely not needed at all during this operation.

You should install a second kernel while you are in chroot -
linux66 for instance

Don’t know whether linux65 (which you have) is still supported.

3

Kernel 6.5.x reached EOL a month (or more) ago; I can only parrot the recommendation to remove it. Kernel 6.6 (LTS) is suggested, or probably 6.9, or even 6.10 if one wishes to compute close to the edge, without falling off.

4

/dev/sdb* are just my thumb drive partitions, so they are not important at all.

5

Thanks. Never updated my kernel ever, probably time to do that. Is it done somehow manually? I try to keep the system up to date all the time, isn’t kernel updated along with pacman -Sy?

6

This link will explain all; and yes, they are updated automatically (within the same major kernel releases):

In the case of kernels, using mhwd-kernel is preferred rather than pacman (or any other method). Again this link explains in more detail.

Cheers.

1 Like
7

Thank you!

8

I’d hazard a guess that the presence of the EOL kernel is what is causing the issue.

The OS will normally notify you when a kernel goes out of date and remind you to upgrade.

9

I updated the system and ran sudo update-grub. Even though the live usb helped with the black screen of grub, I couldn’t get the grub to show Windows as a bootable option, but update-grub nailed it down. Thanks to everybody, the issue seems to be resolved so I’m closing the thread

1 Like
10

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