Librem13v4 doesn't detect NVMe drive after software reboot

Librem
1

Hi all,

I have a Librem 13v4 running PureOS which was a replacement for a faulty 13v3. Thanks for the upgrade!

I was initially using a SSD SATA drive and I have since installed a Samsung 860 QVO NVMe. Since making the NVMe drive my primary I’ve noticed some rather odd behaviour. When I restart through the operating system it goes to the GRUB rescue screen as it can’t find the disk. However when I gracefully shutdown or forcefully power off, and then turn it on, the disk is found as expected.

Could this be an issue with disk, file system or BIOS related?

A dmesg from my laptop can be found here
https://pastebin.com/ecjVmfaK

Thanks

2

Check what is your coreboot version using sudo dmidecode and upgrade if needed.

3

@somefanatic when you reboot via the OS, can you bring up the boot menu (ESC on Purism splash screen) and check the listing/ordering of boot devices? Is the NVMe drive listed? If so, is the NVMe drive first in the list? Is grub installed on the MBR of the NVMe drive?

4

@mladen I’m running 4.8.1-Purism-4, which I believe is the newest?

@MrChromebox, odd, only the NVMe device shows up and the SATA SSD is missing after a soft reboot. The NVMe disk is item number 1 and the SATA SSD is number 2.

#cat /etc/fstab
UUID=bc2f75f6-6b52-4b4b-a8bb-5b32f2003050 /boot ext4 defaults,noatime,discard 0 2
/dev/mapper/luks-053b32ca-fec1-4d08-bff8-4d5b807ded35 / ext4 defaults,noatime,discard 0 1
/dev/mapper/luks-1463c4d6-2396-4c1b-a720-0756d0004419 swap swap defaults,noatime,discard 0 2
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0

#blkid
/dev/nvme0n1p1: UUID=“2d876d6a-278b-46da-bc70-275a70ab9671” TYPE=“ext4” PARTUUID=“44c9bf1d-01”
/dev/nvme0n1p2: UUID=“c957a2b5-a540-475a-a1d7-199cfff79fac” TYPE=“crypto_LUKS” PARTUUID=“44c9bf1d-02”
/dev/sda1: UUID=“bc2f75f6-6b52-4b4b-a8bb-5b32f2003050” TYPE=“ext4” PARTUUID=“8ab14d51-01”
/dev/sda2: UUID=“053b32ca-fec1-4d08-bff8-4d5b807ded35” TYPE=“crypto_LUKS” PARTUUID=“8ab14d51-02”
/dev/mapper/luks-053b32ca-fec1-4d08-bff8-4d5b807ded35: UUID=“262fe634-826f-453d-b55a-42b1a7945854” TYPE=“ext4”
/dev/mapper/luks-1463c4d6-2396-4c1b-a720-0756d0004419: UUID=“e91bca69-1773-4a34-a8d1-df322c4eaa64” TYPE=“swap”
/dev/nvme0n1: PTUUID=“44c9bf1d” PTTYPE=“dos”
/dev/nvme0n1p3: PARTUUID=“44c9bf1d-03”
/dev/sda3: PARTUUID=“8ab14d51-03”

Any further ideas?

5

@somefanatic sounds like grub might not be properly installed on the NVMe drive? Is the NVMe drive listed first when both are visible in the SeaBIOS boot menu?