JimPhreak

So I've got 2 Intel 730 SSD's currently in a cache pool but the write speed to the BTRFS file system is just unacceptable and defeats the whole purpose of having a cache drive IMO. So I'd like to pull one of the cache drives out and go back to a single cache drive with the XFS file system. Are SSD's still not supported as array devices? And if not, any idea on when they might be? I'd love to use the second SSD for my Downloads share so it doesn't take up the space on my cache drive.

Thanks for the screen shot. Are you stopping your dockers before running the backup and if so how are you automating that?

How did you configure your WebSync job? Any chance you can post screens?

Strange...all my drivers are up to date and I only have 1 CPU core selected.

Ok, getting a little closer one step at a time haha. I downloaded the Win 10 ISO and ran the install from that. The setup ran and completed and the VM restarted as it should. It then proceded to boot back into Win7 and upon login this message comes up:

Upgraded all the drivers to the latest (virtio-win-0.1.109) just as instructed but still get the following error:

Anything I'm missing in my settings to increase my chances of getting a Win10 upgrade to work? Continues to bomb during the setup process.

Awesome...Thank you!

Is there any documentation on how to upgrade a Windows 7 VM to Windows 10? If I do an in place upgrade to 10 the setup fails during the process I'm assuming because the VM settings need to be altered first. But I'm wondering what they should be set to and at one point of the upgrade.

Can anyone chime in on the best way to backup docker appdata so I can convert my cache pool back to XFS and then move the data right back without causing docker issues?

That means you are using BTRFS. Thats basically what happened to my cache when I was running BTRFS. I switched it to XFS and have had no issues. Haha, I edited my last post seconds after you replied. So how is your cache currently configured right now? And how did you go about moving your data from the BTRFS cache pool to XFS? I thought you couldn't run a cache pool with XFS? You can't. But I will take speed and no corruption anyday!

That means you are using BTRFS. Thats basically what happened to my cache when I was running BTRFS. I switched it to XFS and have had no issues. I thought you couldn't run a cache pool with XFS? Or did you just get rid of your cache pool all together? My current cache pool consists of two Intel 730 SSD's which are pretty reliable SSD's but I run a decent amount of dockers and with it not being easy to backup docker appdata (have to run custom scripts to do so), I like the redundancy of two drives. But this speed is pretty killer, I don't think I can stand it because I do a lot of data transfers to my array.

Anyone have a suggestion for how to attack this problem and get to the root cause? Can I do iperf testing between my Windows box and unRAID? Not real good with linux so not sure the commands I'd run on the unRAID side and I don't see any dockers that include iperf as a utility.

Anytime I write to my unRAID shares from my Windows 10 machine I'm getting very slow speeds (25-30MB/s) even though these shares have the cache drive enabled and I can see the data being written to my cache pool. I mean these are the kinds of speeds I would expect with no cache but not with 2 SSD's in a cache pool. What gives?

These are the default mappings for the Linuxserver template which can't be changed until after I add the container and then go back in and edit them. However I just went in and changed the paths from /data and /media back to /downloads and /tv and now I'm working. What's the best way to update Sonarr? If I do so from the WebUI it reverts back after restarting the docker.

It looks like my volume mapping aren't being read properly by Sonarr: As you can see Sonarr is reading a /downloads and /tv volume. And another thing, if I do a manual update of Sonarr from within the webUI, it reverts back to an earlier version whenever I restart the Docker.

Is there any documentation on how this is done with regard to UPS's attached to unRAID guest VMs? i'm connected my APC unit to Windows VM, but this is similar to unRAID i think. first, i'm telneting to unRAID and power it down with sbin/powerdown then wait some time (1minute for me) and ssh to esxi host and excute "/sbin/shutdown.sh && /sbin/poweroff" look at unRAID /etc/apcupsd/doshutdown you can ssh from here to esxi host and execute command above.. if you have VMWare tools installed on unRAID, esxi will do clean shutdown i think.. (not tried yet..) I do have VMWare tools installed. I'll have to look into doing this when I get my new UPS next week.

Is there any documentation on how this is done with regard to UPS's attached to unRAID guest VMs?

ok, i just tested it on my test server (X9SCM-iif board) with 6.1 final and no change for me - issue are still there.. for me, a quickest workaround is to add second USB device - flash or UPS and then no issues.. Interesting. So if you don't passthrough your USB controller and just add a second USB device in addition to the boot flash to your VM the issue is resolved? How exactly would one use a UPS (or even want to) with a VM guest? Wouldn't you want the UPS to shut down the entire host?

I had to re-install Sonarr after recreating my docker.img file and I'm getting the following error message under Health Status in my Sonarr settings: I believe this is a permissions issue but I'm unsure how to resolve it without breaking other permissions.

Seeing the following messages in my console. Not showing up in my log accessed through the webGUI.

Well, it's filling up again. The category paths are still blank so aren't the problem. However I see under the UNPACK settings there is mention of the following two directories: ${AppDir}/unrar ${AppDir}/7za I don't see where you can define ${AppDir} so could that be my problem? What do others have this set to? P.S. I upgraded to 6.1 today.

I just get the following output: Been lots of reports of this. Normally resolved by Disabling/Enabling notifications via Settings. Yes that fixes it.

Jim.. are you back on baremetal.. cuz I'm having this as well as a guest on ESXi? Nope, I'm still on ESXi 5.5 as a guest.

Has anyone who is still have issues with resets had a chance to test with the new version 6.1? I would but I have to shut my entire VM server down to remove the passthrough configuration and then have to shut it down again to configure it again if it doesn't fix the issue. I'm doubting the issue is resolves since none of the 6.1RC's seem to fix it but it's worth a shot.