EndeavoursOS on nvme

hi there,
I’m trying to install linux on a nvme but i can’t get it working. Of course I read forum and wiki and search for the solution around. I have no problem installing linux in othere ssd on my PC.

  • MOBO bios updated to the latest
  • Secure boot off
  • fast boot off
  • CSM off
  • There is no option in nvme configuration in bios
    The nvme is detected before the installation start but then i think it has some problem in mounting the partition, as i read the log
    https://termbin.com/w466
    It is GPT partition, clean with gparted before.
    Thanks to anyone helping

Here is the actual error from your log:

2022-04-29 - 19:27:10 [2]: WARNING: [PYTHON JOB]: "Command 'grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=endeavouros-8397 --force' returned non-zero exit status 1." 
2022-04-29 - 19:27:10 [6]: [PYTHON JOB]: "stdout:Installing for x86_64-efi platform.\ngrub-install: error: cannot find a device for /boot/efi (is /dev mounted?)." 

EDIT: I see, it is failing to mount basically everything. That is why your install it failing and it can’t install grub.

check also

  • all disks on AHCI
  • no raid and optane/rst disable
1 Like

I checked multiple time for AHCI but there isn’t any option like that under sata settings in bios. Also no option available for raid.
I checked every option in the bios, took me a long time but poor result.
I use a ASUS B360-K

check all option in your UEFI
create a profile for linux

check also Disks for AHCI , and no hibernation from windows

SecureBoot off
Fast Boot off
No CSM
No Legacy
all disks on AHCI
No optane/RST

you can check in terminal before installing

inxi -Fza
test -d /sys/firmware/efi && echo efi || echo bios
sudo parted -l

yes i also see that failed to mount but i can’t understand why, i tried now also MBR. But nothing. The nvme is mounted, i can modify partition with gparted with no problem

This is for the first command

System:
  Kernel: 5.17.1-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
    parameters: initrd=\arch\boot\intel-ucode.img
    initrd=\arch\boot\amd-ucode.img
    initrd=\arch\boot\x86_64\initramfs-linux.img archisobasedir=arch
    archisolabel=EOS_202204 cow_spacesize=10G nvidia nvidia-drm.modeset=1
    nouveau.modeset=0 i915.modeset=1 radeon.modeset=1 nvme_load=yes
  Desktop: Xfce v: 4.16.0 tk: Gtk v: 3.24.29 info: xfce4-panel wm: xfwm
    v: 4.16.1 vt: 1 dm: LightDM v: 1.30.0 Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B360M-K v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 2811
    date: 05/27/2020
