Unknown device type nvme0n1 (two ssd)

Ok. Let’s try this.

  • Delete unneeded Manjaro entries:
sudo efibootmgr -b 5 -B
sudo efibootmgr -b 4 -B
  • Modify boot order:
sudo efibootmgr -o 3,2,2001,2002,2003

reboot, check if you have Manjaro present in your UEFI boot options. If not, show again the output of sudo efibootmgr -v

1 Like

ok, i did all of these but not showing

//output

BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0002,2001,2002,2003
Boot0000* USB HDD: TOSHIBA TransMemory PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(1,MBR,0x0,0x53b7f4,0x2000)RC
Boot0001* Unknown Device: SAMSUNG MZVLB256HBHQ-00000 PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-81-01-C7-06-76)/HD(1,GPT,5f85c5bd-6f2d-483a-abfd-8c4db9643fa2,0x800,0x100000)RC
Boot0002* Windows Boot Manager HD(1,GPT,456a59f6-dacd-4be2-994e-fae9adb8a92d,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.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.}…e…
Boot0003* Manjaro HD(1,GPT,e9035109-233c-7843-bf43-cb531ab90f69,0x800,0x100000)/File(\EFI\Manjaro\grubx64.efi)
Boot0006* USB HDD: SanDisk PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/HD(2,GPT,bb3a52b7-6c2e-4c25-b9a9-ea656b3ab092,0x1ca3534,0x400)RC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC

Ok. For me this can’t be solved. There you have the Manjaro entry in the list, but you say is not showing up in boot options and boot order is not afected. So I think there is nothing more we can do (at least me)

alright, windows and manjaro will install legacy mode, a damage me? bad performance? freezing problem etc. i’m a developer, i don’t want affect my job

Legacy BIOS doesn’t affect performance

1 Like

currently installed UEFI or Bios ?! little confused by scrolling :wink:

Windows with GPT & UEFI (or BIOS?) & GRUB on /dev/sda1 ?

and Manjaro with GPT & UEFI (or BIOS?) & GRUB on /dev/nvme0n1p1 ?

and here …

you can have different distros / operating systems installed

but Manjaro & manjaro-grub must organize all the events & find all OpsSys on all devices. (Win/Ubuntu/Arch/Manjaro/btw…)

Probably two Grub installed?! (sdd & nvme)
proper place should be: /dev/sda1

or am I wrong?

GPT and UEFI and GRUB /dev/sda1

GPT and UEFI and GRUB /dev/nvme0n1p1

yes, manjaro gnome and opensuse tumbleweed

maybe, i don’t know, i entered manjaro on nvme but over live usb, probably kernel auto generate name nvme0n1

ok … you need chroot your installed system from live-usb

with
manjaro-chroot -a (click 1 if only (0) Manjaro appears)

after this you have a > red# < and mounted installed system (not running):

lsblk
sudo blkid
cat /etc/fstab
sudo ls -al /boot/
sudo ls -al /boot/grub/
sudo ls -al /boot/efi/EFI/

(output format with </> button)

I suspect afterwards:

  • Grub install to /dev/sda1
  • Create & run Grub config

where i do this, on live usb or installed on nvme?

