what causes the missing bootloader after running an update?

[nttec]

we just upgrade to this version

PVE Manager Version pve-manager/6.4-13/9f411e79
Kernel Version Linux 5.4.162-1-pve #1 SMP PVE 5.4.162-2

and haven't decided to upgrade to 7.x version

we really don't want to do an update on the system due to the problem with some vm's getting an error with their bootloader, most of our VM runs with either FreeBSD 13.0 or ubuntu, and some of these VM's when we do an upgrade has missing bootloader when return.

before we are able to fix this, but now it is basically unusable and we can't fix it, and deleting re-installing the VM is not actually a good option since this VM is a live client.

we also have a backup of this vms, and we tried to load from back up but it has the same problem. missing boot loader, though before we do the update this VM works perfectly without issue.


my question is, is this avoidable? is there something that we are missing to make sure this will not happen when we do the next kernel upgrade? this looks like happens with everyone regarding if they have a subscription or not. what causes the missing bootloader after running an update?

 

[nttec]

after doing the upgrade mention above, we are now experiencing random VM having the Boot failed problem. from FreeBSD 13 to Centos 7.

anyone, any idea or solution?

 

[VictorSTS]

But... VMs are isolated from the host the run on. Their bootloader is *in* the VMs boot disk, not on Proxmox. That means that an update of Proxmox won't change anything inside the VM.

I have done many updates/upgrades/migrations from Proxmox 3, 4, 5, 6 and 7 with Ubuntu/Debian, CentOS/Redhat and Windows VMs and never had a "bootloader" issue.

Maybe I'm not understanding the problem correctly. Maybe they are containers instead of VMs?

 

[nttec]

But... VMs are isolated from the host the run on. Their bootloader is *in* the VMs boot disk, not on Proxmox. That means that an update of Proxmox won't change anything inside the VM.

I have done many updates/upgrades/migrations from Proxmox 3, 4, 5, 6 and 7 with Ubuntu/Debian, CentOS/Redhat and Windows VMs and never had a "bootloader" issue.

Maybe I'm not understanding the problem correctly. Maybe they are containers instead of VMs?

definitely VM's, I installed it myself. freebsd only runs on vm as well. I have VM that has ubuntu 20.04 on it and centos 7 also having the same issue. centos 7 is easier to fix just need to restore from backup(but not ideal if it contains data collected on a day-to-day activity), but for Ubuntu and freebsd the boot partition has to be recreated.

 

[Tmanok]

definitely VM's, I installed it myself. freebsd only runs on vm as well. I have VM that has ubuntu 20.04 on it and centos 7 also having the same issue. centos 7 is easier to fix just need to restore from backup(but not ideal if it contains data collected on a day-to-day activity), but for Ubuntu and freebsd the boot partition has to be recreated.

Not trying to be rude, but are you certain that you simply updated or did someone also remove packages? Adding or removing custom KVM could hypothetically change some of the tools used by PVE.

Although I have not used PVE for as long as Victor, since version 5 I have never ever witnessed VMs being unable to boot for anything other than unique host configuration or changing VM configuration. If the guests use EFI, did your update unmount the storage location of the EFI disks? Generally PVE will prevent booting altogether but like I said I really cannot think of a good reason for guests to stop booting properly...

Tmanok

 

[nttec]

Not trying to be rude, but are you certain that you simply updated or did someone also remove packages? Adding or removing custom KVM could hypothetically change some of the tools used by PVE.

Although I have not used PVE for as long as Victor, since version 5 I have never ever witnessed VMs being unable to boot for anything other than unique host configuration or changing VM configuration. If the guests use EFI, did your update unmount the storage location of the EFI disks? Generally PVE will prevent booting altogether but like I said I really cannot think of a good reason for guests to stop booting properly...

Tmanok

Yes, I am sure that there is no modification happening, we've been using proxmox for almost 4 years now and only set it up as how the proxmox should be set up and we didn't remove any package. there are actually a few threads here that have had the same issue since 2020, this is also the main reason why we didn't upgrade immediately. we are clueless as well on why it's happening and we cant do experiments on it since it's being used for live projects of ours.

 

[Tmanok]

Yes, I am sure that there is no modification happening, we've been using proxmox for almost 4 years now and only set it up as how the proxmox should be set up and we didn't remove any package. there are actually a few threads here that have had the same issue since 2020, this is also the main reason why we didn't upgrade immediately. we are clueless as well on why it's happening and we cant do experiments on it since it's being used for live projects of ours.

That is quite grave and very perplexing, hopefully a proxmox staff member can offer better assistance. In the meantime I will ponder further troubleshooting steps.

Cheers. And good luck.


Tmanok