Remove manjaro double from grub

Hi,

I’ve tried to remove the manjaro duplicate in the past (by manually editing a file that is generated by update-grub I think), but every update-grub brings it back. I’ve found this forum thread, but it did not provide a solution. What can I do?

What’s the output of sudo update-grub

Generating grub configuration file …
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.16-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.16-x86_64.img
Found initrd fallback image: /boot/initramfs-5.16-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Manjaro Linux on /dev/nvme0n1p2
Found Windows Boot Manager on /dev/nvme1n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings …
Detecting snapshots …
Found snapshot: 2022-07-16 20:19:06 | timeshift-btrfs/snapshots/2022-07-16_20-19-06/@ | ondemand | {timeshift-autosnap} {created before upgrade} |
Found snapshot: 2022-07-09 09:00:01 | timeshift-btrfs/snapshots/2022-07-09_09-00-01/@ | monthly | N/A |
Found snapshot: 2022-07-04 22:53:45 | timeshift-btrfs/snapshots/2022-07-04_22-53-45/@ | ondemand | {timeshift-autosnap} {created before upgrade} |
Found snapshot: 2022-06-30 22:47:10 | timeshift-btrfs/snapshots/2022-06-30_22-47-10/@ | ondemand | {timeshift-autosnap} {created before upgrade} |
Found snapshot: 2022-06-08 23:00:01 | timeshift-btrfs/snapshots/2022-06-08_23-00-01/@ | monthly | N/A |
Found snapshot: 2022-03-27 22:32:21 | timeshift-btrfs/snapshots/2022-03-27_22-32-21/@ | ondemand | N/A |
Found snapshot: 2022-03-26 06:15:17 | timeshift-btrfs/snapshots/2022-03-27_20-44-33/@ | ondemand | Before restoring ‘2022-03-27 20:39:37’ |
Found snapshot: 2021-12-27 21:12:56 | timeshift-btrfs/snapshots/2022-03-26_06-15-17/@ | ondemand | Before restoring ‘2022-03-22 21:57:30’ |
Found snapshot: 2021-12-27 00:04:05 | timeshift-btrfs/snapshots/2021-12-27_21-12-56/@ | ondemand | Before restoring ‘2021-12-27 00:04:05’ |
Found snapshot: 2021-12-26 23:48:57 | timeshift-btrfs/snapshots/2021-12-26_23-48-57/@ | ondemand | N/A |
Found 10 snapshot(s)
Unmount /tmp/grub-btrfs.Q2TGNKOSYk … Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done

Ok. It’s os-prober the one that it is finding again Manjaro. Can you also show your partition scheme to understand better the situation? Copy the output of these two commands:

sudo lsblk -f
sudo fdisk -l

Sure,

sudo lsblk -f

NAME        FSTYPE   FSVER LABEL    UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0       squashfs 4.0                                                       0   100% /var/lib/snapd/snap/core20/1587
loop1       squashfs 4.0                                                       0   100% /var/lib/snapd/snap/gnome-3-28-1804/161
loop2       squashfs 4.0                                                       0   100% /var/lib/snapd/snap/gnome-3-38-2004/106
loop3       squashfs 4.0                                                       0   100% /var/lib/snapd/snap/gtk-common-themes/1534
loop4       squashfs 4.0                                                       0   100% /var/lib/snapd/snap/gnome-3-38-2004/112
loop5       squashfs 4.0                                                       0   100% /var/lib/snapd/snap/core20/1581
loop6       squashfs 4.0                                                       0   100% /var/lib/snapd/snap/bare/5
loop7       squashfs 4.0                                                       0   100% /var/lib/snapd/snap/core18/2538
loop8       squashfs 4.0                                                       0   100% /var/lib/snapd/snap/core18/2409
loop9       squashfs 4.0                                                       0   100% /var/lib/snapd/snap/gtk-common-themes/1535
loop10      squashfs 4.0                                                       0   100% /var/lib/snapd/snap/heidisql-wine/3
loop11      squashfs 4.0                                                       0   100% /var/lib/snapd/snap/snapd/16010
loop12      squashfs 4.0                                                       0   100% /var/lib/snapd/snap/snapd/16292
loop13      squashfs 4.0                                                       0   100% /var/lib/snapd/snap/wine-platform-6-staging/46
loop14      squashfs 4.0                                                       0   100% /var/lib/snapd/snap/wine-platform-runtime/312
loop15      squashfs 4.0                                                       0   100% /var/lib/snapd/snap/wine-platform-runtime/313
nvme0n1                                                                                 
├─nvme0n1p1 vfat     FAT32 NO_LABEL EA96-E8D2                             298,8M     0% /boot/efi
├─nvme0n1p2 btrfs                   5d3bc15d-77d1-4a2b-8463-6f61a24fd39a  451,3G    76% /var/log
│                                                                                       /var/cache
│                                                                                       /home
│                                                                                       /
└─nvme0n1p3 swap     1     swap     ec3ea076-f43b-4948-a432-473e35dbfcbe                [SWAP]
nvme1n1                                                                                 
├─nvme1n1p1 vfat     FAT32          7CA1-D696                                           
├─nvme1n1p2                                                                             
├─nvme1n1p3 ntfs                    D61CA8251CA7FF1D                                    
└─nvme1n1p4 ntfs                    241AC0D51AC0A4E0

