September 22, 20223 yr Community Expert No clue what happened, but Docker and VM tab are now empty. Attaching log for troubleshooting. Thanks for your help! tower-diagnostics-20220922-2314.zip
September 22, 20223 yr Community Expert You have filled the pool disk and corrupted their img files. After you make room you will have to recreate them. docker.img is easy, do you have a backup of libvirt.img? https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file Many of your array disks are very full also. Full disks don't perform as well, and if you ever need to check filesystem, repair will need some free space to work in.
September 22, 20223 yr Author Community Expert Thanks for your quick note. I don't think I have a backup of the libvirt.img. That's needed for reinstalling the VMs? Any other way to recreate my VMs?
September 22, 20223 yr 1 hour ago, steve1977 said: I don't think I have a backup of the libvirt.img. That's needed for reinstalling the VMs? Any other way to recreate my VMs? Your VM disks should still be ok, but you will need to recreate the configurations to the best of your ability and point to the existing vdisks. The libvirt.img holds the XML configuration files as well as any other customizations and settings like autostart and such. How many VM's?
September 23, 20223 yr Author Community Expert Thanks. Docker indeed went smoothly. Struggling to remember how I had the VMs setup 😞 Started with one of the 3 VMs. Getting the following error: "VM creation error: cannot open directory '/etc/libvirt/hooks/qemu.d': input/output error. Any idea what could be causing this and how to solve?
September 23, 20223 yr 28 minutes ago, steve1977 said: cannot open directory '/etc/libvirt/hooks/qemu.d': input/output error. Any idea what could be causing this and how to solve? Sounds like the libvirt.img is still corrupted.
September 23, 20223 yr Author Community Expert How to uncorrupt it? I deleted the docker file as suggested per the link. So, docker containers are working again. But VM remains non-corrupting. Could also be because I may have done something wrong in the VM settings though.
September 23, 20223 yr Community Expert Delete and recreate libvirt similar to what you did with docker.
September 23, 20223 yr 13 hours ago, steve1977 said: Started with one of the 3 VMs If you can still access the XML's you can save that to a text document before you delete the libvirt.img file. That way you can paste back the configs exactly as they were.
September 23, 20223 yr Author Community Expert 1 minute ago, JonathanM said: If you can still access the XML's you can save that to a text document before you delete the libvirt.img file. That way you can paste back the configs exactly as they were. Thanks. Where are the XML stored?
September 23, 20223 yr /etc/libvirt/qemu or if you can still edit the VM's just switch to advanced view.
September 23, 20223 yr Author Community Expert Maybe easier to first try whether I can get the config right. Shouldn't be so difficult. Basically just need to remember the bios type / number, which I can try various options. Rest should be quite clear. After deleting the libvirt file, do I need to recreate it or does this happen automatically?
September 23, 20223 yr 35 minutes ago, steve1977 said: After deleting the libvirt file, do I need to recreate it or does this happen automatically? Disable the VM service in settings, delete the libvirt.img file, when you enable the VM service it should be recreated.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.