krone6

Thanks for the link. I'll save it and reference it in the future. I forgot and for some reason didn't update my original post with the resolution. Since then I've upgraded to each new release as it gets updated so whatever the latest version is is the one I'm on now and the VMs work fine, though they're still super picky sometimes.

Please create your own thread since this one has been solved.

Thanks for the link. I'll save it and reference it in the future.

Thank you for pointing me in the right direction as it allowed me to figure it out. Bridging was enabled however I created the VM when virbr0 was set as defualt. After setting br0 as the new default I didn't update the xml in my virtual machine, so it was still using the wrong adapter.

I've looked at the wiki multiple times and in this forum (and Google) though cannot find how I was able to bridge the VM's adapter to the host's. I've already tried the three bridges in settings with no luck as well as assigning a static IP. All I'm after is to get my VM on the 192.168.5.0/24 network instead of the 192.168.122.0/24 network it's currently on. All drivers have been installed. Thank you for any assistance and if there's an article I can read that explains this that'd also be helpful so I can go to that in the future if I ever forget. Network: 192.168.5.0/24 Host IP: 192.168.5.10 Gateway: 192.168.5.254 VM: 192.168.122.232 (I want this to be 192.168.5.11) OS: Server 2012 R2 Standard Build 9600 64-bit

I'm confused on a couple parameters when setting this docker up. Currently I only have one unraid server with a DVR virtual machine for a few cameras. My only goal currently is to perform an rsync for daily/monthly backups on certain folders to another hard drive so I know exactly what's on it. 1: What'd the /Source be? Does that just point to my data share where all data resides on the unraid machine 2: Where would the /Backups reside? The actual directory all rsync jobs complete in? Thank you. I'm not an expert in rsync as you can tell.

Update: I was finally able to recover a bunch of stuff with File Scanvenger. Still shifting through so many documents and pictures, however it's all off the hdd and onto a spare on. I didn't do a deep format of this before using it and recovered a heck of a lot of pictures and documents that don't relate to me. I even found a form filled out by the director of technologies at 2K games ordering the Havok physics engine with his signature. I am definitely going to have a better backup in place as I can understand losing a bunch of pictures that didn't mean much and losing family pictures, documents, resumes, receipts, and everything else in one huge derp. Homelab or not that is way too unacceptable. This thread can be closed as it has been resolved.

Update: Plugged the disk into my computer through the onboard SATA bus instead of a USB adapter and the programs are finding it instead of a RAW drive. Doing a long (deep) scan using File Scavenger currently though that'll take 7 hours. I see 376GB on it so the data's there and am confident I can retrieve it all in tact. Thank you for the replies, everyone. I'll try the four tools out to see if any of them help and update when I find more. To garycase: What if I told you there are no backups yet? Would I get slapped for derping?

Resolution: File Scanvenger successfully recovered files and has allowed me to sort through them all. It sucks this happened but at least I got stuff back. Unraid became very sluggish and unresponsive, knocking out explorer.exe on my computer after just a couple of options in the web GUI or just straight up after a couple hours with no VMs running. I decided to reinstall from scratch which has fixed these issues. The new problem is that I accidentally assigned my main data drive as a second parity where it became unmountable once I changed it to a data drive. A party check was not run when it was added as a second parity, however. I've already ran a parity check once I fixed my mistake as well a sxfs_repair -v per the wiki which was unablet to find any working superblocks.Window utilities to read xfs drives failed to work and threads found here have not worked either. What can I do to fix this issue as it has all of my data. I've not bought additional drives yet though will definitely do so after this. The diagnostics zip will be found attached. I have the backup of my old unraid install and can get diagnostics from that if needed. And because I know someone will ask, yes, the right 4TB drive is in the parity slot. Before I enabled the array I put the backup unraid onto the flash drive and took a picture to make sure to avoid this exact situation. ground-diagnostics-20160517-0807.zip

Well mine is at /mnt/user/system/libvirt/libvirt.img which is where the upgrade process put it and that works fine for me. Since the 'system' share is set as cache only that is a the same as /mnt/cache/system/libvirt/libvirt.img /mnt/user/Virtual Machines/libvirt.img is also cache only and didn't work for me so it's strange you had better luck than me. At least future users upgrading can look into this thread in case they run into similar and use what we've both experienced.

Fixed it. libvirt.img cannot be anywhere other than /mnt/cache/libvirt.img even if you put it in a folder that /is/ the cache drive. It must specifically be that exact path. Once I make it /mnt/cache/libvirt.img the status changes.

IT should be created by unraid. You did try to put libvirt.img in the path? Yes, that was one of the new things I tried earlier.

Tried a few new things though nothing's working. Where can I download the libvirt.img as I can't find it anywhere? Also I have two virtIO isos in my folder after downloading and cannot see them in explorer even with hidden files enabled. They show up in unRaid's GUI, though.

Attached will be the screenshot of what I see. All of the file paths should be right with the status in the top right. My array is started I just took the picture before it was. After checking it didn't make a difference whether it was or not as the status still said disabled either way.

After upgrading to the new beta (and checking over all of the changes/warnings) the status in VM manager says disabled. I've changed some settings in advance mode to match where the files are located and it stayed that way. Turning it off and then on didn't solve it either. Is there something I can do to fix this otherwise I looks like it's back to 6.1.9? Pictures on request since I don't know what'd be relevant to everyone here. Thank you. ground-diagnostics-20160320-1047.zip