[SOLVED] PVE 9.1.5 doesn't boot after dist-upgrade (AMI BIOS)

D

derMiepz

New Member
Mar 3, 2025
5
1
1
Heya!

Today I noticed that after I migrated from PVE 8.x to 9.x a while ago (following the docs to the best of my ability), my kernel was still outdated. I wanted to fix that now by using "apt dist-upgrade", but after that my PVE didn't boot properly and only sent me to the BIOS.

I tried the things from the following threads and websites already:
K

[SOLVED] Thread 'help!!! grub rescue - proxmox 8.1'

Hello,

i have a 5 years proxmox server installed with the early 5.x versions with zfs. Until now with all the upgrades everything worked perfectly and had version 8.
Yesterday i upgraded and after the reboot i get "GRUB RESCUE - UNKNOWN FILESYSTEM" error.

I have read the guides here and tried to resolve, but since it was from an early version, i don't have the 512mb partitions.

I have booted with liveusb proxmox iso, and can mount the rpool to /mnt and see the files.

Please help me what to do. If i have to reinstall, is there a way to save all data (since zfs makes parts) or run backup...
https://pve.proxmox.com/wiki/Recover_From_Grub_Failure
N

[SOLVED] Thread 'GRUB Rescue - Need help for beginner!'

Hi,
I'm not very experienced with Linux core systems, but I think I've got a big, big problem:
After restarting my server, it doesn't boot anymore

GRUN loading.. Welcome to GRUB! error: no such device: 542d67217ce82747. error: unknown filesystem. grub rescue>

Can anybody give me support, what to do now? I've found some information in the internet, but I'm not sure if they are applicable to ZFS.
And before making something wrong it's better to ask here, I think.

Thanks
nigi

After that, I now get the error "grub rescue : “error: symbol ‘grub_disk_native_sectors’ not found”"

I found this post but it didn't help me unfortunately.
M

Thread 'grub rescue : “error: symbol ‘grub_disk_native_sectors’ not found”'

Hello to you all,
It seems I have messed up my proxmox machine with an apt update this morning. I think it was grub-pc or something like that, which asks during the update where grub was installed. Well, I think I didn't answered correctly. Anyway, here's where I am for now :
- I end up in grub rescue mode. From there I can do "ls", which gives something like that :
(lvm/pve-root) (lvm/pve-swap) (hd0) (hd0,gpt1) (hd1) (hd1,gpt1) (hd2) (hd0,gpt3) (hd2,gpt2) (hd2,gpt1) error out of memory
- (lvm/pve-root) seems the one that contains boot/ with vmlinuz-6.2.15-pve
- I can do set...

I can get it to boot when using a live ISO via Ventoy. (Advanced options -> Rescue Boot)

TL;DR: I probably nuked my bootloader and I have no idea how to get it working again :/

