You are not logged in.
Hi,
I've been playing around with the kingston NVMe built into my laptop, finding it has (poor) SED capabilities.
Seeing it only respected the Pyrite standard (i.e. not full OPAL), I went ahead and set up an admin password and booted from an Arch USB to see how access would really be blocked.
I therefore bypassed the password prompt, then proceeded with booting the Arch. The NVMe drive didn't seem to be accessible, I got various nvme errors and lsblk did not list any partitions. Since sedutil doesn't support my drive (probably because it's not full OPAL), I couldn't do much more and rebooted.
I was surprised to find that I couldn't boot from the drive anymore, even when providing the correct password. The UEFI did not list Linux Boot Manager as an option. I booted back into the Arch install, providing the correct password at the drive prompt this time, and I was able to chroot into my arch install, run "bootctl install" ("bootctl status" had warned about empty EFI Variables), and all was back to normal.
Is this to be expected in any way, or some bug in the laptop's firmware ?
Offline