Clear will not install to nvme

Q&A
21

Possible failure points:

Path:/dev/nvme0n1p6 Model: MajorMinor:259:6 PtType: FsType:f2fs

I’m not sure f2fs is well supported yet. Highly recommend to choose ext4.

parted /dev/nvme0n1 set 5 boot on

it’s OK, you can also share ESP with Windoze.

Warning: Partition(s) 1 on /dev/sdb have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.

What exactly are you trying to write? Physically disconnect another drives before installation.

2021/09/17 15:06:41 [WRN] Could not determine the guid for: nvme0n1p1
2021/09/17 15:06:41 [WRN] Could not determine the guid for: nvme0n1p2
2021/09/17 15:06:41 [WRN] Could not determine the guid for: nvme0n1p3
2021/09/17 15:06:41 [WRN] Could not determine the guid for: nvme0n1p4
2021/09/17 15:06:41 [INF] Setting GUIDs for device: /dev/nvme0n1
2021/09/17 15:06:41 [DBG] sgdisk /dev/nvme0n1 --typecode=5:C12A7328-F81F-11D2-BA4B-00A0C93EC93B
2021/09/17 15:06:41 [DBG] sync user is sudo_user=#1000
2021/09/17 15:06:41 [DBG] Gnome Proxy Mode: none
2021/09/17 15:06:41 [DBG] [Previous line repeated 4 times]
2021/09/17 15:06:41 [DBG] cmd.Env:
2021/09/17 15:06:42 [DBG] Pre-Installation has no message content
2021/09/17 15:06:42 [DBG] The operation has completed successfully.
2021/09/17 15:06:42 [DBG] sgdisk /dev/nvme0n1 --typecode=6:4F68BCE3-E8CD-4DB1-96E7-FBCAF984B709
2021/09/17 15:06:42 [DBG] sync user is sudo_user=#1000
2021/09/17 15:06:42 [DBG] Gnome Proxy Mode: none
2021/09/17 15:06:42 [DBG] [Previous line repeated 4 times]
2021/09/17 15:06:42 [DBG] cmd.Env:
2021/09/17 15:06:43 [DBG] The operation has completed successfully.

Also interesting stuff, have no idea what’s happening yet.

P.S. Clear will not install to nvme with CLR_BOOT & CLR_ROOT partitions pre-prepared · Issue #2428 · clearlinux/distribution · GitHub

22

I have tried ext4. It failed also. If it means anything,when I tried using the“clr-installer-gui” from the working HHD the log did not have any warnings, but the install still failed.

24

Note that you no longer have to have a swap partition, if there is not one allocated the installer will create a swapfile in /var.

There are also some helpful tutorials online for doing dual booting:
https://docs.01.org/clearlinux/latest/tutorials/multi-boot/dual-boot-win.html

You can ignore the warning " [WRN] Could not determine the guid for: nvme"
It is just saying the installer doesn’t know what guid to that partition is, which is fine because it is not in use for the install.

There have been problems with some NVME drives which seem related to the kernel.
There are a few recommendations here:

25

I followed the instructions https://docs.01.org/clearlinux/latest/tutorials/multi-boot/dual-boot-win.html. I read the recommendations the latency change seems to make sense. If you think I should try that could tell me me how to use it during the install (rather than during boot pressing e and adding nvme_core.default_ps_max_latency_us=300. I am for any other suggestions too.

26

how to use it during the install

Boot from LiveCD and press space several times just after UEFI logo - boot menu will appear. Next steps are described here.

If it will fix your issue you can make this latency permanent. After installation repeat these steps for new OS and run

mkdir -p /etc/cmdline.d
echo "nvme_core.default_ps_max_latency_us=300" > /etc/cmdline.d/nvme_max_latency.conf

clr-boot-manager update
reboot
27

Changing the latency to 300 did not work.

28

Try to increase: 500, 1000, 2000.

29

I tried 1000 and 2000, install failed on both.

30

5500 working fine.

Also check AHCI mode (I’m serious): boot - How to install Ubuntu on a dell latitude 5400 with WD SN520 NVMe SSD? - Ask Ubuntu

31

My bios was in RAID. Switched it to AHCI. I had to start my windows 10 in safe mode before making the change but now it’s fine. I was sure that would fix the install problem,but it still failed. I am still glad I did it. Everything I read said it should be in AHCI anyway. One of the posts said to try latency=5500. I will try that also. Thanks

2 Likes
33

As in my post on the Dell failure:
Did you set up wifi or have your computer hardwired to a network before starting?

Several of your error messages are because the installer can’t access the cdn.

I easily installed to nmve on a wired workstation, but failed time and again when on a laptop. Finally connected to wifi before starting and it worked right away.

Hope my experience helps you.

34

Mine is a hardwired desktop. I will look at the logs again concerning the cdn although it installed on the hard drive of the same PC with the same ethernet connection. Thanks

35

I finally got Clear to install to my nvme. I installed it from the successful Clear install to my HD using the clr-installer-gui bundle and the new 5.14.8kernel. I would mark this as solved, except now when I boot(using systemd-boot) from the menu, Windows will boot but when I select Clear OS it goes to a non gui screen asking for log-in, then when I press enter it wants a password, but the password I entered during install does not work. Any help to get to the desktop would be much appreciated.

36

but the password I entered during install does not work.

Boot from livecd, chroot to your NVMe installation and reset the password. A lot of guides available.

2 Likes
37

That worked. I learned a lot from this problem. Thanks