wrong boot disk. send help.

cheeki-breeki

New Member
Oct 20, 2023
18
0
1
got into a bit of a mess.

i'm running proxmoxVE on Disk1.

i then installed proxmoxVE on Disk2.

now when i try to boot into Disk1, it boots from Disk2.

strange thing is, that dis2 isn't even listed as bootable device from bios, because i needed to mod the bios with nvme module. so disk1 is selected boot disk, but uefi or something else is switching to disk2 in boot process.

tried to restore grub and vfat partitions, by overwriting the first 2 partitions of disk1 from a backup before installation on disk2, to no avail.

i'm assuming i need to do something with pve-efiboot-tool and/or etc/fstab.

efibootmgr showed disk2 as first priority.

i changed it to disk1, but it had no effect.

zfs on disk1 has label rpool-OLD, and is not listed with zpool status, and no pool available for import.

path is also different in efibootmgr;

disk1: efi/boot/bootx64.efi

disk2: efi/systemd/systemd-bootx64.efi

perhaps because disk2 is nvme.

but disk2 entry has changed partuuid to be the same as disk1, after changing boot order in efibootmgr (maybe i also ran efibootmgr refresh)

i'm considering cloning disk1 over disk2, but fear more config problems.
 
Last edited:
Check ' efibootmgr ' output and the man page for same

Proxmox isn't really designed for dual/triple boot; as a hypervisor it's more designed to take over the server.
If you want to boot from disk1, remove disk2.

Recovering a win10 boot is a completely different matter and may require win10-specific utilities. Hope you have backups.
 
Check ' efibootmgr ' output and the man page for same

Proxmox isn't really designed for dual/triple boot; as a hypervisor it's more designed to take over the server.
If you want to boot from disk1, remove disk2.

Recovering a win10 boot is a completely different matter and may require win10-specific utilities. Hope you have backups.
have put my reply merged with first post for newcomers.

sure would be nice if anybody else had a suggestion for a solution