CPU:
  Info: model: Intel Core i5-9600K bits: 64 type: MCP arch: Coffee Lake
    family: 6 model-id: 0x9E (158) stepping: 0xD (13) microcode: 0xEC
  Topology: cpus: 1x cores: 6 smt: <unsupported> cache: L1: 384 KiB
    desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB L3: 9 MiB
    desc: 1x9 MiB
  Speed (MHz): avg: 800 min/max: 800/4600 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800
    bogomips: 44412
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
  Vulnerabilities:
  Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
    mitigation: Enhanced IBRS, IBPB: conditional, RSB filling
  Type: srbds mitigation: TSX disabled
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: ZOTAC driver: nvidia
    v: 510.60.02 alternate: nouveau,nvidia_drm pcie: gen: 3 speed: 8 GT/s
    lanes: 2 link-max: lanes: 16 ports: active: none
    off: DP-3,DVI-D-1,HDMI-A-1 empty: DP-1,DP-2 bus-ID: 01:00.0
    chip-ID: 10de:1b81 class-ID: 0300
  Device-2: Microdia Webcam Vitade AF type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 1-8:7 chip-ID: 0c45:6366
    class-ID: 0102 serial: <filter>
  Display: server: X.Org v: 1.21.1.3 compositor: xfwm v: 4.16.1 driver: X:
    loaded: nvidia unloaded: modesetting alternate: fbdev,nouveau,nv,vesa
    gpu: nvidia,nvidia-nvswitch display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 7280x1440 s-dpi: 109 s-size: 1696x333mm (66.77x13.11")
    s-diag: 1728mm (68.05")
  Monitor-1: not-matched mapped: DP-4 pos: primary,left res: 3440x1440
    hz: 50 dpi: 110 size: 797x334mm (31.38x13.15") diag: 864mm (34.02")
    modes: N/A
  Monitor-2: DVI-D-1 mapped: DVI-D-0 note: disabled pos: primary,center
    model: Acer V243HQ serial: <filter> built: 2009 res: 1920x1080 hz: 60
    dpi: 94 gamma: 1.2 size: 521x293mm (20.51x11.54") diag: 598mm (23.5")
    ratio: 16:9 modes: max: 1920x1080 min: 640x480
  Monitor-3: HDMI-A-1 mapped: HDMI-0 note: disabled pos: right
    model: MSI MP241 serial: <filter> built: 2020 res: 1920x1080 hz: 60 dpi: 93
    gamma: 1.2 size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9
    modes: max: 1920x1080 min: 640x480
  OpenGL: renderer: NVIDIA GeForce GTX 1070/PCIe/SSE2
    v: 4.6.0 NVIDIA 510.60.02 direct render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel
    v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
    chip-ID: 8086:a348 class-ID: 0403
  Device-2: NVIDIA GP104 High Definition Audio vendor: ZOTAC
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 2
    link-max: lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10f0 class-ID: 0403
  Device-3: Roland DUO-CAPTURE EX type: USB driver: snd-usb-audio
    bus-ID: 1-3:3 chip-ID: 0582:0159 class-ID: ff00
  Device-4: Medeli USB Audio Device type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-6:5 chip-ID: 0a67:11c0
    class-ID: 0300 serial: <filter>
  Device-5: Microdia Webcam Vitade AF type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 1-8:7 chip-ID: 0c45:6366
    class-ID: 0102 serial: <filter>
  Sound Server-1: ALSA v: k5.17.1-arch1-1 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.49 running: yes
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel modules: wl pcie:
    gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:2723
    class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 05:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp5s0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 1-14:8 chip-ID: 8087:0029 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 1.04 TiB used: 1.68 GiB (0.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 model: NVME SSD 512GB size: 476.94 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4
    type: SSD serial: <filter> rev: T0609B0L temp: 30.9 C scheme: MBR
  ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SA400S37120G
    size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 0010 scheme: GPT
  ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: HD502HJ
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: 0002 scheme: MBR
  ID-4: /dev/sdc maj-min: 8:32 type: USB vendor: SanDisk model: Cruzer Edge
    size: 14.59 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: N/A size: 10 GiB used: 59.7 MiB (0.6%) fs: overlay
    source: ERR-102
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 27.8 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 243 Uptime: 3m wakeups: 0 Memory: 15.55 GiB
  used: 1.71 GiB (11.0%) Init: systemd v: 250 target: multi-user.target
  tool: systemctl Compilers: gcc: 11.2.0 Packages: pacman: 903 lib: 212
  Shell: Bash v: 5.1.16 running-in: xfce4-terminal inxi: 3.3.14

Then second command give me nothing, it keeps loading

The third one

[liveuser@eos-2022.04.08 ~]$ sudo parted -l
Model: ATA KINGSTON SA400S3 (scsi)
Disk /dev/sda: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size   File system  Name  Flags
 1      17.4kB  538MB  538MB  fat32              boot, esp
 2      538MB   120GB  119GB  ext4


Model: ATA SAMSUNG HD502HJ (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start  End  Size  Type  File system  Flags


Model: SanDisk Cruzer Edge (scsi)
Disk /dev/sdc: 15.7GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  15.7GB  15.7GB  primary  fat32        boot, lba


Model: NVME SSD 512GB (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start  End  Size  File system  Name  Flags

with gparted

  • format in gpt table
  • create 3 partitions
    – /boot/efi in Fat32 (vfat) size 32Mo , add flag esp & boot
    – / ( size between 25Go to 35Go ) in ext4
    – /home all the rest in ext4
    quit gparted

launch installer , add mountpoint for /boot/efi , / and /home
and retry

1 Like

No real difference i think. Partition operation with Gparted ok, but installation failed.
I attach the log file again, same error
https://termbin.com/5wqe

1 Like

Is there or was there anything else installed on this NVME?

  Setting up actions for "/dev/nvme0n1" with 0 entries. 
2022-04-29 - 20:03:57 [6]:     ..  Can not resize "/dev/nvme0n1p1" , filesystem "fat32" does not support resize. 
2022-04-29 - 20:03:57 [6]:     ..  Checking if "/dev/nvme0n1p1" can be replaced. 
2022-04-29 - 20:03:57 [6]:     ..  NO, insufficient storage 

This should be – /boot/efi in Fat32 (vfat) size 512Mib , add flag esp & boot

I’ve used also 512 Mbi for boot, just to try. No difference
Yes there was window 11. I tried to setup a dual boot, after failing I deleted everything, hoping that without w11 the installation would succeed.

It seems that /boot/ is there
Creating zstd-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

==> Creating zstd-compressed initcpio image: /boot/initramfs-linux-lts.img
==> Image generation successful

But it can’t find /boot/efi/
2022-04-29 - 22:14:20 [6]: [PYTHON JOB]: “Bootloader: grub (efi)”
2022-04-29 - 22:14:20 [6]: … Running (“grub-install”, “–target=x86_64-efi”, “–efi-directory=/boot/efi”, “–bootloader-id=endeavouros-6839”, “–force”)
2022-04-29 - 22:14:20 [6]: … Target cmd: (“grub-install”, “–target=x86_64-efi”, “–efi-directory=/boot/efi”, “–bootloader-id=endeavouros-6839”, “–force”) Exit code: 1 output:
Installing for x86_64-efi platform.
grub-install: error: cannot find a device for /boot/efi (is /dev mounted?).

Could it be this?:
Did you select the right drive, nvme, to install the bootloader on? Make sure it is the last thing you check before continue the install.
I remember that it resets the drive to install the bootloader to, everytime you do something in setting up partitions.

Calamares is not too smart IMHO. For example, it seems IIUC that even if target root has failed (or pending) to be mounted, it tries mounting the rest of tatget mount points :scream_cat: .

What I would do:

  • Check/try to mount target drive/partitions manually to custom folders and watch for errors
  • Create a new vfat partitiion on the target system and mount it at /boot .
  • Run Calamares from terminal in debug mode, watching info messages.
  • Notice the temporary folder used for Calamares mount points and see see what is written inside. Also check in a new terminal session/tab for existing mount points at any time, to see if mounting really fail, or is a wrong message. (mount | grep nvme)
  • If your installation seems done (and Calamares is failing to install bootloader, perform a manual grub installation, using the new vfat partition (mounted at /boot) for --efi-directory (read Archwiki or man grub-install for specific command).

In any case, post output from your ISO installer terminal

sudo inxi -dpuoLRa

Good luck! :smile:

Edited:
Disk is MBR not GPT

 ID-1: /dev/nvme0n1 maj-min: 259:0 model: NVME SSD 512GB size: 476.94 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4
    type: SSD serial: <filter> rev: T0609B0L temp: 30.9 C scheme: MBR

I tried creating another partition table, verifying with “parted -l”

Model: NVME SSD 512GB (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End    Size   File system  Name  Flags
 1      1049kB  512GB  512GB  ext4

Installation failed.

I notice something, when i’m in the other ssd, after format the nvme, i cannot mount it, even if it is detected correctly, showing me this

Seems somethings corrupted from the previous ntfs window partition, maybe there is way to clean it the proper way (?)

1 Like

Okay so you used parted to create a GPT partition and installed again and it failed? Or you used parted to verify?

It fail to mount everythings, this night i will investigate more and post everything i can.

Btw i notice that usings my arcolinux system installed on the other ssd, although i can see the nvme, when i try to mount it, just to use it as storage it fail, can get why. I posted some material below, maybe it can have something with the window partition that was on this disk before?

I’ve done like 20 install try, i checked very carefully, i think is something with nvme mounting it self, but can get the way around it. it just can’t mount the nvme it self, although is detected

How did you create the GPT partition before installing?

yes, several time. I used also gparted to create a new partition table, GPT of course, and then tried to reinstall but no different results