Tybio

The top level "Media" directory is totally optional, I can see why some people like it so they only have one share on the network. It's personal preference, no real impact to operation either way as you would still add the TV and Movies directories separately. As to allocation, I prefer to have my media mixed for the simple reason that TV shows create their directory when the FIRST show of the season comes out, then for the rest of the TV year episodes are added to that directory (and with split level, the same disk). This means that if you are running all of your disks near capacity then you can get into an ugly situation, so I always check toward the end of each summer to make sure I have one disk with a fair amount of free space that Unraid will use for new season directories for the new year. That means I often "fill up" free space on other disks with Movies to max my usage. I'm a huge fan of season folders per disk, as if you binge a show having to wait for disks to spin up between each episode can get a little annoying, but there are considerations you have to take into account doing this. As far as plex goes, how you split directories over disks isn't going to matter a bit to Plex as it sees them as one big folder.

While it is good, I just can't really get into cases that you have to mod with power tools. It does end up being a better case, I grant :). We really do need a new hot-swap solution, I'd love a Define with hot-swap (just spin the cage and give it freaking caddies!)

I've found the 6+TB drives to be more reliable and faster than the older smaller drives. However right now the sweet spot is at 8TB drives, you can get a WD external and shuck it for ~$170 (See the good deals forum). I'm currently running a 10TB parity and it's amazing. Faster than any of my other drives, never goes about 28 degrees. With drives, there is little risk in the consumer space, by the time they get to us they have had to solve the problems for the large enterprise customers (like Amazon, Google, FB etc) so if they were "iffy" they would never have been deployed in the first place.

Best option I've seen to date is this: Not run it myself, but thought I'd point it out.

Seems that you can: https://www.newegg.com/Product/Product.aspx?Item=N82E16811129021

With unraid you can lose as many disks as you have parity disks. So with one parity disk, you can have one failure without any data loss (provided you rebuild onto a good disk). If a second disk fails then you lose the data on both of the disks that have failed, but data on other drives is fine (but unprotected until you fix parity)

I would do it, in fact I'm not sure I'd be willing to do without split level. I have the following setup: Movies - Split at top level TV - Split top two levels This means that each season of a show can be on a different drive, which really helps pack data onto drives as you don't have to figure out which shows are "Active" and will need more space when you have disks that are nearly full. A much safer way for those with automatic media additions (NZBGet, Sonarr, Radarr).

