VM crashed - how to save it?

You can boot a live image and try to repair the installation or you can restore the vm. Looks like disk or module is missing or both.

Can you do ls for /dev?
 
Did you change anything in the VM config before this happend? Is it a new VM or converted from another type like .vmdk, please share your vm config (/etc/pve/qemu-server/<id_of_your_vm>.conf)?
AFAIK if this is a unifi controller, it should make backups of the configuration on its own which means in the worst case you could just restore it that way.
 
tim said:
Did you change anything in the VM config before this happend? Is it a new VM or converted from another type like .vmdk, please share your vm config (/etc/pve/qemu-server/<id_of_your_vm>.conf)?
AFAIK if this is a unifi controller, it should make backups of the configuration on its own which means in the worst case you could just restore it that way.
Click to expand...
The VM has been running for almost a year, nothing changed.
Heres the config:
agent: 1
bootdisk: sata0
cores: 2
ide2: local:iso/ubuntu-18.04.2-live-server-amd64.iso,media=cdrom
memory: 8192
name: unifi
net0: virtio=8A:B0:B7:9E:3D:A9,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
sata0: local-lvm:vm-100-disk-0,size=64G
scsihw: virtio-scsi-pci
smbios1: uuid=64e6ed92-acdf-4fbd-b95f-57ae52026868
sockets: 1
vmgenid: bfdee692-fdf6-4339-a3dc-73888454e350
 
Ok, boot it from a live cd. You can select the boot device from the gui options tab of your VM. You can use the iso which is still present in your config if you want or any other live image your are used to, after boot open a console with ctrl+alt+F2 and check with "lsblk -f" which block devices are still there. Look for the not found uuid and which uuid's are still present. You'll need to make sure that the uuid referenced in the vm's fstab is still the correct one.
 
You must log in or register to reply here.
Top Bottom