First install Manjaro dualboot with Win10 on Thinkpad. Not able to boot with grub

Hi everyone.

After using diverse Linux distributions on VMs I decided, that I finally want to have a ‘real’ Linux installation and that Manjaro (kde) will be my preferred Distro for that :slight_smile:

Due to some programs I need for my studies I have to use a dual boot with Windows 10 on my Thinkpad T14s.
Unfortunately I am not able to boot properly.

I installed everything according to this manual:

https://forum.manjaro.org/t/root-tip-dual-boot-manjaro-and-windows/1164

After only to be able to directly boot to Windows I discovered a missing boot flag and I did a second install (was still missing), then added the boot flag manually but had the same outcome. After I tried this:

https://archived.forum.manjaro.org/t/using-livecd-v17-0-1-and-above-as-grub-to-boot-os-with-broken-bootloader/24916

And over grub prompt

grub> search.file /etc/manjaro-release  root
grub> configfile /boot/grub/grub.cfg

I am able to get to grub and at least boot Manjaro. I updated grub, however it is still not showing up when booting.
Interesting is, that if I go into the boot menu when I start my notebook I have Manjaro in the menu (actually twice now…) but if i choose it, screen gets just blank for one second and I’m back at it, not able to boot Manjaro but only Windows.

Since this is my first install of Manjaro (or any Linux system) I am a bit out of ideas and googling solutions now. I wonder if it is maybe a firmware problem with my Notebook (I found a thread about it but I am a bit hesitant trying that) or if I just totally messed up with my installation :frowning:

If someone here could help me I would be very glad.

sudo parted -l

Model: disk2go wood (scsi)
Disk /dev/sda: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 2      2836MB  2841MB  4194kB  primary               esp


Model: SAMSUNG MZVLB256HBHQ-000L7 (nvme)
Disk /dev/nvme0n1: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name                          Flags
 1      1049kB  274MB  273MB   fat32           EFI system partition          boot, hidden, esp
 2      274MB   290MB  16.8MB                  Microsoft reserved partition  msftres
 3      290MB   129GB  129GB   ntfs            Basic data partition          msftdata
 5      129GB   130GB  537MB   fat32                                         boot, legacy_boot, esp
 6      130GB   134GB  4295MB  linux-swap(v1)                                swap, legacy_boot
 7      134GB   189GB  54.5GB  ext4
 8      189GB   255GB  66.3GB  ext4
 4      255GB   256GB  1049MB  ntfs            Basic data partition          hidden, diag

efibootmgr -v

BootCurrent: 001B
Timeout: 0 seconds
BootOrder: 0002,0001,0000,0017,0018,0019,001A,001B,001C
Boot0000* Windows Boot Manager	HD(1,GPT,78be2365-885c-4a26-aa4e-1434b85b96aa,0x800,0x82000)/File(\EFI\manjaro\grubx64.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...B................
Boot0001* manjaro	HD(5,GPT,7bae3102-c048-594d-bac8-d1da86041771,0xf100000,0x100000)/File(\EFI\manjaro\grubx64.efi)
Boot0002* manjaro	HD(1,MBR,0x0,0x40,0x548718)/File(\EFI\Manjaro\grubx64.efi)
Boot0010  Setup	FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu	FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012  Diagnostic Splash Screen	FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013  Lenovo Diagnostics	FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014  ThinkShield secure wipe	FvFile(3593a0d5-bd52-43a0-808e-cbff5ece2477)
Boot0015  Startup Interrupt Menu	FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0016  Rescue and Recovery	FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot0017* USB CD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0018* USB FDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0019* NVMe0	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Boot001A* ATA HDD0	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot001B* USB HDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot001C* PXE BOOT	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot001D  Regulatory Information	FvFile(478c92a0-2622-42b7-a65d-5894169e4d24)
Boot001E* Boot Next Boot Option	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,a7ca6d35b2c2684783721826a7404894)

sudo blkid

/dev/nvme0n1p1: LABEL="SYSTEM" UUID="AAA4-C0F8" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="78be2365-885c-4a26-aa4e-1434b85b96aa"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="d4f524ca-bb8b-4d1c-8929-66afd26c1dc3"
/dev/nvme0n1p3: LABEL="Windows" BLOCK_SIZE="512" UUID="01D734A789A4F130" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="9f73d20e-03f9-4aac-af0d-86f9b5c76215"
/dev/nvme0n1p4: LABEL="WinRE_DRV" BLOCK_SIZE="512" UUID="8EBEA722BEA70237" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="898089b9-b1a7-433e-aba7-f44cd83d863f"
/dev/nvme0n1p5: LABEL_FATBOOT="NO_LABEL" LABEL="NO_LABEL" UUID="DBF0-3389" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="7bae3102-c048-594d-bac8-d1da86041771"
/dev/nvme0n1p6: UUID="ead25be8-0f34-419d-b61a-4cdba2810844" TYPE="swap" PARTUUID="5a078a9c-e8af-8046-b385-3b9a00da9a27"
/dev/nvme0n1p7: UUID="2b7cea6d-3e9a-44fc-b430-4f930fb75f74" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="035b3ecd-bcbc-6d4c-93be-01bdf3b5ecc8"
/dev/nvme0n1p8: UUID="670313e3-170c-482f-9954-85bafea28604" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="7ea2a876-d21d-4146-bb5a-6b9c11c839d6"
/dev/sda1: BLOCK_SIZE="2048" UUID="2021-04-18-14-54-58-00" LABEL="MANJARO_KDE_2102" TYPE="iso9660"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="MISO_EFI" LABEL="MISO_EFI" UUID="3DA9-7D51" BLOCK_SIZE="512" TYPE="vfat"

