Linux did detect sda and sda1 during the failed boot. That does not cause any confusion, because sda has label c3072e18, while nvme0n1 is labelled 2d889912. (Also there is no sda2 partition on sda.)I did not recall whether the Toshiba may or may not have been plugged in during the non-booting incident. I set eeprom boot order as NVMe last (SD and USB is either first or second). I am sure that SD was not there as needs un-screwing the case.
The initramfs knew it was looking for PARTUUID=2d889912-02, which is the second partition of the NVMe. Linux did not find that drive, for some reason.
I do not have any experience with NVMe on Pi5. I would be inclined to drop back to Gen2 speed if there are any further issues. The boot failure is basically harmless, because Linux has not accessed the drive by that point. But losing connectivity while running, which may have been the cause of your previous failed shutdown, could lead to data loss.
Statistics: Posted by jojopi — Fri Dec 06, 2024 5:45 pm