Additional info:
root@pve:~# efibootmgr
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0001,0000,0002
Boot0000* proxmox HD(2,GPT,f9a7e04b-4d62-4a20-af20-2b28941ba115,0x13e0,0xffffd)/File(\EFI\proxmox\grubx64.efi)
Boot0001* UEFI OS HD(2,GPT,f9a7e04b-4d62-4a20-af20-2b28941ba115,0x13e0,0xffffd)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
Boot0002 UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f
Boot0003* UEFI: SanDisk, Partition 2 PciRoot(0x0)/Pci(0x14,0x0)/USB(12,0)/HD(2,MBR,0xcb448206,0x755d500,0x10000)0000424f
root@pve:~# blkid
/dev/mapper/pve-vm--115--disk--0: UUID="e24dd992-8ae4-4182-8b06-1e3ea0895a87" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-root: UUID="153e5361-49e3-40ac-8495-a45029d29d53" BLOCK_SIZE="4096" TYPE="ext4"
/dev/nvme0n1p3: UUID="S6V5bz-kZ2j-hiKw-Erzx-DAJZ-wfpT-s3DVX3" TYPE="LVM2_member" PARTLABEL="Logical Volume Manager (LVM) partiti" PARTUUID="784f503b-2cea-4314-83d0-3d2d35967efb"
/dev/nvme0n1p2: UUID="7D0B-6EBB" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI System partition" PARTUUID="f9a7e04b-4d62-4a20-af20-2b28941ba115"
/dev/mapper/pve-vm--114--disk--0: UUID="4f62e7ac-1846-4a63-a51f-e2a60e540a78" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-vm--119--disk--0: UUID="e62aea4f-d393-414f-bf65-888bd45af5c8" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-vm--104--disk--0: UUID="5aa8e107-a90e-4594-a784-6121a94d4ba6" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-vm--100--disk--0: UUID="a4cbd83d-2f13-48b9-81fb-1901c7432a59" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-vm--111--disk--0: UUID="c312efda-e801-4e47-9002-3a8d2bbdff5e" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-vm--109--disk--0: UUID="59ad914f-9e10-4f02-8a55-49bf57f8348b" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-vm--116--disk--0: UUID="922bf3f2-ba58-45d4-bd6b-56a071babf00" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-swap: UUID="766520d7-4df1-49c8-a990-9d358e6af95d" TYPE="swap"
/dev/mapper/pve-vm--106--disk--0: UUID="1cf49142-3267-4bdf-bf16-22e1b9023a6e" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-vm--113--disk--0: UUID="c0c2fe45-f198-44af-b6fe-0806acad91b2" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-vm--118--disk--0: UUID="b9dcb4ae-3cf7-40b9-9513-5b7e2fca5e12" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-vm--102--disk--0: UUID="3d0bffb9-1fd7-47ea-846d-92d50b9d04f8" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-vm--111--disk--1: UUID="c8c4b5ee-5970-406e-a0d7-ba83a1d2ba5a" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sda2: SEC_TYPE="msdos" LABEL_FATBOOT="VTOYEFI" LABEL="VTOYEFI" UUID="7353-81B1" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="cb448206-02"
/dev/sda1: LABEL="Ventoy" UUID="4E21-0000" BLOCK_SIZE="512" TYPE="exfat" PARTUUID="cb448206-01"
/dev/mapper/pve-vm--110--disk--0: UUID="3f408914-b93e-4ebc-ab51-4f9454ed44c8" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-vm--117--disk--0: UUID="c06d4166-6ed9-49fb-a5c9-905272ea1bd8" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/pve-vm--108--disk--0: UUID="5a990cc7-ceee-4f5f-995b-7877e76b0e55" BLOCK_SIZE="4096" TYPE="ext4"
/dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/mapper/pve-vm--107--disk--0: PTUUID="26cb551f" PTTYPE="dos"
/dev/nvme0n1p1: PARTLABEL="BIOS Boot partition" PARTUUID="c650d5ee-bc96-485e-9be0-2972274fe6c1"
/dev/mapper/pve-vm--120--disk--0: UUID="2fbc3062-9985-4b31-bf57-fe28b02feb95" BLOCK_SIZE="4096" TYPE="ext4"
/dev/loop6: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop4: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop2: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/mapper/pve-vm--105--disk--0: PTUUID="8f612d6d-fc71-4218-ae43-291d3e782cc1" PTTYPE="gpt"
/dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/mapper/pve-vm--101--disk--0: UUID="ff7db553-4a9d-4f72-92ac-69aaa711fada" BLOCK_SIZE="4096" TYPE="ext4"
/dev/loop7: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/mapper/pve-vm--103--disk--1: PTUUID="86f54cb4-b5c2-43a9-9d05-a038f960d12e" PTTYPE="gpt"
/dev/loop5: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop3: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/mapper/pve-vm--121--disk--0: UUID="37a9a9cc-5301-4640-9555-0c100a121db1" BLOCK_SIZE="4096" TYPE="ext4"
root@pve:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 1.9M 1 loop /snap/btop/924
loop1 7:1 0 1.9M 1 loop /snap/btop/935
loop2 7:2 0 74M 1 loop /snap/core22/2292
loop3 7:3 0 66.8M 1 loop /snap/core24/1267
loop4 7:4 0 66.9M 1 loop /snap/core24/1349
loop5 7:5 0 73.9M 1 loop /snap/core22/2216
loop6 7:6 0 48.1M 1 loop /snap/snapd/25935
loop7 7:7 0 50.9M 1 loop /snap/snapd/25577
sda 8:0 1 58.7G 0 disk
├─sda1 8:1 1 58.7G 0 part
└─sda2 8:2 1 32M 0 part
nvme0n1 259:0 0 953.9G 0 disk
├─nvme0n1p1 259:1 0 1007K 0 part
├─nvme0n1p2 259:2 0 512M 0 part /boot/efi
└─nvme0n1p3 259:3 0 931G 0 part
├─pve-swap 252:0 0 7G 0 lvm [SWAP]
├─pve-root 252:1 0 96G 0 lvm /
├─pve-data_tmeta 252:2 0 8.1G 0 lvm
│ └─pve-data-tpool 252:4 0 795.8G 0 lvm
│ ├─pve-data 252:5 0 795.8G 1 lvm
│ ├─pve-vm--100--disk--0 252:6 0 8G 0 lvm
│ ├─pve-vm--102--disk--0 252:7 0 40G 0 lvm
│ ├─pve-vm--104--disk--0 252:8 0 8G 0 lvm
│ ├─pve-vm--106--disk--0 252:9 0 256G 0 lvm
│ ├─pve-vm--107--disk--0 252:10 0 100G 0 lvm
│ ├─pve-vm--105--disk--0 252:11 0 128G 0 lvm
│ ├─pve-vm--108--disk--0 252:12 0 8G 0 lvm
│ ├─pve-vm--109--disk--0 252:13 0 3G 0 lvm
│ ├─pve-vm--110--disk--0 252:14 0 2G 0 lvm
│ ├─pve-vm--111--disk--0 252:15 0 6G 0 lvm
│ ├─pve-vm--111--disk--1 252:16 0 20G 0 lvm
│ ├─pve-vm--112--disk--0 252:17 0 32G 0 lvm
│ ├─pve-vm--113--disk--0 252:18 0 10G 0 lvm
│ ├─pve-vm--114--disk--0 252:19 0 16G 0 lvm
│ ├─pve-vm--115--disk--0 252:20 0 8G 0 lvm
│ ├─pve-vm--116--disk--0 252:21 0 2G 0 lvm
│ ├─pve-vm--117--disk--0 252:22 0 12G 0 lvm
│ ├─pve-vm--103--disk--0 252:23 0 4M 0 lvm
│ ├─pve-vm--103--disk--1 252:24 0 120G 0 lvm
│ ├─pve-vm--103--disk--2 252:25 0 4M 0 lvm
│ ├─pve-vm--118--disk--0 252:26 0 10G 0 lvm
│ ├─pve-vm--119--disk--0 252:27 0 20G 0 lvm
│ ├─pve-vm--101--disk--0 252:28 0 10G 0 lvm
│ ├─pve-vm--120--disk--0 252:29 0 4G 0 lvm
│ └─pve-vm--121--disk--0 252:30 0 4G 0 lvm
└─pve-data_tdata 252:3 0 795.8G 0 lvm
└─pve-data-tpool 252:4 0 795.8G 0 lvm
├─pve-data 252:5 0 795.8G 1 lvm
├─pve-vm--100--disk--0 252:6 0 8G 0 lvm
├─pve-vm--102--disk--0 252:7 0 40G 0 lvm
├─pve-vm--104--disk--0 252:8 0 8G 0 lvm
├─pve-vm--106--disk--0 252:9 0 256G 0 lvm
├─pve-vm--107--disk--0 252:10 0 100G 0 lvm
├─pve-vm--105--disk--0 252:11 0 128G 0 lvm
├─pve-vm--108--disk--0 252:12 0 8G 0 lvm
├─pve-vm--109--disk--0 252:13 0 3G 0 lvm
├─pve-vm--110--disk--0 252:14 0 2G 0 lvm
├─pve-vm--111--disk--0 252:15 0 6G 0 lvm
├─pve-vm--111--disk--1 252:16 0 20G 0 lvm
├─pve-vm--112--disk--0 252:17 0 32G 0 lvm
├─pve-vm--113--disk--0 252:18 0 10G 0 lvm
├─pve-vm--114--disk--0 252:19 0 16G 0 lvm
├─pve-vm--115--disk--0 252:20 0 8G 0 lvm
├─pve-vm--116--disk--0 252:21 0 2G 0 lvm
├─pve-vm--117--disk--0 252:22 0 12G 0 lvm
├─pve-vm--103--disk--0 252:23 0 4M 0 lvm
├─pve-vm--103--disk--1 252:24 0 120G 0 lvm
├─pve-vm--103--disk--2 252:25 0 4M 0 lvm
├─pve-vm--118--disk--0 252:26 0 10G 0 lvm
├─pve-vm--119--disk--0 252:27 0 20G 0 lvm
├─pve-vm--101--disk--0 252:28 0 10G 0 lvm
├─pve-vm--120--disk--0 252:29 0 4G 0 lvm
└─pve-vm--121--disk--0 252:30 0 4G 0 lvm
root@pve:~# ls -l /boot/efi/EFI/proxmox/grubx64.efi
-rwxr-xr-x 1 root root 172032 Feb 11 20:18 /boot/efi/EFI/proxmox/grubx64.efi
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext4 errors=remount-ro 0 1
UUID=7D0B-6EBB /boot/efi vfat defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
Note: I added the "UUID=7D0B-6EBB /boot/efi vfat defaults 0 1". Wasn't there before and it's still broken when deleting the line.

