Problem with Booting on Grub

Hello Guys

I installed Manjaro Linux as dualboot to Windows. So Yesterday I would like to try an other Linux and installed OpenSuse Tumbleweed. Everything worked fine but after the Installation, when the computer restarted, my BIOS didn’t find something to boot on it. So I can’t boot on Windows, Manjaro or OpenSuse. I’m trying to solve the problem with Manjaro. I can boot on Manjaro on my SSD with the Stick. I tried “efibootmgr” but the this was the response:
sudo efibootmgr -c -d /dev/nvme0p -p 1 -L “manjaro” -l “\EFI\Manjaro\grubx64.efi”
EFI variables are not supported on this system.

I already tried “update-grub” and he it worked everything without an error and saw opensuse too. I’m booting with legacy. Is there a way to add grub to my bios?

I hope my English is not to bad and Thanks in advance.

If you want UEFI you cannot boot in legacy mode. Pls boot your manjaro an post output of:

inxi -Fxxxz
fdisk -l
lsblk
ls -l /boot/efi/EFI

But obviously you have setup at least manjaro with MBR.

Ah okay, yeah I setup Manjaro with MBR

My Outputs:
inxi -Fxxxz

System:    Host: michi-pc Kernel: 4.14.78-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.2.1 
           Desktop: Cinnamon 3.8.9 wm: muffin dm: LightDM 1.28.0 Distro: Manjaro Linux 
Machine:   Type: Laptop System: LENOVO product: 20L5CTO1WW v: ThinkPad T480 serial: <filter> Chassis: type: 10 
           serial: <filter> 
           Mobo: LENOVO model: 20L5CTO1WW v: SDK0J40697 WIN serial: <filter> UEFI [Legacy]: LENOVO 
           v: N24ET39W (1.14 ) date: 05/22/2018 
Battery:   ID-1: BAT0 charge: 21.9 Wh condition: 22.6/23.9 Wh (95%) volts: 12.5/11.4 model: LGC 01AV489 
           type: Li-poly serial: <filter> status: Unknown cycles: 5 
           ID-2: BAT1 charge: 27.3 Wh condition: 46.5/47.5 Wh (98%) volts: 11.1/10.8 model: LGC 01AV491 
           type: Li-ion serial: <filter> status: Discharging cycles: 20 
CPU:       Topology: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP arch: Kaby Lake rev: A 
           L2 cache: 8192 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31880 
           Speed: 600 MHz min/max: 400/4000 MHz Core speeds (MHz): 1: 636 2: 609 3: 646 4: 647 5: 646 6: 604 
           7: 604 8: 602 
Graphics:  Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:5917 
           Device-2: NVIDIA GP108M [GeForce MX150] driver: N/A bus ID: 01:00.0 chip ID: 10de:1d10 
           Display: x11 server: X.Org 1.20.2 driver: intel resolution: 2560x1440~60Hz 
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 620 (Kabylake GT2) v: 4.5 Mesa 18.2.3 compat-v: 3.0 
           direct render: Yes 
Audio:     Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 chip ID: 8086:9d71 
           Sound Server: ALSA v: k4.14.78-1-MANJARO 
Network:   Device-1: Intel Ethernet I219-V vendor: Lenovo driver: e1000e v: 3.2.6-k port: efa0 bus ID: 00:1f.6 
           chip ID: 8086:15d8 
           IF: enp0s31f6 state: down mac: <filter> 
           Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: efa0 bus ID: 03:00.0 
           chip ID: 8086:24fd 
           IF: wlp3s0 state: up mac: <filter> 
           IF-ID-1: wwp0s20f0u6 state: down mac: <filter> 
