lionelhutz

I thought that went away, but yes it's due to the way files are handled on the filesystem which is a subsystem thing way below the split level ability to control. I've seen it to when moving files.

The Docker file is a BTRFS disk image. Those errors are showing it has issues. You probably have to re-build it. It's fairly simple, stop Docker, delete the image file, start Docker and then pick the my-*** templates to re-install the Dockers.

The parity would only spin when writing the file to the array drive, not while seeding it. You don't need parity spinning to read from an array drive. Move the completed ones to the a cached array share and also let sonarr and couch move to the cache in a media share. Then, the mover puts the whole mess of seeding and final media to the array all at the same time when it runs.

Yes, doing so will not delete anything outside of the Docker image. In other words, it won't delete any files on the cache drive.

If you cache drive pool isn't showing any errors then the errors are in the virtual docker filesystem. You can try re-creating it again until it starts to behave. The docker image will still corrupt on a XFS drive. My cache is currently formatted XFS and my docker image currently is corrupt with 4 errors. Fortunately, the dockers are all still working so I haven't bothered to fix it.

Presently, the parity can't be used to do anything with corruption as reported by BTRFS. I'm doubtful anything will change in the future but I could be wrong. Unless you are expecting to be writing to multiple drives at the same time I wouldn't use any special hardware for the parity drive. I would just use a drive at least as good as your data drives. All drives need to be spinning to create the initial parity data, but not to write data to a single disk once the parity is in place.

What you saw was a normal limitation of the Windows networking connecting to the server. Happens to everyone unless their player buffers enough video length to play through the pause.

Which docker? Either click on the docker name or the icon and select Edit. Then, in the grey Update Container bar on the right side there is an Advanced View slider. Move it to the right and a section called Advanced Variables will show up. The user and password may be listed there. Also, look in the text description of the docker for them.

HeidiSQL should work too. Otherwise, yes you would have to command line it.

I don't use NZBget but in SAB you just use tv and movies in the categories, not /tv or /movies, to add the category directories inside the downloads/complete directory. I suspect that forward slash is putting the directory to the root of the Docker instead of as a subdirectory of the downloads directory.

Have you got the option ApendCategoryDir set to yes? In the movies and TV setup the destination directories /tv and /movies only exists in the docker. Those directories are not "mapped" to the server.

You don't even need the Docker image, all you really need is the app data and the same USB stick. When you setup Docker and add containers again, the template drop-down will have my-xxx listed where xxx are the Dockers you have previously installed. You can just pick each one and install it. As for the array. When you transfer the same disks to the new hardware, the disks get picked-up again and re-assigned like they were. It's a good idea to take a screen image just in case, but the array should just keep working.

If you use a cache drive, any files you write to the cache are unprotected until the mover runs. If you run the mover and still see it then check the cache drive contents.

One of the selling points of BTRFS is that the filesystem stores parity information, so it can detect data errors. This was being touted as giving the ability to correct data errors by LimeTech, but the parity can only be used to detect data errors on a single disk, not correct them. I Pointed that out to Jon in the fall when he was posting how the correcting ability of BTRFS was such an advantage on a BTFRS filesystem. You need an array to have the ability to correct data errors. Linus is running a BTRFS array so even if his array has a small corruption issue running scrub should be able to fix it. There is also parity on the metadata and it can be used to correct a metadata issue on a single drive. I found BTRFS simply didn't work for me. The main place I saw issues was with my MariaDB (or MySQL) database which would become corrupted within a few days. This is why I say try it and beat on the drive with a bunch of reading and writing and then run scrub or check the log and see if it's having issues. If it works, then you're good. Since I had issues, I've been running the database on XFS for almost a year without any random corruption, so I don't believe I had a hardware issue causing random corruption because it wouldn't just go away with a different filesystem. When I do the next upgrade, I will likely buy a couple of SSD's and try them in a BTRFS array. There are advantages to the filesystem if it will work.

I could demonstrate those speeds, and even higher, on 2-3G files. But, it doesn't have much to do with the speed of my drives. It's due to the 16G of memory in my server.

Not possible. Snapshots are a part of the BTRFS filesystem, so they must be created on the same BTRFS drive or array of BTRFS drives. I really don't understand the rest of what you posted, but it doesn't seem to be related to this request. It seems you want to be able to tell the mover to move from one specific disk to another specific disk, which isn't what the mover does. This request is to move from say disk4 to the same shares on the other disks to empty disk4 so it can be removed, instead of the cache disk into the array shares.

I'd try it on an array. You can add the second drive at any time. You can only correct certain errors with an array of BTRFS drives, likely the errors you seeing. Even LimeTech didn't know this until I pointed it out a little while ago. I never had much luck with BTRFS on a single cache drive. I get errors in the docker virtual BTRFS image too, and they can't be corrected either.

unRAID won't just swap the drive assignments, but if you're worried it will then just keeping the parity drive out of the system would be useless.

The connections should not matter. Once you set the new motherboard to boot the USB stick it should recognize the drives and start the array as if nothing changed.

unRAID will still recognize the drives and current array even after hardware changes assuming you have a valid configuration. No need to start over. Typically, just plug the USB into the new server with the same drives and it will boot and work just like nothing was changed.

A feature of unMENU was the ability to add your own info for the hard drives, like date of purchase and where for example. It was handy to keep track of the drive history.

Split level 3 would only be better if you want the files for a season to be spread out over multiple drives. I would leave it at 2. There is no explanation for what you found in the info you have provided.

You probably did something wrong copying one time if that is the only case. Copy the files disk2 to disk1 and then delete the extra directories on disk2.

After first adding the my movies share the library scan would just hang every time. The docker doesn't hold all the information and images so of course it's scraping data from outside sources so this will take time to complete on a first scan where the images don't exist. But, as I already noted twice now, in my case the first scan of the library would hang every time so it was nothing to do with bandwidth. It simply was hanging on trying to identify a movie or movies.

We've run USB 17-18' at work and it's been fine. I'd try it first. You could always put a powered USB hub just below the floor to act like a repeater with another USB hub at the desk. They're pretty cheap. DVI can also carry analog signals, basically the equivalent of VGA but I highly doubt that your monitors are running on analog. So, you can probably just convert to a HDMI cable as mentioned to make the routing easier. You can assign 2 video cards to the same VM.