and sudo fdisk -l

Disk /dev/nvme0n1: 1,86 TiB, 2048408248320 bytes, 4000797360 sectors
Disk model: ADATA SX8200PNP                         
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: F804B52B-7F8A-A949-B9CD-1E772B7FBFA6

Device              Start        End    Sectors  Size Type
/dev/nvme0n1p1       4096     618495     614400  300M EFI System
/dev/nvme0n1p2     618496 3982340530 3981722035  1,9T Linux filesystem
/dev/nvme0n1p3 3982340531 4000795469   18454939  8,8G Linux swap


Disk /dev/nvme1n1: 476,94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: SAMSUNG MZVLB512HBJQ-000L2              
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 5DDBE9A7-20FA-41CE-8C43-02006B57E52E

Device             Start        End   Sectors   Size Type
/dev/nvme1n1p1      2048     206847    204800   100M EFI System
/dev/nvme1n1p2    206848     239615     32768    16M Microsoft reserved
/dev/nvme1n1p3    239616  999175430 998935815 476,3G Microsoft basic data
/dev/nvme1n1p4 999176192 1000212479   1036288   506M Windows recovery environment


Disk /dev/loop0: 61,96 MiB, 64970752 bytes, 126896 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 164,76 MiB, 172761088 bytes, 337424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 254,09 MiB, 266436608 bytes, 520384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 81,26 MiB, 85209088 bytes, 166424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 400,8 MiB, 420265984 bytes, 820832 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 61,96 MiB, 64966656 bytes, 126888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 4 KiB, 4096 bytes, 8 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop7: 55,56 MiB, 58261504 bytes, 113792 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop8: 55,54 MiB, 58232832 bytes, 113736 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop9: 91,69 MiB, 96141312 bytes, 187776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop10: 13,59 MiB, 14254080 bytes, 27840 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop11: 46,95 MiB, 49233920 bytes, 96160 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop12: 46,96 MiB, 49242112 bytes, 96176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop13: 383,41 MiB, 402034688 bytes, 785224 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop14: 347,14 MiB, 364003328 bytes, 710944 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop15: 347,14 MiB, 364007424 bytes, 710952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

hm… normally it should exclude the @ subvolume. Did you rename it?

sudo btrfs subvolume list /

I don’t think so, but I’m not sure.

ID 256 gen 122786 top level 5 path timeshift-btrfs/snapshots/2021-12-27_00-04-05/@
ID 257 gen 123048 top level 5 path @home
ID 258 gen 123044 top level 5 path @cache
ID 259 gen 123048 top level 5 path @log
ID 1087 gen 122786 top level 5 path timeshift-btrfs/snapshots/2021-12-26_23-48-57/@
ID 1090 gen 122786 top level 5 path timeshift-btrfs/snapshots/2021-12-27_21-12-56/@
ID 1091 gen 122786 top level 5 path timeshift-btrfs/snapshots/2022-03-26_06-15-17/@
ID 1485 gen 122786 top level 5 path timeshift-btrfs/snapshots/2022-03-27_20-44-33/@
ID 1498 gen 123048 top level 5 path @
ID 1500 gen 122786 top level 5 path timeshift-btrfs/snapshots/2022-03-27_22-32-21/@
ID 1719 gen 122786 top level 5 path timeshift-btrfs/snapshots/2022-06-08_23-00-01/@
ID 1805 gen 122786 top level 5 path timeshift-btrfs/snapshots/2022-06-30_22-47-10/@
ID 1818 gen 122786 top level 5 path timeshift-btrfs/snapshots/2022-07-04_22-53-45/@
ID 1822 gen 122786 top level 5 path timeshift-btrfs/snapshots/2022-07-09_09-00-01/@
ID 1823 gen 122786 top level 5 path timeshift-btrfs/snapshots/2022-07-16_20-19-06/@