[SOLVED] VM cannot start | end kernel panic - not syncing
- Thread starter livioavalle
- Start date
Virtual disk corrupted? Physical disk of storage for virtual disks corrupted? Maybe memory errors? After restoring this VM (to a new VM, preferably on another Proxmox) from (known good) backups, does it work?
I tried mounting the VM disk on another VM and i can mount and browse it. The physical disk works, because it have other VM and CT disk and they all work.
That does not guarantee that all the data on all the disks is still correct. If your storage does not use ZFS or BTRFS then corruption cannot always be detected. Did you test the memory?
Assuming its not a hardware problem: What did you change inside the broken VM that might cause a incomplete or broken initramfs? Did the VM crash or did you lose power while updating or did you run update-initramfs with invalid configuration files?
Otherwise, it's probably a (temporary) hardware failure that causes corruption and restoring from backup might be easiest.
It was the initrd file corrupted because a crash when update-initramfs was working. I used a .dpkg-bak initrd file to start the vm and then restore the initrd normal file
Those are the little clues people need to help figure out what went wrong.
Glad you got it working again and thank you for sharing the solution.