No.Wait. Trying to get an idea of what is there... You said
So that drive is the only drive in the system
But I see more drives in this system (in that report) than just that one...
Code:
===================================== UEFI =====================================
BIOS is EFI-compatible, and is setup in EFI-mode for this live-session.
efibootmgr -v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0000,0005,0003,0004
Boot0000* ubuntu HD(1,GPT,867f021e-bde0-4ba6-9bf3-780f6f7899ed,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* proxmox HD(2,GPT,aebc9c90-0c59-4729-9178-84b8bade1696,0x800,0x100000)/File(\EFI\proxmox\grubx64.efi)
Boot0003* WDC WD5000AAKX-083CA1 BBS(HD,,0x0)AMBO
Boot0004* SanDisk BBS(HD,,0x0)AMBO
Boot0005* UEFI: SanDisk PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(1,0)/HD(1,MBR,0x2c534026,0x3c4,0x1340)AMBO
This session has been detected as 'live' because /proc/cmdline contains (boot=casper)
This session has been detected as 'live' because df -Th / contains overlay
In most of it, I see sda and sdb, where sda is the wdc hdd that you installed Ubuntu to... with 3 partitions... sda1 is the EFI. sda2 is the /boot. sda3 is the root partition with LVM. SDB is the USB LiveCD you booted from.
I see two big problems. sdc is a mystery... Because there is no "sdc" and for some reason sometimes it thinks there is... Look at lines 403-405, and intermitterntly from Lines 102-153. That will cause problems, but it not the problem stopping you from booting... I'll go over that one after I go over resolving your main problem first, because I think that one is a really easy fix and is an additional/sideline issue....
*** The main problem is sort of two-fold. It looks as if the Server previously... Maybe before you had it, had Promox installed 'somewhere'. It no longer exists 'anywhere', except for the UEFI boot menu file in the EFI partition.
Code:
# Snip from lines 208-213
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,0000,0005,0003,0004
Boot0001* proxmox HD(2,GPT,aebc9c90-0c59-4729-9178-84b8bade1696,0x800,0x100000)/File(\EFI\proxmox\grubx64.efi)
That EFI memu item is still there, and your UEFI BIOS Firmware is still set to boot the orphaned menu item to boot from...Instead of booting from your Ubuntu UEFI menu entry
Code:
Boot0000* ubuntu HD(1,GPT,867f021e-bde0-4ba6-9bf3-780f6f7899ed,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Recommendation:
- A soon as you get into your UEFI BIOS, on BIOS post, it should see that it only has one drive connected, and resolve thinking that it has anohter drive connected...
- Go to the UEFI boot order and select the Ubuntu EFI menut item as the first in the order.
- Turn off FastBoot. That will skip over most of the POST boot order chacks, which makes the booting faster... But has a big drawback, that it will disable the keyboard and mouse until POST is over... Sometimes "you need" that input interaction to do things on boot.
- For now, leave SecureBoot enabled. That is how you installed 20.04 and should be working with that. If you still had 18.04 installed, I would tell you to turn it off. (That didn't support that yet.)
- Then save, and reboot. It should boot.
Afterwards... Delete that promox efi menu item file and remove it from the EFI menu, using 'efibootmgr'. it has no place there anymore. You could delete this whole directory and files recursively: /dev/sda1/EFI/proxmox/.
With that, you should be running again in a matter of minutes.
Bookmarks