Everything was going pretty good until I saw a plugin that wanted the newest version of unraid; so I upgraded. The next day I found the server unresponsive; I did a reboot and found that my dockers and vms were gone. 

I started looking for back ups but I looks like I didn't make any. Even though I recall spending a lot of time looking up backup and stuff. And i did find a backup but it was a backup from a save file from a VM. Not the VM itself.

 

 

find /mnt -name libvirt.img
/mnt/user/system/libvirt/libvirt.img
/mnt/user0/system/libvirt/libvirt.img
/mnt/disk3/system/libvirt/libvirt.img

 

No backups found details on the files

root@Tower:/mnt/user/system/libvirt# stat libvirt.img
  File: libvirt.img
  Size: 1073741824      Blocks: 2097152    IO Block: 4096   regular file
Device: 0,52    Inode: 649362777788858824  Links: 1
Access: (0644/-rw-r--r--)  Uid: (   99/  nobody)   Gid: (  100/   users)
Access: 2023-03-24 11:40:07.460759411 -0500
Modify: 2023-03-24 13:32:54.094738686 -0500
Change: 2023-03-24 13:32:54.094738686 -0500
 Birth: -

root@Tower:/mnt/user0/system/libvirt# stat libvirt.img
  File: libvirt.img
  Size: 1073741824      Blocks: 2097152    IO Block: 4096   regular file
Device: 0,51    Inode: 649362777788858824  Links: 1
Access: (0644/-rw-r--r--)  Uid: (   99/  nobody)   Gid: (  100/   users)
Access: 2023-03-24 11:40:07.460759411 -0500
Modify: 2023-03-24 13:32:54.094738686 -0500
Change: 2023-03-24 13:32:54.094738686 -0500
 Birth: -

root@Tower:/mnt/disk3/system/libvirt# stat libvirt.img
  File: libvirt.img
  Size: 1073741824      Blocks: 2097152    IO Block: 4096   regular file
Device: 9,3     Inode: 6517375432  Links: 1
Access: (0644/-rw-r--r--)  Uid: (   99/  nobody)   Gid: (  100/   users)
Access: 2023-03-24 11:40:07.460759411 -0500
Modify: 2023-03-24 13:32:54.094738686 -0500
Change: 2023-03-24 13:32:54.094738686 -0500
 Birth: 2023-03-24 11:40:07.460759411 -0500

 

Looking at the Libvirt Log file I get find the following

2023-03-24 17:50:52.825+0000: 8645: info : libvirt version: 8.7.0
2023-03-24 17:50:52.825+0000: 8645: info : hostname: Tower
2023-03-24 17:50:52.825+0000: 8645: error : virPCIVPDParseVPDLargeResourceFields:555 : internal error: Checksum validation has failed
2023-03-24 17:50:52.829+0000: 8645: error : virPCIVPDParseVPDLargeResourceFields:555 : internal error: Checksum validation has failed

 

looks like there is still hope, I am running a parity check now to see if any of that can be restored.

 

I also read that you could recreate the VM using the same Vdisk but I can't seem to locate those anywhere.

The directory where I would have stored those is empty. I had a Windows 10 and Ubuntu VM

The docket can be restored fairly easily. It's the VMs I'm concerned about.

 

Any assistance would be much appreciated.

Fun times...

tower-diagnostics-20230324-1328.zip

Parity check won't restore any data, based on the btrfs transid both docker and libvirt images are new, I see you have an unassigned SSD, maybe that was your cache drive before? And the old libvirt and docker images are there?

The 3 drives are from a old camera storage; I looked in them already.

You know; i think your right; i think my cache drive is whats missing.

I'll see if i can toss that back on or view its contents.

JorgeB you nailed it.

The cache drive was unmounted.

And I am at fault for it. It was not caused by the upgrade but something I did.

I had removed IP_Storage which consisted of 2 drives.

But when I had removed this pool and must have removed that cache drive as well.

I remounted the cache drive and my VMs and docker are back.

 

My bad, Thank you very much JorgeB.