The file is in your library, your library isn't in the docker. Just install the Nerdpack plugin and then add mediainfo to unraid and process the file. Mediainfo output isn't going to change based on running it from within the docker or not (And if it does, we have a much bigger problem here

Thanks for the update! I'll check things over the next few days...really love the new Gather feature

I had always thought that the WD80EFZX helium and the WDC_WD80EFAX were non, but I'm not sure.

Just picked up two, both the larger cache. Had to get them to price match at check-out as they were still labeled as $179 in the store. Preclearing now.

I'm also not sure the % complete for Gather is operating correctly, I just passed 65G of a ~235G gather operation where I'm moving all ~235G to a new disk and it is sitting at 3.15% complete, thus the time to completion seems way off. Minor problem, but I thought I'd point it out! Edit: The gather finished, it was at exactly 11.11% when complete. Hope that helps.

Also, as a feature request, just to help my OCD would it be possible to remove the root directory from the disks where it is empty? Even if this works, in the above post it looks like it would leave /mnt/disk4/Andromeda in place, just empty.

Ok, here you go: I: 2017/08/18 18:13:10 core.go:775: Running Move operation ... I: 2017/08/18 18:13:10 core.go:905: Command Started: (src: /mnt/disk4) rsync -avPRX "TV/Andromeda/Season 1" "/mnt/disk3/" I: 2017/08/18 18:13:58 core.go:987: Command Finished I: 2017/08/18 18:13:58 core.go:993: Current progress: 1.06% done ~ 1h15m51s left (66.70 MB/s) I: 2017/08/18 18:13:58 core.go:1005: Removing: rm -rf "TV/Andromeda/Season 1" However: root@Storage:/boot/logs# ls /mnt/disk4/TV/Andromeda/Season\ 1/ Andromeda\ -\ 01x01\ -\ Under\ the\ Night\ (1).avi Andromeda\ -\ 01x12\ -\ The\ Mathematics\ of\ Tears.avi Andromeda\ -\ 01x02\ -\ An\ Affirming\ Flame\ (2).avi Andromeda\ -\ 01x13\ -\ Music\ of\ a\ Distant\ Drum.avi Andromeda\ -\ 01x03\ -\ To\ Loose\ the\ Fateful\ Lightning.avi Andromeda\ -\ 01x14\ -\ Harper\ 2.0.avi Andromeda\ -\ 01x04\ -\ D\ Minus\ Zero.avi Andromeda\ -\ 01x15\ -\ Forced\ Perspective.avi Andromeda\ -\ 01x05\ -\ Double\ Helix.avi Andromeda\ -\ 01x16\ -\ The\ Sum\ of\ Its\ Parts.avi Andromeda\ -\ 01x06\ -\ Angel\ Dark,\ Demon\ Bright.avi Andromeda\ -\ 01x17\ -\ Fear\ and\ Loathing\ in\ the\ Milky\ Way.avi Andromeda\ -\ 01x07\ -\ The\ Ties\ That\ Blind.avi Andromeda\ -\ 01x18\ -\ The\ Devil\ Take\ the\ Hindmost.avi Andromeda\ -\ 01x08\ -\ The\ Banks\ of\ the\ Lethe.avi Andromeda\ -\ 01x19\ -\ The\ Honey\ Offering.avi Andromeda\ -\ 01x09\ -\ A\ Rose\ in\ the\ Ashes.avi Andromeda\ -\ 01x20\ -\ Star-Crossed.avi Andromeda\ -\ 01x10\ -\ All\ Great\ Neptune's\ Ocean.avi Andromeda\ -\ 01x21\ -\ It\ Makes\ a\ Lovely\ Light.avi Andromeda\ -\ 01x11\ -\ The\ Pearls\ that\ Were\ His\ Eyes.avi Andromeda\ -\ 01x22\ -\ Its\ Hour\ Come\ 'Round\ at\ Last\ (1).avi

Running another test, I'll post results if the files are still in the old directory.

Just had this happen to me, Gathered 12 Monkies and had to manually remove the directories on disk7 and 8. Are you changing working directory to the src: drive? Or using the full path to actually remove the directories? I: 2017/08/18 12:20:14 core.go:775: Running Move operation ... I: 2017/08/18 12:20:14 core.go:905: Command Started: (src: /mnt/disk7) rsync -avPRX "TV/12 Monkeys/Season 1" "/mnt/disk1/" I: 2017/08/18 12:27:02 core.go:987: Command Finished I: 2017/08/18 12:27:02 core.go:993: Current progress: 6.14% done ~ 1h44m2s left (53.75 MB/s) I: 2017/08/18 12:27:02 core.go:1005: Removing: rm -rf "TV/12 Monkeys/Season 1" I: 2017/08/18 12:27:02 core.go:905: Command Started: (src: /mnt/disk8) rsync -avPRX "TV/12 Monkeys/Season 2" "/mnt/disk1/" I: 2017/08/18 12:29:36 core.go:987: Command Finished I: 2017/08/18 12:29:36 core.go:993: Current progress: 8.86% done ~ 1h36m27s left (56.29 MB/s) I: 2017/08/18 12:29:36 core.go:1005: Removing: rm -rf "TV/12 Monkeys/Season 2" I: 2017/08/18 12:29:36 core.go:1092: unBALANCE - MOVE operation completed Started: Aug 18, 2017 12:20:14 Ended: Aug 18, 2017 12:29:36 Elapsed: 9m22.689s Move operation has finished Transferred 33.21 GB at ~ 56.29 MB/s

Might not help, but I got sick of cache limitations when I was doing major updates (Upgrading a season of a big show to Bluray when released etc) so I finally just bit the bullet and used an old 240G SSD as an unassigned device for NZB downloading and an old 4T spinner to host my torrents. It was just less painful than making the other choice of having a SSD cache with enough room (Large $$$ commitment) or a large spinner that is slow. Obviously, I had the spare SATA ports to make this work, but I've found it's MUCH more stable...now my NZB downloads don't impact my production array even if I get a set of Remux-1080p downloads that don't post-process properly. I don't have to spend $$$ on large SSD space for torrents that would see no benefit from them. Obviously the solution depends on situation, but think of it more like finding the trade-offs that work for you rather than trying to stick to one method of operation...just my recommendation.

My understanding is that the dockers are built once a week from the current check-in of the branch they are following. Never update the app inside a docker, it leads to all sorts of issues

One other note, check the actual directory mount in the Docker, when I checked, the configuration was fine for /movies, however within the docker /movies didn't exist. It looks like if Radarr can't find the "root" directory, it just uses "localdir" to save the files. So it could be the list thing, or you might need to docker exec into it and see if /movies is properly mounted. If not, you have to force the template to update. I changed movies to another location, then back, and it started working again.

UPDATE3: For those using lists, this is a key bug: https://github.com/Radarr/Radarr/issues/1711 I added a list last week and nomater what happens it will not save the "Path" for it, resulting in the webhome of Radarr being used...which is in the docker container. Perhaps I'm the only one here running into this, but I thought Id post just in case.

So I got back from my trip, and it looks like Radarr is pulling the finished files into /opt/radar within the docker when it finds them completed in the download client.. The paths look right, let me try re-installing the docker as a hammer. UPDATE: Found it, for some reason the /movies share wasn't being mounted. It was in the config so it took me logging into the docker and doing 'df -h' to see that it was missing. In the absence of this, it seems radarr just copies the file to the webroot. I tried removing/reinstalling the docker, that didn't work. I had to end up removing the /movies definition from the template and re-adding it. UPDATA2: No dice, still moving the files into freaking /opt/radarr

I just got locked out of my openvpn-as docker (So no access as I'm on the road) due to docker suddenly filling the docker.img. So I don't think this is just you, but I can't confirm until Friday :(. The reason I suspect radarr is it had 4 big files waiting to import with the error "Not enough free space" and when I tried to manually import one, that's when my image whent over the top and (I guess) locked up docker.

I have the update running weekly, I believe that it was the prior maintainers version, so was not getting updated. Everything else is up to date, just hadn't needed this one in years so never caught the change.

Was just working on that when I did a last pass to "Check for stupid". Unfortunatly for me, I found where I was stupid. I had the old plugin installed (Last updated in 2015!). Uninstalled, added the new version and life is good. Sorry about the miss-fire!

Having the same issue, with the same SSD (Evo 840). Can't get the name to stick for the life of me, even tried the trick of adding a line to the .cfg file to force it.