using live USB now
then continue with chroot and auto mount your installed system

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 78.4M 1 loop
loop1 7:1 0 595M 1 loop
loop2 7:2 0 1.3G 1 loop
loop3 7:3 0 627.2M 1 loop
sda 8:0 0 232.9G 0 disk
|-sda1 8:1 0 100M 0 part
|-sda2 8:2 0 16M 0 part
|-sda3 8:3 0 232.3G 0 part
-sda4 8:4 0 506M 0 part sdb 8:16 1 7.2G 0 disk |-sdb1 8:17 1 2.6G 0 part -sdb2 8:18 1 4M 0 part
nvme0n1 259:0 0 238.5G 0 disk
|-nvme0n1p1 259:1 0 512M 0 part /boot/efi
|-nvme0n1p2 259:2 0 6G 0 part
`-nvme0n1p3 259:3 0 232G 0 part /

/dev/nvme0n1p1: UUID=“6D89-8BE2” BLOCK_SIZE=“512” TYPE=“vfat” PARTUUID=“e9035109-233c-7843-bf43-cb531ab90f69”
/dev/nvme0n1p2: UUID=“56441967-948a-4467-a2c0-b3710ae2e741” TYPE=“swap” PARTUUID=“29df143f-542a-964c-9835-ec3b00b2c646”
/dev/nvme0n1p3: UUID=“be12a26e-1b38-4290-ac30-36c9d02a1866” BLOCK_SIZE=“4096” TYPE=“ext4” PARTUUID=“f6505585-04b3-614f-b3bf-ac27a7b58268”
/dev/sda1: UUID=“56F5-C6AF” BLOCK_SIZE=“512” TYPE=“vfat” PARTLABEL=“EFI system partition” PARTUUID=“456a59f6-dacd-4be2-994e-fae9adb8a92d”
/dev/sda2: PARTLABEL=“Microsoft reserved partition” PARTUUID=“bd47f2de-a7d9-4e76-be01-069f68e69a9c”
/dev/sda3: BLOCK_SIZE=“512” UUID=“B2A2F69CA2F6646F” TYPE=“ntfs” PARTLABEL=“Basic data partition” PARTUUID=“5d6c06aa-46a5-42e0-a3da-3bd91b54459c”
/dev/sda4: BLOCK_SIZE=“512” UUID=“F83A634A3A63054A” TYPE=“ntfs” PARTUUID=“3fdecfcc-c690-4858-823f-738b9dda2e05”
/dev/loop0: TYPE=“squashfs”
/dev/loop1: TYPE=“squashfs”
/dev/loop2: TYPE=“squashfs”
/dev/loop3: TYPE=“squashfs”
/dev/sdb1: BLOCK_SIZE=“2048” UUID=“2020-09-11-17-22-12-00” LABEL=“MANJARO_XFCE_201” TYPE=“iso9660”
/dev/sdb2: SEC_TYPE=“msdos” LABEL_FATBOOT=“MISO_EFI” LABEL=“MISO_EFI” UUID=“0DC8-2349” BLOCK_SIZE=“512” TYPE=“vfat”

/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).

UUID=6D89-8BE2 /boot/efi vfat umask=0077 0 2
UUID=56441967-948a-4467-a2c0-b3710ae2e741 swap swap defaults,noatime 0 2
UUID=be12a26e-1b38-4290-ac30-36c9d02a1866 / ext4 defaults,noatime 0 1

total 49964
drwxr-xr-x 5 root root 4096 Sep 15 14:39 .
drwxr-xr-x 17 root root 4096 Sep 11 20:13 …
drwxr-xr-x 5 root root 4096 Jan 1 1970 efi
drwxr-xr-x 5 root root 4096 Sep 15 16:26 grub
-rw------- 1 root root 31623260 Sep 15 14:36 initramfs-5.8-x86_64-fallback.img
-rw------- 1 root root 9590189 Sep 15 14:36 initramfs-5.8-x86_64.img
-rw-r–r-- 1 root root 3161088 Jun 16 20:50 intel-ucode.img
-rw-r–r-- 1 root root 20 Sep 3 17:18 linux58-x86_64.kver
drwxr-xr-x 2 root root 4096 Sep 11 20:10 memtest86+
-rw-r–r-- 1 root root 6753984 Sep 11 20:10 vmlinuz-5.8-x86_64

total 40
drwxr-xr-x 5 root root 4096 Sep 15 16:26 .
drwxr-xr-x 5 root root 4096 Sep 15 14:39 …
drwxr-xr-x 2 root root 4096 Sep 15 14:38 fonts
-rw-r–r-- 1 root root 7427 Sep 15 16:26 grub.cfg
-rw-r–r-- 1 root root 1024 Sep 15 14:39 grubenv
drwxr-xr-x 3 root root 4096 Sep 15 14:38 themes
drwxr-xr-x 2 root root 12288 Sep 15 14:38 x86_64-efi

total 16
drwxr-xr-x 4 root root 4096 Sep 15 17:38 .
drwxr-xr-x 5 root root 4096 Jan 1 1970 …
drwxr-xr-x 2 root root 4096 Sep 15 17:38 Manjaro
drwxr-xr-x 2 root root 4096 Sep 15 17:38 boot

ok, thanks for the overview

your NVME is entered as the first line in your /etc/fstab

this loads what you see in /boot/

is the only system that is installed & can also be found by grub on NVME

we have to tell Manjaro that GRUB (system start) is on a different hard drive

for this we have to do the following Modify:

sudo nano /etc/fstab
change here UUID from nmve to sda … here /dev/sda1 correct locate

#UUID=6D89-8BE2 /boot/efi vfat umask=0077 0 2
UUID=56F5-C6AF /boot/efi vfat umask=0077 0 2

Then save and return (STRG+X, Y and press enter for save)

now we need to install/re-check GRUB to /dev/sda1

pls logout chroot with “exit” … this unmount your installed Manjaro …
after this remount with manjaro-chroot -a

the current chroot should mount the drive /dev/sda1 to /mnt/boot/efi ?!
before /dev/nvme0n1p1 was mounted to /mnt/boot/efi :slight_smile:

correct and understood so far?

ok … after chroot / remount without errors …

sudo ls -al /boot/efi/EFI/
Microsoft (without Manjaro) should now also be visible here ?!

95% of the work done :wink:

here pls enter & output:

sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck

and then last

sudo update-grub

now exit & reboot

maybe you have more luck at the start now ?!

1 Like

these process doing on live usb? mounted manjaro? or manjaro on nvme?

I always do this in the live-session (live-usb) & chroot
mount & u-mount is faster than restarting the system

Installing for x86_64-efi platform.
Installation finished. No error reported.

Generating grub configuration file …
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.8-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.8-x86_64.img
Found initrd fallback image: /boot/initramfs-5.8-x86_64-fallback.img
Adding boot menu entry for UEFI Firmware Settings …
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done

This is because of the memtest86 file in the grub actions and can be ignored or fixed by removing memtest86 file.

I didn’t read the all the messages as it started to be non sense to me, but I have Windows installed on UEFI/GPT on its own SSD, and I have Manjaro installed on its own NVME SSD as GPT/UEFI. My system boots on the NVME SSD, I have the grub boot menu entry where I can select to boot on Manjaro or Windows. I don’t know why your system doesn’t work but yeah you’re doing something wrong.

mehh, same, sata show boot menu, still not show nvme :confused:

whatever is told to me, i did all of these :man_shrugging:

I suppose that was selected in the first installation of the wrong boot sector ?!
(probably the nvme was given and not the ssd (where Microsoft & co is on it)

not fail … next try :wink:

what amazes me, grub won’t find any other systems like Microsoft etc …

pls output from
lsblk -al
sudo ls -al /boot/efi/EFI/
(in the live usb & chroot or nvme install > no matter > where you are right now)

actually should now be:
/boot/efi → /dev/sda1 (MS, Co & NewManjaro)
/(root) → /dev/nvme0n1p3

assuming everything was done correctly?

What is the first Boot-Order in your BIOS/UEFI-Settings when booting?

**(i made a mistake. unfortunately read too much and lost sight of the goal.
wanted to help you too much (all systems under one GRUB)
and didn’t help with unkown device type: nvme0n1

sorry very much)

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 78.4M 1 loop
loop1 7:1 0 595M 1 loop
loop2 7:2 0 1.3G 1 loop
loop3 7:3 0 627.2M 1 loop
loop4 7:4 0 0 loop
loop5 7:5 0 0 loop
loop6 7:6 0 0 loop
loop7 7:7 0 0 loop
sda 8:0 0 232.9G 0 disk
sda1 8:1 0 100M 0 part /boot/efi
sda2 8:2 0 16M 0 part
sda3 8:3 0 232.3G 0 part
sda4 8:4 0 506M 0 part
sdb 8:16 1 7.2G 0 disk
sdb1 8:17 1 2.6G 0 part
sdb2 8:18 1 4M 0 part
nvme0n1 259:0 0 238.5G 0 disk
nvme0n1p1 259:1 0 512M 0 part
nvme0n1p2 259:2 0 6G 0 part
nvme0n1p3 259:3 0 232G 0 part /

total 5
drwxr-xr-x 5 root root 1024 Sep 15 20:30 .
drwxr-xr-x 4 root root 1024 Jan 1 1970 …
drwxr-xr-x 2 root root 1024 Sep 14 17:28 Boot
drwxr-xr-x 4 root root 1024 Sep 14 17:27 Microsoft
drwxr-xr-x 2 root root 1024 Sep 15 20:30 manjaro

it’s just warning, i removed memtest then not show this warning