On Monday, 16 September 2019 12:37:15 BST Mick wrote: > On Sunday, 15 September 2019 23:26:47 BST Peter Humphrey wrote: > > On Sunday, 15 September 2019 10:29:13 BST Mick wrote: > > > What do you see in the / filesystem when the ESP partition is *not* > > > mounted? > > > > The ESP space is not a partition here. > > I think we are confusing terms. Your screenshot definitely shows a > partition, /dev/nvme0n1p2 which is your ESP partition and is flagged as > such by parted. The "small unpartitioned space" at the beginning of the > disk is not a partition and should be left well alone. (see my next email > response on a disambiguation of these two items).
You're right, of course. It is a partition, just left empty. My mistake. --->8 > OK, it seems the systemd-boot decided to create a directory > 45b3c9f27eedd9ca60997b555d46f90d-* within your ESP partition and expect to > find the default OS kernel in this path. I have no idea why it would do > this. Me neither. > It could be a bug related to systemd-boot, or something you ran, but some > systemd user or dev should chime in as to what might have caused it. My > exposure to systemd is limited, I continue to find it awkward/unpleasant to > use on binary distros. I'm sure I didn't do anything to the efi. I was rebooting after a daily update that needed restarts of several boot and sysinit services. I was surprised when, instead of showing the efi boot menu, the system launched into some kind of kernel that didn't have the necessary drivers, and stopped in a panic. That's when the fun began. The only initramfses are early_ucode.cpio and intel-uc.img. -- Regards, Peter.