findmnt -s

TARGET    SOURCE                                    FSTYPE OPTIONS
/boot/efi UUID=DBF0-3389                            vfat   umask=0077
/         UUID=2b7cea6d-3e9a-44fc-b430-4f930fb75f74 ext4   defaults,noatime
/home     UUID=670313e3-170c-482f-9954-85bafea28604 ext4   defaults,noatime

findmnt /boot/efi

TARGET    SOURCE         FSTYPE OPTIONS
/boot/efi /dev/nvme0n1p5 vfat   rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro

sudo tree /boot/efi

/boot/efi
└── EFI
    ├── boot
    │   └── bootx64.efi
    └── Manjaro
        └── grubx64.efi

3 directories, 2 files

Thank you very much in advance!

I think your partitioning seems odd, you have two ext 4 partitions, swap has legacy_boot flag?, same for your linux boot has a legacy flag, and it seems you used legacy instead of uefi to create your live usb.

Couple of questions that may help troubleshoot:

  • Is your windows installed as uefi or legacy?
  • did you disable secure boot
  • did you resize your windows partition and create a free partition in windows for your linux install?

Once you created that free partition in windows you just select it to install manjaro. That may be easiest to get started.

Is your windows installed as uefi or legacy?

as uefi

did you disable secure boot

yes

did you resize your windows partition and create a free partition in windows for your linux install?

yes that’s what I did. I did it according to the manual from this forum I posted above. Thats also why I have two ext4 partitions (root and home), because it was recommended there.

, swap has legacy_boot flag?, same for your linux boot has a legacy flag

that is something that is confusing me yes… they were there right after the install.

and it seems you used legacy instead of uefi to create your live usb

That’s a good remark. I will look into that more precise. I used the programm Rufus for the image, but I could not choose much options.

So I decided to do all over again and made a fresh live usb, this time with Ventoy.
But once again after the installation swap and linux boot have a legacy_boot flag (though I got rid of the second boot manjaro boot section) and it starts up to windows only.
No chance to get into grub except over live USB and grub prompt.

I also used rEFInd boot manager to make sure I have an EFI boot and it works (can also boot into Manjaro over it).

Is there a way to get rid of the legacy_boot flags and could that be the problem?

edit: looks now like this:

efibootmgr -v

BootCurrent: 001B
Timeout: 0 seconds
BootOrder: 0001,0000,0017,0018,0019,001A,001B,001C
Boot0000* Windows Boot Manager	HD(1,GPT,78be2365-885c-4a26-aa4e-1434b85b96aa,0x800,0x82000)/File(\EFI\manjaro\grubx64.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...B................
Boot0001* Manjaro	HD(5,GPT,7bae3102-c048-594d-bac8-d1da86041771,0xf100000,0x100000)/File(\EFI\Manjaro\grubx64.efi)
Boot0010  Setup	FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011  Boot Menu	FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012  Diagnostic Splash Screen	FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013  Lenovo Diagnostics	FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014  ThinkShield secure wipe	FvFile(3593a0d5-bd52-43a0-808e-cbff5ece2477)
Boot0015  Startup Interrupt Menu	FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0016  Rescue and Recovery	FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot0017* USB CD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0018* USB FDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0019* NVMe0	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Boot001A* ATA HDD0	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot001B* USB HDD	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot001C* PXE BOOT	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot001D  Regulatory Information	FvFile(478c92a0-2622-42b7-a65d-5894169e4d24)
Boot001E* Boot Next Boot Option	VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,a7ca6d35b2c2684783721826a7404894)

sudo parted -l

Model: SAMSUNG MZVLB256HBHQ-000L7 (nvme)
Disk /dev/nvme0n1: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name                          Flags
 1      1049kB  274MB  273MB   fat32           EFI system partition          boot, hidden, esp
 2      274MB   290MB  16.8MB                  Microsoft reserved partition  msftres
 3      290MB   129GB  129GB   ntfs            Basic data partition          msftdata
 5      129GB   130GB  537MB   fat32                                         boot, legacy_boot, esp
 6      130GB   134GB  4295MB  linux-swap(v1)                                swap, legacy_boot
 7      134GB   189GB  54.5GB  ext4
 8      189GB   255GB  66.3GB  ext4
 4      255GB   256GB  1049MB  ntfs            Basic data partition          hidden, diag

I could now solve the problem.
I did mount grub to the Windows EFI partition and not as a separate partition - as it is descriped in the tutorial I mentioned in the first post.
(Means I will most problably need to repair grub after Win updates in the future, but I think I will switch to rEFInd bootloader later).

Though I dont now why it did not work as descriped in the manual, since a rEFInd install was also not able to boot and the Laptop was not able to boot at all wenn I excluded the Win bootloader. Maybe it has really something to do with the notebook, don’t know.
However installing it directly on the Windows EFI partition does the trick for now.

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