Drives:    Local Storage: total: 953.87 GiB used: 213.01 GiB (22.3%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLB1T0HALR-000L7 size: 953.87 GiB speed: 31.6 Gb/s 
           lanes: 4 serial: <filter> rev: 4L2QEXA7 scheme: GPT 
Partition: ID-1: / size: 33.39 GiB used: 28.04 GiB (84.0%) fs: ext4 dev: /dev/nvme0n1p5 
           ID-2: /home size: 200.86 GiB used: 184.97 GiB (92.1%) fs: ext4 dev: /dev/nvme0n1p6 
           ID-3: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p7 
Sensors:   System Temperatures: cpu: 31.0 C mobo: N/A 
           Fan Speeds (RPM): cpu: 0 
Info:      Processes: 347 Uptime: 1h 25m Memory: 15.20 GiB used: 1.90 GiB (12.5%) Init: systemd v: 239 
           Compilers: gcc: 8.2.1 clang: 7.0.0 Shell: bash v: 4.4.23 running in: gnome-terminal inxi: 3.0.26 

fdisk -l

Disk /dev/nvme0n1: 953.9 GiB, 1024209543168 bytes, 2000409264 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
Disklabel type: gpt
Disk identifier: C58C6883-E2F1-460C-89BD-8F45F96B3CE3

Device               Start        End   Sectors   Size Type
/dev/nvme0n1p1        2048     534527    532480   260M EFI System
/dev/nvme0n1p2      534528     567295     32768    16M Microsoft reserved
/dev/nvme0n1p3      567296  518711295 518144000 247.1G Microsoft basic data
/dev/nvme0n1p4  1998360576 2000408575   2048000  1000M Windows recovery environment
/dev/nvme0n1p5   518711296  590391295  71680000  34.2G Linux filesystem
/dev/nvme0n1p6   590391296 1020471295 430080000 205.1G Linux filesystem
/dev/nvme0n1p7  1020471296 1053239295  32768000  15.6G Linux swap
/dev/nvme0n1p8  1053239296 1063479295  10240000   4.9G Microsoft basic data
/dev/nvme0n1p9  1527320576 1998360575 471040000 224.6G Linux filesystem
/dev/nvme0n1p10 1063479296 1063495679     16384     8M BIOS boot
/dev/nvme0n1p11 1063495680 1105438719  41943040    20G Linux filesystem
/dev/nvme0n1p12 1105438720 1527320575 421881856 201.2G Linux filesystem

Partition table entries are not in disk order.


Disk /dev/loop0: 201.1 MiB, 210825216 bytes, 411768 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: 42.1 MiB, 44183552 bytes, 86296 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: 194.9 MiB, 204382208 bytes, 399184 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: 478.2 MiB, 501399552 bytes, 979296 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: 172.5 MiB, 180871168 bytes, 353264 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: 141.3 MiB, 148197376 bytes, 289448 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: 162.9 MiB, 170766336 bytes, 333528 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: 135.8 MiB, 142352384 bytes, 278032 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: 87.9 MiB, 92123136 bytes, 179928 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: 458.3 MiB, 480579584 bytes, 938632 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: 200.9 MiB, 210673664 bytes, 411472 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: 201.3 MiB, 211075072 bytes, 412256 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: 87 MiB, 91160576 bytes, 178048 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: 86.9 MiB, 91099136 bytes, 177928 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: 477.9 MiB, 501075968 bytes, 978664 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: 194.6 MiB, 204070912 bytes, 398576 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/loop16: 34.7 MiB, 36323328 bytes, 70944 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/loop17: 143.5 MiB, 150441984 bytes, 293832 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/loop18: 135.8 MiB, 142352384 bytes, 278032 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/loop19: 135.8 MiB, 142352384 bytes, 278032 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/loop20: 193.7 MiB, 203042816 bytes, 396568 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/loop21: 143.5 MiB, 150433792 bytes, 293816 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/loop22: 172.1 MiB, 180424704 bytes, 352392 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

lsblk

NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0          7:0    0 201.1M  1 loop /var/lib/snapd/snap/hiri/53
loop1          7:1    0  42.1M  1 loop /var/lib/snapd/snap/gtk-common-themes/701
loop2          7:2    0 194.9M  1 loop /var/lib/snapd/snap/firefox/118
loop3          7:3    0 478.2M  1 loop /var/lib/snapd/snap/libreoffice/86
loop4          7:4    0 172.5M  1 loop /var/lib/snapd/snap/spotify/19
loop5          7:5    0 141.3M  1 loop /var/lib/snapd/snap/chromium/506
loop6          7:6    0 162.9M  1 loop /var/lib/snapd/snap/spotify/16
loop7          7:7    0 135.8M  1 loop /var/lib/snapd/snap/discord/72
loop8          7:8    0  87.9M  1 loop /var/lib/snapd/snap/core/5662
loop9          7:9    0 458.3M  1 loop /var/lib/snapd/snap/libreoffice/76
loop10         7:10   0 200.9M  1 loop /var/lib/snapd/snap/hiri/55
loop11         7:11   0 201.3M  1 loop /var/lib/snapd/snap/hiri/56
loop12         7:12   0    87M  1 loop /var/lib/snapd/snap/core/5145
loop13         7:13   0  86.9M  1 loop /var/lib/snapd/snap/core/4917
loop14         7:14   0 477.9M  1 loop /var/lib/snapd/snap/libreoffice/80
loop15         7:15   0 194.6M  1 loop /var/lib/snapd/snap/firefox/137
loop16         7:16   0  34.7M  1 loop /var/lib/snapd/snap/gtk-common-themes/319
loop17         7:17   0 143.5M  1 loop /var/lib/snapd/snap/chromium/412
loop18         7:18   0 135.8M  1 loop /var/lib/snapd/snap/discord/71
loop19         7:19   0 135.8M  1 loop /var/lib/snapd/snap/discord/79
loop20         7:20   0 193.7M  1 loop /var/lib/snapd/snap/firefox/107
loop21         7:21   0 143.5M  1 loop /var/lib/snapd/snap/chromium/396
loop22         7:22   0 172.1M  1 loop /var/lib/snapd/snap/spotify/21
nvme0n1      259:0    0 953.9G  0 disk 
├─nvme0n1p1  259:1    0   260M  0 part 
├─nvme0n1p2  259:2    0    16M  0 part 
├─nvme0n1p3  259:3    0 247.1G  0 part 
├─nvme0n1p4  259:4    0  1000M  0 part 
├─nvme0n1p5  259:5    0  34.2G  0 part /
├─nvme0n1p6  259:6    0 205.1G  0 part /home
├─nvme0n1p7  259:7    0  15.6G  0 part [SWAP]
├─nvme0n1p8  259:8    0   4.9G  0 part /boot/efi
├─nvme0n1p9  259:9    0 224.6G  0 part 
├─nvme0n1p10 259:10   0     8M  0 part 
├─nvme0n1p11 259:11   0    20G  0 part 
└─nvme0n1p12 259:12   0 201.2G  0 part 
ls -l /boot/efi/EFI
total 16
drwxr-xr-x 6 root root 4096 Oct 25 19:14 BOOT
drwxr-xr-x 2 root root 4096 Jul 24 04:40 BOOT-rEFIndBackup
drwxr-xr-x 2 root root 4096 Jul 24 04:40 Manjaro
drwxr-xr-x 2 root root 4096 Oct 25 19:02 tools

This is weird. Looks to me as if Manjaro is the only OS installed as UEFI. All others do not show up in the EFI directory. Boot Manjaro using your stick and choose “Detect EFI boot loaders”. Your system is messed up pretty good.

fdisk -l
Disk /dev/nvme0n1: 953.9 GiB, 1024209543168 bytes, 2000409264 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
Disklabel type: gpt

The filesystem table is “gpt” and that means you cannot boot anything which is configured as MBR. How did you manage to get there in the first place?
Edit: You need to switch to UEFI mode to do so.

Hmm sorry, I cant find “Detect EFI boot loaders”. Is it possible for you, to describe exactly, where I can find this?
Edit: Didn’t saw your edit. I found it. I got there many options. Should I list all? I would take “(hd0,pt8)/efi/Manjaro/grubx64.efi”?

Yes, this is the right one

Tried all options. It shows always:
error: not a valid root device.

Welcome to UEFI/MBR hell. Unless @gohlip knows a solution for this, I say you have bricked your box. If not already done so make a backup of your important data. You can do this by booting your live stick. Telling MBR and UEFI apart or even have them work together is at least impossible for me. Wait a while for @gohlip to jump in once he is notified about this post.

Okay, I’ll do that. Thank you for the support.

You apparently installed Tumbleweed in MBR/MSDOS mode.
Manjaro is on UEFI mode, as probably Windows.
Edit2: What and how could this exist?

Size of 4.9 GB is not sane for $esp
Please post this, preferably from the installation, but can help even from Live media.

inxi -puo

This time you had booted in MSDOS/Legacy mode. If you boot Live media, you have to select the option with UEFI (in UEFI selection menu). Then you can apply that command and follow it with update-grub

Edit: It wasn’t clear if the efibootmgr command you ran from Live media or Installation.
It has to be from the installation and doublecheck the proper partition names.
Yours should be

sudo efibootmgr -c -d /dev/nvme0n1 -p 1 -L "manjaro" -l "\EFI\Manjaro\grubx64.efi"

You have to confirm you have $esp (/boot/efi) in your installation’s /etc/fstab

Here is your guide

Hmm dont know why, but it didn’t worked. Tried it with UEFI and with Legacy. Both time same result. No error from 1. to 5. step. Step 6 result:
sudo grub-install /dev/nvme0n1

Installing for i386-pc platform.
Installation finished. No error reported.

sudo update-grub

Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-4.14-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.14-x86_64.img
Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img
Found linux image: /boot/vmlinuz-3.16-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-3.16-x86_64.img
Found initrd fallback image: /boot/initramfs-3.16-x86_64-fallback.img
Found openSUSE Tumbleweed on /dev/nvme0n1p11
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done

I think “/dev/nvme0n1” was wrong.
Tried UEFI two times. First time without efibootmgr and second time with this command. It created both time an entry to my bios with “manjaro”. They both don’t give any response. There was no new entry after the legacy try. But tried the manjaro entries again and it didn’t changed anything.

Tried the “Some difficult UEFI setups” with "Lenovo - " too but I didn’t had the directories or the files.

Result to:

sudo efibootmgr -c -d /dev/nvme0n1 -p 1 -L "manjaro" -l "\EFI\Manjaro\grubx64.efi"
efibootmgr: ** Warning ** : Boot0002 has same label manjaro
efibootmgr: ** Warning ** : Boot0003 has same label manjaro
BootCurrent: 001C
Timeout: 0 seconds
BootOrder: 0004,0003,0002,001A,0001,0000,0017,0018,001E,0019,001D,001F,001B,001C,0024
Boot0000* Windows Boot Manager
Boot0001* ubuntu
Boot0002* manjaro
Boot0003* manjaro
Boot0010  Setup
Boot0011  Boot Menu
Boot0012  Diagnostic Splash Screen
Boot0013  Lenovo Diagnostics
Boot0014  Startup Interrupt Menu
Boot0015  Rescue and Recovery
Boot0016  MEBx Hot Key
Boot0017* USB CD
Boot0018* USB FDD
Boot0019* NVMe1
Boot001A* NVMe0
Boot001B* ATA HDD0
Boot001C* USB HDD
Boot001D* PCI LAN
Boot001E  Otype or paste code heretype or paste code herether CD
Boot001F  Other HDD
Boot0020* USBR BOOT CDROM
Boot0021* USBR BOOT Floppy
Boot0022* ATA HDD
Boot0023* ATAPI CD
Boot0024* PCI LAN
Boot0004* manjaro

It’s maybe not relevant but after step 4. I selected manjaro and there shows for a short time this error:

Booting `Manjaro Linux`

error: file `/boot/grub/grubenv` not found.
Loading Linux 4.14.78-1-MANJARO x64 ...
Loading initial ramdisk ...
Press any key to continue ...

Result to inxi -puo:

Partition:
  ID-1: / size: 33.39 GiB used: 28.05 GiB (84.0%) fs: ext4 
  dev: /dev/nvme0n1p5 uuid: 4e334153-e764-40ff-a794-89d4dc81ef88 
  ID-2: /boot/efi size: 4.87 GiB used: 2.3 MiB (0.0%) fs: vfat 
  dev: /dev/nvme0n1p8 uuid: 513A-8BA0 
  ID-3: /home size: 200.86 GiB used: 185.00 GiB (92.1%) fs: ext4 
  dev: /dev/nvme0n1p6 uuid: 41cacbbf-a3e6-429f-b50e-822d06e1ebd8 
  ID-4: /run/media/michi/MJRO1711 size: 1.55 GiB used: 1.55 GiB (100.0%) 
  fs: iso9660 dev: /dev/sda1 uuid: 2018-07-02-18-41-19-00 
  ID-5: /var/lib/snapd/snap/chromium/396 raw size: 143.5 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop13 
  uuid: N/A 
  ID-6: /var/lib/snapd/snap/chromium/412 raw size: 143.5 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop15 
  uuid: N/A 
  ID-7: /var/lib/snapd/snap/chromium/506 raw size: 141.3 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop9 
  uuid: N/A 
  ID-8: /var/lib/snapd/snap/core/4917 raw size: 86.9 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop0 
  uuid: N/A 
  ID-9: /var/lib/snapd/snap/core/5145 raw size: 86.9 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop3 
  uuid: N/A 
  ID-10: /var/lib/snapd/snap/core/5662 raw size: 87.9 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop14 
  uuid: N/A 
  ID-11: /var/lib/snapd/snap/discord/71 raw size: 135.8 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop10 
  uuid: N/A 
  ID-12: /var/lib/snapd/snap/discord/72 raw size: 135.8 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop5 
  uuid: N/A 
  ID-13: /var/lib/snapd/snap/discord/79 raw size: 135.8 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop2 
  uuid: N/A 
  ID-14: /var/lib/snapd/snap/firefox/107 raw size: 193.6 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop1 
  uuid: N/A 
  ID-15: /var/lib/snapd/snap/firefox/118 raw size: 194.9 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop17 
  uuid: N/A 
  ID-16: /var/lib/snapd/snap/firefox/137 raw size: 194.6 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop16 
  uuid: N/A 
  ID-17: /var/lib/snapd/snap/gtk-common-themes/319 raw size: 34.6 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop18 
  uuid: N/A 
  ID-18: /var/lib/snapd/snap/gtk-common-themes/701 raw size: 42.1 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop19 
  uuid: N/A 
  ID-19: /var/lib/snapd/snap/hiri/53 raw size: 201.1 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop8 
  uuid: N/A 
  ID-20: /var/lib/snapd/snap/hiri/55 raw size: 200.9 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop6 
  uuid: N/A 
  ID-21: /var/lib/snapd/snap/hiri/56 raw size: 201.3 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop11 
  uuid: N/A 
  ID-22: /var/lib/snapd/snap/libreoffice/76 raw size: 458.3 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop21 
  uuid: N/A 
  ID-23: /var/lib/snapd/snap/libreoffice/80 raw size: 477.9 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop22 
  uuid: N/A 
  ID-24: /var/lib/snapd/snap/libreoffice/86 raw size: 478.2 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop12 
  uuid: N/A 
  ID-25: /var/lib/snapd/snap/spotify/16 raw size: 162.9 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop20 
  uuid: N/A 
  ID-26: /var/lib/snapd/snap/spotify/19 raw size: 172.5 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop7 
  uuid: N/A 
  ID-27: /var/lib/snapd/snap/spotify/21 raw size: 172.1 MiB 
  size: <root required> used: <root required> fs: squashfs dev: /dev/loop4 
  uuid: N/A 
  ID-28: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap 
  dev: /dev/nvme0n1p7 uuid: 017607c7-9d10-4880-a90d-82f08441806d 
Unmounted:
  ID-1: /dev/nvme0n1p1 size: 260.0 MiB fs: vfat label: SYSTEM 
  uuid: CCD0-E972 
  ID-2: /dev/nvme0n1p10 size: 8.0 MiB fs: <root required> label: N/A 
  uuid: N/A 
  ID-3: /dev/nvme0n1p11 size: 20.00 GiB fs: ext4 label: N/A 
  uuid: fb247606-8639-4857-aeca-615b95370dd9 
  ID-4: /dev/nvme0n1p12 size: 201.17 GiB fs: xfs label: N/A 
  uuid: 7abbdaaf-4eca-4746-9dd6-32c1de5d71da 
  ID-5: /dev/nvme0n1p2 size: 16.0 MiB fs: <root required> label: N/A 
  uuid: N/A 
  ID-6: /dev/nvme0n1p3 size: 247.07 GiB fs: ntfs label: Windows 
  uuid: B00AD3A80AD369BC 
  ID-7: /dev/nvme0n1p4 size: 1000.0 MiB fs: ntfs label: WinRE_DRV 
  uuid: 3218D52E18D4F1B9 
  ID-8: /dev/nvme0n1p9 size: 224.61 GiB fs: ext4 label: All 
  uuid: 6b9518bb-45d0-4dee-9c69-014b8d731815 
  ID-9: /dev/sda2 size: 4.0 MiB fs: vfat label: MISO_EFI uuid: DAA8-362B 

The only missing puzzle/info is fstab. Post

cat /etc/fstab

Most probably you 'll fix it changing UUID for /boot/efi in fstab to uuid: CCD0-E972`, the main $esp.
Do this first.
Then, in Manjaro installation booted in UEFI mode (this is important) swap esp and install grub.

sudo umount /boot/efi
sudo mount /dev/nvme0p1 /boot/efi
sudo grub-install /dev/nvme0p1 --recheck
sudo update-grub
reboot

Manjaro is installed in UEFI, confirm this by the presence of /boot/efi in fstab. If not true, you need to decide what/how/why you will use UEFI or MSDOS/Legacy.

Sorry, I need to learn much about the BIOS. I installed everything with the Legacy. I didn’t knew before, that efibootmgr is for UEFI (I know it was obvious). So the uuid isn’t CCD0-E972.
cat /etc/fstab

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=4e334153-e764-40ff-a794-89d4dc81ef88 /              ext4    defaults,noatime 0 1
UUID=41cacbbf-a3e6-429f-b50e-822d06e1ebd8 /home          ext4    defaults,noatime 0 2
UUID=017607c7-9d10-4880-a90d-82f08441806d swap           swap    defaults,noatime 0 2
UUID=513A-8BA0                            /boot/efi      vfat    defaults,noatime 0 2

I read that UEFI should be better. So if it is possible to change to UEFI without problems, we could change. Legay would be great too, because I started with it and it’s maybe easier to boot on Windows with Legacy but I don’t have much experience with the BIOS stuff.

Since there is an $esp in fstab, assuming you have not done it manually, it was created from the installer, which suggests the installation was UEFI. If so, you don’t need to re-install Manjaro. Also WinOS is probably UEFI but you need to confirm yourself.

If changing UUID as suggested makes Manjaro boot normally, all seems fine. If not, post your findings to get some more suggestions.

How can I change the UUID? I booted Manjaro with a Stick in UEFI mode when I did the fstab output.

If you mean into the installation (not the Live media installer), then run the suggested commands at my previous post., including changing UUID in fstab.

sudo umount /boot/efi

sudo mount /dev/nvme0p1 /boot/efi
mount: /boot/efi: special device /dev/nvme0p1 does not exist.

sudo grub-install /dev/nvme0p1
Installing for x86_64-efi platform.
grub-install: error: cannot find EFI directory.

sudo update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-4.14-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.14-x86_64.img
Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img
Found linux image: /boot/vmlinuz-3.16-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-3.16-x86_64.img
Found initrd fallback image: /boot/initramfs-3.16-x86_64-fallback.img
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Found openSUSE Tumbleweed on /dev/nvme0n1p11
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done

There is now only one manjaro entry. Thats good but I can’t boot in it.

Sorry, I was in a hurry and typed the partition name by memory (which is a disaster…).
Corrected:

sudo umount /boot/efi
sudo mount /dev/nvme0n1p1 /boot/efi
sudo grub-install /dev/nvme0n1 --recheck
sudo update-grub
reboot

Do not forget to edit fstab.

It didn’t worked. Can select manjaro but nothing happens.

sudo umount /boot/efi

sudo mount /dev/nvme0n1p1 /boot/efi/

sudo grub-install /dev/nvme0n1
Installing for x86_64-efi platform.
Installation finished. No error reported.

sudo update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-4.14-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.14-x86_64.img
Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img
Found linux image: /boot/vmlinuz-3.16-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-3.16-x86_64.img
Found initrd fallback image: /boot/initramfs-3.16-x86_64-fallback.img
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Found openSUSE Tumbleweed on /dev/nvme0n1p11
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=4e334153-e764-40ff-a794-89d4dc81ef88 /              ext4    defaults,noatime 0 1
UUID=41cacbbf-a3e6-429f-b50e-822d06e1ebd8 /home          ext4    defaults,noatime 0 2
UUID=017607c7-9d10-4880-a90d-82f08441806d swap           swap    defaults,noatime 0 2
UUID=CCD0-E972                            /boot/efi      vfat    defaults,noatime 0 2

Is that right, that I update fstab manually in an editor?

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