dvd.collector

You can't format a disk with the plugin and then use it on the array, it will appear as unmountable. You can, however, assign the target drive as a single slot cache device, select XFS as the file system, and format it that way. It can then be moved to another system, and / or mounted using UD. Or just copy the files across while it's in the cache slot. What, exactly, are you trying to accomplish? Your post is not fully fleshed out as to why you couldn't just rebuild the new drive in the old drive's slot, which would populate the old drive's data on the new drive. I was basically upgrading from a 1g to a 2g drive and trying to change filesystem from reiser to XFS at the same time. Guess I was trying to be too clever. So is there now no way to read the data on the disk formatted as XFS through the UD plugin?

Uh Oh, what have I done wrong here??? I thought I would use this plugin to be able to move items off an array disk to a new disk formatted as XFS, mounted with this plugin. That all went fine and the data was copied across. My plan was then to remove the old array disk and put in the new disk which was already formatted as XFS with my data on it and then do a new config and rebuild parity. HOWEVER, the new disk is showing as not formatted. Even when I try re-mounting it now with unassigned devices the mount button is greyed out and just the format button is available! Where have I gone wrong here? Can I save the data on the disk that I used in unassigned devices??

I have a Win10 VM that was working fine prior to the 6.2 upgrade I did around a month ago. Since the 6.2 upgrade the VM now fails to start around 50% of the time, hanging at the windows loading screen. The VM shows as paused in the VM manager. I have to force kill it and then restart, and it usually works fine the second time. I can see the following in the log: 2016-12-11 09:48:33.368+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower Domain id=1 is tainted: high-privileges Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) KVM internal error. Suberror: 3 extra data[0]: 80000b0e extra data[1]: 31 RAX=0000000000000001 RBX=ffffe4018abd3750 RCX=ffffe4018abd3750 RDX=fffff80833c827f0 RSI=ffffe4018abafa80 RDI=ffffe4018aba9180 RBP=ffffe4018adcf900 RSP=ffffe4018ac4df20 R8 =ffffe4018abd3750 R9 =ffffe4018abd36c0 R10=0000000000000006 R11=ffffe4018adcfb40 R12=00000004de385657 R13=ffffbe86b5947f70 R14=ffffe4018ab23180 R15=fffff8022c61d000 RIP=fffff80833c82812 RFL=00010202 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] CS =0010 0000000000000000 00000000 00209b00 DPL=0 CS64 [-RA] SS =0018 0000000000000000 00000000 00409300 DPL=0 DS [-WA] DS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] FS =0053 0000000000000000 0000bc00 0040f300 DPL=3 DS [-WA] GS =002b ffffe4018aba9000 ffffffff 00c0f300 DPL=3 DS [-WA] LDT=0000 0000000000000000 ffffffff 00c00000 TR =0040 ffffe4018abafb40 00000067 00008b00 DPL=0 TSS64-busy GDT= ffffe4018abb6c00 0000006f IDT= ffffe4018abb6c70 00000fff CR0=80050031 CR2=ffffe4018abd3754 CR3=00000000001aa000 CR4=001506f8 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000d01 Code=c1 01 83 f8 01 74 1c 8b 41 04 85 c0 74 0d 0f 1f 40 00 f3 90 <8b> 41 04 85 c0 75 f7 33 c0 48 83 c4 20 5b c3 48 8b 41 08 48 8b 51 18 48 8b 49 10 ff 15 7d I don't suppose this means anything to anyone?

I have a Win10 VM that was working fine prior to the 6.2 upgrade I did around a month ago. Since the 6.2 upgrade the VM now fails to start around 50% of the time, hanging at the windows loading screen. The VM shows as paused in the VM manager. I have to force kill it and then restart, and it usually works fine the second time. I can see the following in the log: 2016-12-11 09:48:33.368+0000: starting up libvirt version: 1.3.1, qemu version: 2.5.1, hostname: Tower Domain id=1 is tainted: high-privileges Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) KVM internal error. Suberror: 3 extra data[0]: 80000b0e extra data[1]: 31 RAX=0000000000000001 RBX=ffffe4018abd3750 RCX=ffffe4018abd3750 RDX=fffff80833c827f0 RSI=ffffe4018abafa80 RDI=ffffe4018aba9180 RBP=ffffe4018adcf900 RSP=ffffe4018ac4df20 R8 =ffffe4018abd3750 R9 =ffffe4018abd36c0 R10=0000000000000006 R11=ffffe4018adcfb40 R12=00000004de385657 R13=ffffbe86b5947f70 R14=ffffe4018ab23180 R15=fffff8022c61d000 RIP=fffff80833c82812 RFL=00010202 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] CS =0010 0000000000000000 00000000 00209b00 DPL=0 CS64 [-RA] SS =0018 0000000000000000 00000000 00409300 DPL=0 DS [-WA] DS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] FS =0053 0000000000000000 0000bc00 0040f300 DPL=3 DS [-WA] GS =002b ffffe4018aba9000 ffffffff 00c0f300 DPL=3 DS [-WA] LDT=0000 0000000000000000 ffffffff 00c00000 TR =0040 ffffe4018abafb40 00000067 00008b00 DPL=0 TSS64-busy GDT= ffffe4018abb6c00 0000006f IDT= ffffe4018abb6c70 00000fff CR0=80050031 CR2=ffffe4018abd3754 CR3=00000000001aa000 CR4=001506f8 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000d01 Code=c1 01 83 f8 01 74 1c 8b 41 04 85 c0 74 0d 0f 1f 40 00 f3 90 <8b> 41 04 85 c0 75 f7 33 c0 48 83 c4 20 5b c3 48 8b 41 08 48 8b 51 18 48 8b 49 10 ff 15 7d I don't suppose this means anything to anyone?

