package shim-signed 1.51.3+15.7-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

It seems your /boot/efi partition is not mounted. Please mount it to continue the upgrade.

It seems you actually deleted that partition otherwise it would have been automatically mounted (which you can see fails here because the partition no longer exists).

In this case, please create a new EFI system partition and mount it to /boot/efi.

The bug here is that we allowed you to continue with a device that no longer exists, but since we already have other bugs tracking this and I don't have them handy I'll go close this instead of marking it a duplicate.

Firstly, thanks @juliank

1. I am a newbie to ubuntu

2. I got a new computer that I just installed the Ubuntu 22.04 iso on, I did not upgrade from any version. I formatted the windows 11 default O.S and installed ubuntu.

3. Does this step - "In this case, please create a new EFI system partition and mount it to /boot/efi." involves me formatting the computer. This is my personal PC, and made this new installation of ubuntu about 2 weeks ago.

Peter, please show the output of the command 'ls -l /dev/disk/by-id' on this system.

For the record, we have seen a surprisingly large number of bug reports of this sort *specifically* from users with NVME disks and no other kinds of disks so I am suspicious. You're the first bug reporter who has responded after initial bug filing, however, so it hasn't been possible to get more information!

I was able to solve this issue, thanks to what juliank suggested.

"In this case, please create a new EFI system partition and mount it to /boot/efi."

Like I said, I'm new to Ubuntu so I shared this with ChatGPT and the solution it recommended. worked.

Would it be possible to share it here, as it's AI and I don't know the rules of this platform.

I don't the output of the command will be same as what it was when the bug was reported.

```
$ ls -l /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root 13 Oct 11 21:00 nvme-eui.00000000000000007c354851ed684214 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Oct 11 21:00 nvme-eui.00000000000000007c354851ed684214-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Oct 11 21:00 nvme-eui.00000000000000007c354851ed684214-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 13 Oct 11 21:00 nvme-TS512GMTE220S_H278000148 -> ../../nvme0n1
lrwxrwxrwx 1 root root 13 Oct 11 21:00 nvme-TS512GMTE220S_H278000148_1 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Oct 11 21:00 nvme-TS512GMTE220S_H278000148_1-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Oct 11 21:00 nvme-TS512GMTE220S_H278000148_1-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Oct 11 21:00 nvme-TS512GMTE220S_H278000148-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Oct 11 21:00 nvme-TS512GMTE220S_H278000148-part2 -> ../../nvme0n1p2

```

I would post the report of what I did though with the CAVEAT -> This is specific to my issue, and no SO answer could help me but what Juliank wrote.

-> Initially, my /boot/efi was mounted on the only partition available on my disk. So, i created a new Fat32 partition on `/dev/nvme0n1` using `gparted`.

-> Then, I formated the new partition with FAT32 filesystem
`
-> Then mounted the EFI partition which already existed btw on `dev/nvme0n1p1` to the new partition `dev/nvme0n1p2`

-> I updated the `/etc/fstab` with the new location of `/boot/efi` and commented out the old value

-> I reinstalled grub and did a reboot.

----

During reboot, I got this error - `x86/cpu: SGX disable by BIOS.`

I fixed this by going into the BiOs settings and switched the option for Intel SGX to Enable, and the rest was history.

Thanks once again @juliank. I do not regret trying out ubuntu

> Would it be possible to share it here, as it's AI and I don't know the rules of this platform.

Please tell us the instructions that you followed.