Duplicate grub entries for Manjaro

Support
1

It seems that my post got removed regarding this issue probably with the forum outage.

I have 2 entries for the same OS in my Grub boot menu

The top one says Manajro the other says Manjaro on nvme0p1 -which is where Manajro is.

I should point out the filesystem being used is btrfs

I have tried a Timeshift rollback - didnt affect anything

I have tried booting from install media and running manjaro-chroot -a - didnt work, It couldn’t find any Linux partitions

I tried sudo update-grub - didnt affect anything

I found another fixit guide for Garuda that involved mounting the subvolune @ from the install media but it wouldn’t let me mount it.

the example that was given was

sudo mkdir /mnt
sudo mount /dev/sdxy /mnt ( I assume I replace sdxy with my drive which is nvme0p1)
sudo garuda-chroot /mnt/@ (to be replaced with manjaro-chroot)

This failed at the mount part.

I was given a bunch of fixes on this forum that where basically update-grub but with other variables.

I dont have the references to these as they are gone now after the forum outage.

I know this is only a cosmetic issue with a duplicate entry in Grub but its annoying the hell out of me to the point that Im ready to re-install. But I know to someone with half an idea this should be an easy fix.

Can someone help?

Also question number 2. If I do re-install can I restore a rescuezilla backup? I made the backup AFTER I found the duplicate entry issue. Will the backup have the same issue? Im guessing yes.

2

Hi @thedatabug,

There are 2 entries for each installed kernel - the normal, every day one and the “fallback” one. That’s perfectly normal and how it should be. It’s probably this.

To confirm, please return the output of:

grep "menuentry '" /boot/grub/grub.cfg
3

If it ain’t broke, don’t fix it

:footprints:

4 
grep "menuentry '" /boot/grub/grub.cfg

menuentry 'Manjaro Linux' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-404cc3b3-e737-4e2c-b8d3-edd4960f341b' {
        menuentry 'Manjaro Linux (Kernel: 6.7.1-1-MANJARO x64)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.7.1-1-MANJARO x64-advanced-404cc3b3-e737-4e2c-b8d3-edd4960f341b' {
        menuentry 'Manjaro Linux (Kernel: 6.7.1-1-MANJARO x64 - fallback initramfs)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.7.1-1-MANJARO x64-fallback-404cc3b3-e737-4e2c-b8d3-edd4960f341b' {
        menuentry 'Manjaro Linux (Kernel: 6.6.13-1-MANJARO x64)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.6.13-1-MANJARO x64-advanced-404cc3b3-e737-4e2c-b8d3-edd4960f341b' {
        menuentry 'Manjaro Linux (Kernel: 6.6.13-1-MANJARO x64 - fallback initramfs)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-6.6.13-1-MANJARO x64-fallback-404cc3b3-e737-4e2c-b8d3-edd4960f341b' {
menuentry 'Manjaro Linux (on /dev/nvme0n1p2)' --class manjaro --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-404cc3b3-e737-4e2c-b8d3-edd4960f341b' {
        menuentry 'Manjaro Linux (on /dev/nvme0n1p2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/@/boot/vmlinuz-6.7-x86_64--404cc3b3-e737-4e2c-b8d3-edd4960f341b' {
        menuentry 'Manjaro Linux (Kernel 6.7.1-1-MANJARO x64) (on /dev/nvme0n1p2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/@/boot/vmlinuz-6.7-x86_64--404cc3b3-e737-4e2c-b8d3-edd4960f341b' {
        menuentry 'Manjaro Linux (Kernel 6.7.1-1-MANJARO x64 - fallback initramfs) (on /dev/nvme0n1p2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/@/boot/vmlinuz-6.7-x86_64--404cc3b3-e737-4e2c-b8d3-edd4960f341b' {
        menuentry 'Manjaro Linux (Kernel 6.6.13-1-MANJARO x64) (on /dev/nvme0n1p2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/@/boot/vmlinuz-6.6-x86_64--404cc3b3-e737-4e2c-b8d3-edd4960f341b' {
        menuentry 'Manjaro Linux (Kernel 6.6.13-1-MANJARO x64 - fallback initramfs) (on /dev/nvme0n1p2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/@/boot/vmlinuz-6.6-x86_64--404cc3b3-e737-4e2c-b8d3-edd4960f341b' {
        menuentry 'Memory Tester (memtest86+) (on /dev/nvme0n1p2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/@/boot/memtest86+/memtest.bin--404cc3b3-e737-4e2c-b8d3-edd4960f341b' {
        menuentry 'Memory Tester (memtest86+) (on /dev/nvme0n1p2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/@/boot/memtest86+/memtest.efi--404cc3b3-e737-4e2c-b8d3-edd4960f341b' {
        menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {
5

Im replying to my own problem.

I managed to fix it myself. After having been given a lot of clues as to where to look I edited the main grub.cfg file

sudo micro /boot/grub/grub.cfg

I then found the section pointing to Manajro on nvmep1 and deleted it. (the duplicate)

I had a brown pant moment rebooting and yes all was well.

I have no idea wether the entry will come back if os-probe is run but for now at least my grub menu is as it should be.

EDIT:

Doing the above is a fix of sorts but only temporary. The duplicate entry will re-appear whenever you

sudo update-grub

I have found a more long term and less destructive method on a Ubuntu forum.

Basically the issue is os-prober. Im not sure on the technical details but if you do the following:

sudo chmod -x /etc/grub.d/30_os-prober
sudo grub-mkconfig -o /boot/grub/grub.cfgsudo update-grub

The first command basically disables the os-prober entry in the grub directory to be non-executable. An alternative fix would be to un-install os-prober but this could lead to further issues down the road. This method just disables it without removing it all together.

The second line will re-create the grub menu without os-probers input. which will remove the duplicate entry.

My explanation may not be absolutely technically correct but it is the gist of what going on. I leave this here for other who may run into this issue.

1 Like
6

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