Proxmox failed boot

E

ejkeebler

Member
May 10, 2021
25
1
8
50
I had an issue today. My vms were alive, but several things were not working. I could not get to my proxmox server through the gui or through telnet. So I shut down the vms and decided to reboot my proxmox host. When it rebooted, it just keeps saying booting: proxmox failed to boot and then i'm dead in the water. the vms are on a different disk. and I have a zfs setup on the device that proxmox is managing. I tried the rescue boot, but it doesnt do anything really. My current plan is installing proxmox on a USB drive and try to boot from that and see if I can at least get to the zfs and vms. And see if i can recover the proxmox disk.

Any ideas? What problems might i have if I just reinstall proxmox on the disk? Will i lose my vms/zfs share?
 
Hi!

Were there any mentionable changes before the issues surfaced (e.g. updates, config/hardware/networking/firmware changes)? Either way, does the boot fail before the bootloader (i.e. can you select e.g. a different kernel version)? If you can select a different kernel version, is there any difference between those?
 
dakralex said:
Hi!

Were there any mentionable changes before the issues surfaced (e.g. updates, config/hardware/networking/firmware changes)? Either way, does the boot fail before the bootloader (i.e. can you select e.g. a different kernel version)? If you can select a different kernel version, is there any difference between those?
Click to expand...
drive died, became unrecognized. I thought i had setup the drives in mirror, but I have no idea what happened and why the other drive will not boot, and now im concerned it will die soon, so I installed proxmox on a usb for now. I ordered 2 spinning disks to install proxmox on and getting rid of the older ssds i had used. all the vms were on a zfs pool on 2 nvme drives. I imported the pool, but i could not find the vms really. I wiped that pool recreated, set them up in a zfs mirror. imported my storage zfs pool so, all my data was good outside of the vms, not sure what I was going wrong there. I thought I would be able to import the vm pool and just add the vms back, that's obviously not how it works and i'll have to read up on migrating vms from one proxmox install to another, I dont want to spend another few days setting up the vms again. Fortunately I have all my docker compose files backed up, so getting some of the containers going again wasnt bad, but most of the configs were stored on the vms that I could not figure out how to restore.
 
Thanks, I had figured at worst I would have to recreate the vm, and then I could just copy anything from the old disk over, but that was obviously a giant mistake as there is no "directory" for my vm. I had only one vm that mattered and 1 lxc container. Reconfiguring them was not a huge pain, but I forgot I was not storing the data from the docker containers on my zfs share, because of so many issues with db's on nfs/cifs, so I was storing the dbs on the vm locally :). Wont make that mistake again. All my important files or large files all store on the ZFS storage, so not a huge deal in the end, but I dont want to lose any of that data again. I.e. resetting up all my home assistant, and reimporting all my recipes into mealie lol
 
If I click on my vm and lxc's and click backup, and choose snapshot, can I then restore them on a new proxmox install? Or do I need to shut them down? and do I still need the configs in /etc/pve ? If I need those configs, do I just copy those back to the new proxmox install and reboot?
 
You can backup a VM while it's running. Of course, the resulting backup can be restored on any other PVE host. If you've passed any hardware to the backed-up VM, it must be available on the target PVE, or you'll remove it from the VM's hardware after the restore.
 
You must log in or register to reply here.
Top Bottom