1/2
 
2/2

root@pve:/sys/firmware/efi# fdisk -l
Disk /dev/loop0: 1.86 MiB, 1953792 bytes, 3816 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 1.87 MiB, 1957888 bytes, 3824 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 73.96 MiB, 77549568 bytes, 151464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 66.85 MiB, 70094848 bytes, 136904 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop4: 66.85 MiB, 70098944 bytes, 136912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop5: 73.95 MiB, 77541376 bytes, 151448 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop6: 48.09 MiB, 50421760 bytes, 98480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop7: 50.93 MiB, 53399552 bytes, 104296 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: KINGSTON OM8PGP41024Q-A0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8EA96FCF-55AA-D80F-408F-AEB9BB4E6B92

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 4061 2014 1007K BIOS boot
/dev/nvme0n1p2 5088 1053660 1048573 512M EFI System
/dev/nvme0n1p3 1054684 1953529194 1952474511 931G Linux LVM


Disk /dev/mapper/pve-swap: 7 GiB, 7516192768 bytes, 14680064 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/pve-root: 96 GiB, 103079215104 bytes, 201326592 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 58.71 GiB, 63043141632 bytes, 123131136 sectors
Disk model: Cruzer Glide 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xcb448206

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 123065599 123063552 58.7G 7 HPFS/NTFS/exFAT
/dev/sda2 123065600 123131135 65536 32M ef EFI (FAT-12/16/32)


