The backups are made via the Proxmox web interface.I created a backup of each machine to a network share (backup server)īefore I executed any update related command.I'm 100% sure all the VMs worked find before the Proxmox upgrade.How can I be sure that this is not happening again? How did this occur? is it my fault? is it a bug? is it a known issue?Īs I'm scared that other VMs will also break permanently.If it's not fixable, is there a way to enter the disk so I can get the data? None of them works as they all give the same issue. It contains 170 GB of mails and the only backup I have is "proxmox backups" (images. Unfortunately, this does not work for the most important machine, The only thing that worked for the most of the VMs was restoring the backup. I Googled for hours and found a lot of similar issues. So I did it again and after that all the VMs gave the concerning error. After some Google attempts I found a post somewhere that it sometimes helps to reboot the host, ![]() Some of the VMs gave the error Boot failed: not a bootable disk in the console and kept rebooting. Some VMs (start on boot) also worked directly. ![]() The LXC containers were started (start on boot) without any issue. (Maybe they have a relation with the issues I'm now running into.)Īfter the upgrade finished, I restarted the host to complete the upgrade. Which I was worried about, but the upgrade just continued. I followed these steps: Upgrade Proxmox VE from 6.x to 7.0ĭuring the upgrade I had some errors about "disk not found".First upgrade to the most recent 6.x version with apt-get update followed by apt-get upgrade-dist.I did it according to the following steps: Today I decided to upgrade Proxmox Virtual Environment (PVE)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |