February 25, 20179 yr I had a bit of a crash after changing up my array. I'm rebuilding my appdata from a CA backup and I know I can rebuild my dockers pretty easily. However, my entire VMs tab is blank. Completely blank. None of my VMs. No ability to create new ones. Nothing. Any idea how I fix this? Thanks!
February 25, 20179 yr Community Expert If you can't create new ones there's a strong possibility that libvirt.img is corrupt, post your diagnostics. Tools -> Diagnostics
February 25, 20179 yr Community Expert If it's corrupt you can restore it from a backup, if you don't have one you'll need to re-create it and and all the VMs, you can re-use the existing vdisks.
February 25, 20179 yr Author 18 minutes ago, johnnie.black said: If it's corrupt you can restore it from a backup, if you don't have one you'll need to re-create it and and all the VMs, you can re-use the existing vdisks. I don't mind rebuilding if I have to. But would that explain the tab being completely blank? See attached image. ocean-diagnostics-20170224-1737.zip Edited February 25, 20179 yr by ksignorini
February 25, 20179 yr Author Alright. So I restored my libvirt from a CrashPlan backup and now I have the page again. I can build VM's. But what do I do now to get my two good VM's back up and running? I have a copy of the XML but I don't know what to do with it? Do I build a new VM and just point it at the image? What if I type in the size incorrectly? Do I need to do this first, then edit the XML and paste it in? Or is there somewhere I just drop the XML and it all works? I'm very confused. Please help. Thank you!
February 25, 20179 yr Community Expert Feb 24 16:45:37 Ocean emhttp: shcmd (81): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/user/system/libvirt/libvirt.img' /etc/libvirt 1 |& logger Feb 24 16:45:37 Ocean root: mount: wrong fs type, bad option, bad superblock on /dev/loop0, Feb 24 16:45:37 Ocean root: missing codepage or helper program, or other error Feb 24 16:45:37 Ocean root: Feb 24 16:45:37 Ocean root: In some cases useful info is found in syslog - try Feb 24 16:45:37 Ocean root: dmesg | tail or so. Feb 24 16:45:37 Ocean root: mount error Libvirt was indeed corrupt, if you restored a backup it should have your VMs, if it hasn't it wasn't a good backup (I don't know if Crashplan can correctly backup that file while in use). To re-create your VMs just select "Custom" and paste the backup XML, adjust vdisk path if needed.
February 25, 20179 yr Author Thanks for the help. I restored libvirt and recreated the VMs but it looks like their images are busted too. I'll recreate them from backups and see what happens.
Archived
This topic is now archived and is closed to further replies.