Disk /dev/mapper/pve-vm--100--disk--0: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--102--disk--0: 40 GiB, 42949672960 bytes, 83886080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--104--disk--0: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--106--disk--0: 256 GiB, 274877906944 bytes, 536870912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--107--disk--0: 100 GiB, 107374182400 bytes, 209715200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: dos
Disk identifier: 0x26cb551f

Device Boot Start End Sectors Size Id Type
/dev/mapper/pve-vm--107--disk--0-part1 * 2048 207714303 207712256 99G 83 Linux
/dev/mapper/pve-vm--107--disk--0-part2 207716350 209713151 1996802 975M 5 Extended
/dev/mapper/pve-vm--107--disk--0-part5 207716352 209713151 1996800 975M 82 Linux swap / Solaris

Partition 2 does not start on physical sector boundary.


Disk /dev/mapper/pve-vm--105--disk--0: 128 GiB, 137438953472 bytes, 268435456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 8F612D6D-FC71-4218-AE43-291D3E782CC1

Device Start End Sectors Size Type
/dev/mapper/pve-vm--105--disk--0-part1 2048 4095 2048 1M BIOS boot
/dev/mapper/pve-vm--105--disk--0-part2 4096 268433407 268429312 128G Linux filesystem


Disk /dev/mapper/pve-vm--108--disk--0: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--109--disk--0: 3 GiB, 3221225472 bytes, 6291456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--110--disk--0: 2 GiB, 2147483648 bytes, 4194304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--111--disk--0: 6 GiB, 6442450944 bytes, 12582912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--111--disk--1: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--112--disk--0: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--113--disk--0: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--114--disk--0: 16 GiB, 17179869184 bytes, 33554432 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--115--disk--0: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--116--disk--0: 2 GiB, 2147483648 bytes, 4194304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--117--disk--0: 12 GiB, 12884901888 bytes, 25165824 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--103--disk--0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--103--disk--1: 120 GiB, 128849018880 bytes, 251658240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 86F54CB4-B5C2-43A9-9D05-A038F960D12E

Device Start End Sectors Size Type
/dev/mapper/pve-vm--103--disk--1-part1 2048 206847 204800 100M EFI System
/dev/mapper/pve-vm--103--disk--1-part2 206848 239615 32768 16M Microsoft reserved
/dev/mapper/pve-vm--103--disk--1-part3 239616 250007551 249767936 119.1G Microsoft basic data
/dev/mapper/pve-vm--103--disk--1-part4 250007552 251654143 1646592 804M Windows recovery environment