many thanks for this guide!

There are several reports about issues with watched status at the Plex forum. Some clients works fine but a few have this issue. Thanks yeah, it seems PHT now doesn't work properly with PMS and isn't going to be fixed!

Anyone having weird Plex issues recently with it keeping track of watched status etc. Please was working fine for many months, but now is not marking shows as watched when I get to the end not remembering when I left off and allowing me to resume not adding items I'm watching to the "on deck" section I'm assuming its something related to the latest update, although I hadn't even noticed it had updated! Anyone got any ideas?

Maybe this is an nvidia va amd thing then. Pretty sure Battleborn is an nvidia "sponsored" game as it has physx in it. Maybe Doom is optimised for AMD? Might explain battleborn working fine on your nvidia card and doom on my AMD one... Still, 15fps seems really low even taking that into account.

If you are playing Doom thru Steam, enable the fps counter... its in the steam settings, In-Game section - "In game fps counter". That should give you a good indication of your framerate. Anything above 30 should be playable, but of course higher is better.

I've got doom running on a windows VM and it runs fine at around 60fps with most (if not all) settings on the max. On the other hand, Battleborn runs really slowly on the same hardware...

Hi binhex, that would work... if Sonarr supported use of a proxy... which as far as I can tell it doesnt :'(

Hi all, is there a docker for Sonarr which has a built in VPN similar to the delugeVPN docker? The reason I need this is because my ISP has blocked quite few indexers that I'd like to use. The actual downloading isn't an issue as usenet itself isn't blocked and I use delugeVPN for torrents so that's OK.

How are you passing the XBOX controller though to the VM? Mine will only work with the whole USB port/hub passed through to the VM rather than the individual controller.

I notice SABNZBd has been updated to v1 now - so has needo done this? If so, can it be updated to v1.01?

I turn mine off as it seems to use around 50w power more when the VM is running. I guessing this is because the graphics card is active whilst the VM is running.

Try installing the dynamix stats plugin and watch the system stats page. That will show you what speed the disk is writing at. This is how I identified that it seems to write to RAM first, as you see RAM fill up before the disk writing seems to start.

Are you transferring to a cached share? i.e. writing to your cache drive? I see the same effect as you when I'm writing directly to the array, as it seems I can transfer over the network faster than my array can write. I think the initial spike you see is it writing to RAM, which then once full causes the "pause" and eventually a failure if you don't limit your connection speed. I don't see this effect writing to my cache SSD though as that can sustain the write speed higher than my network. To work around the issue when I was writing directly to the array I found a copy program that allowed me to throttle the speed I was transferring at. Limiting to ~40MB/s seemed to allow the transfer to complete successfully.

check you are sending the request to the correct MAC address?

Didn't work for me with Minecraft (and others).

Which game(s) won't install on the network drive?

is it possible to alter the mover script to enable turbo writes before the mover runs and turn it off again afterwards?

There is a workaround for the mapped drive issue... create a batch script that maps the drive at logon. This at least means you don't need to double click on it for it to be "seen" by windows. However I still find that it causes some programs to fail that require the drive to be present. I assume because they load before they script mapping the drive runs. Haven't figured a way around that one yet.

solved by running the file check tools.

Saw this in my unraid log at boot: Jan 20 08:42:37 Tower shfs/user: shfs_readdir: fstatat: Sp.2015.1080p.Bluray.DTS-HD.7.1.mkv (13) Permission denied Jan 20 08:42:37 Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk5/Films/Sp (13) Permission denied So then checked the directory and this shows: root@Tower:/mnt/disk5/Films/Sp# ls -l /bin/ls: cannot access Sp.2015.1080p.Bluray.DTS-HD.7.1.mkv: Permission denied total 0 ???? ? ? ? ? ? Sp.2015.1080p.Bluray.DTS-HD.7.1.mkv I'm unable to delete or do anything with this file. Can anyone advise what has happened? This file was placed on this disk by the mover.

OK thanks Jonp. Any comment on why the CPU use in the windows VM shows zero, but in top (or on the unraid dashboard) seems to hover at 30% use by the qemu-system-x86 process? Does this happen on your rig?