Disk /dev/mapper/pve-vm--103--disk--2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--118--disk--0: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--119--disk--0: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--101--disk--0: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--120--disk--0: 4 GiB, 4294967296 bytes, 8388608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/pve-vm--121--disk--0: 4 GiB, 4294967296 bytes, 8388608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes

Any help is much appreciated and I'm happy to provide more info asap.
Thanks in advance!
 
The Wiki gives you keys heh, use a debian live CD or a rescue shell.. you can try efibootmgr -n 0000 to avoid the 0003 entry that is probably unhappy.  If that works, well, set the boot order to start with the proxmox entry.

If it fails, mount your system disks, and at least root and /boot/efi, and run grub-install /dev/nvme0n1and update-grub to get your bootloader back? Proxmox Wiki will help, so will the Debian one about EFI: https://wiki.debian.org/GrubEFIReinstall
 
Last edited:
  • Like
Reactions: derMiepz
Gilou said:
The Wiki gives you keys heh, use a debian live CD or a rescue shell.. you can try efibootmgr -n 0000 to avoid the 0003 entry that is probably unhappy.  If that works, well, set the boot order to start with the proxmox entry.

If it fails, mount your system disks, and at least root and /boot/efi, and run grub-install /dev/nvme0n1and update-grub to get your bootloader back? Proxmox Wiki will help, so will the Debian one about EFI: https://wiki.debian.org/GrubEFIReinstall
Click to expand...
Thank you for your answer!

So I'm pretty sure I found the answer to my problem, but not how to fix it yet.

Using "efibootmgr -n 0000" works, but only once.
I then used "efibootmgr -o 0,1,2" to set the actual boot sequence, but it won't get saved after restarting Proxmox. It automatically sets 0001 as the first entry:

Code: 
root@pve:~# efibootmgr
BootCurrent: 0000
Timeout: 1 seconds
BootOrder: 0001,0000,0002
Boot0000* proxmox       HD(2,GPT,f9a7e04b-4d62-4a20-af20-2b28941ba115,0x13e0,0xffffd)/File(\EFI\proxmox\grubx64.efi)
Boot0001* UEFI OS       HD(2,GPT,f9a7e04b-4d62-4a20-af20-2b28941ba115,0x13e0,0xffffd)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
Boot0002  UEFI: Built-in EFI Shell      VenMedia(5023b95c-db26-429b-a648-bd47664c8012)0000424f
Boot0003* UEFI: SanDisk, Partition 2    PciRoot(0x0)/Pci(0x14,0x0)/USB(14,0)/HD(2,MBR,0xcb448206,0x755d500,0x10000)0000424f

It seems like there is an issue with "UEFI OS". Why?

When booting my server, a Minisforum UN1290, I only have "UEFI OS" as a boot option in the "Setup" menu. (Actual BIOS settings etc)
But when I check the "Boot Options" in the main menu, there is also a "proxmox" entry.

Manually selecting the "proxmox" entry works as expected, but since I don't have this option in the Setup menu, I always get that grub error after restart.WhatsApp Image 2026-02-11 at 22.58.42.jpegWhatsApp Image 2026-02-11 at 22.58.42ss.jpegWhatsApp Image 2026-02-11 at 22.58.47sss.jpeg
 
Last edited:
Wow I totally forgot to send and answer yesterday.
What I wanted to send is:

No I can't. I added pics after I already sent my post, showing the entries I have in the setup menu.

But your second suggestion worked. I googled some more and asked AI (I know, shame on me) and it seems like a rather common problem with AMI-based UEFI firmware. The firmware ignores custom BootOrder entries and always prioritizes the standard UEFI fallback path: "\EFI\BOOT\BOOTX64.EFI"

How I fixed it now:

1. Mount the EFI partition (if not already mounted)
Code: 
mount /dev/nvme0n1pX /boot/efi

2. Backup existing fallback loader
Code: 
mkdir -p /boot/efi/EFI/BOOT/backup
mv /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/backup/

3. Copy Proxmox GRUB to fallback path
Code: 
cp /boot/efi/EFI/proxmox/grubx64.efi \
   /boot/efi/EFI/BOOT/BOOTX64.EFI

4. Reboot
 
  • Like
Reactions: Gilou
Heh, well, if that works.. then, problem solved :P
I'm surprised it sees the boot option but doesn't allow you to set it.. OVH had some servers that would reset the boot order also without asking.. anyway, now you know a bit more about UEFI and GRUB, heh!
 
  • Like
Reactions: derMiepz
You must log in or register to reply here.
Top Bottom
Back