trurl

Might be useful to have diagnostics also.

Google seems to indicate that the only linux driver available is proprietary so won't be supported by UD.

Nobody else has reported this and it seems extremely unlikely the update would have changed the volume label.

That looks OK. Don't know. Is it having that problem on both the Docker page and the Dashboard?

That comes from the template too. Click Edit then post a screenshot of the Update Container page on Advanced View.

You already asked about that plugin in the correct plugin thread. That (nerd tools) was not the correct plugin thread. Please don't clutter up plugin and docker support threads with random questions about other things. I have split these into the correct plugin thread.

UNRAID has always been the required volume label. It seems unlikely it would have worked with anything else whatever the version.

There are 4 different possible settings for use cache, only 2 of those settings will invoke mover, and only one of them will result in moving files TO cache. Also, mover can't move open files so just setting something to cache-prefer (the one that will move TO cache) may not be enough to get it done. Disable docker service, or at least stop the particular container, then run mover after setting it to cache-prefer. And only 2 of the 4 settings for use cache will result in files staying on cache. See this FAQ for more details about the use cache settings: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#comment-537383

Crossposting has been considered a bad thing on message boards since before the World Wide Web. How can we coordinate our responses to your posts when they are in multiple threads? Let me know if you can't delete them and I will do it for you.

Unraid is not RAID. There is no mirroring in the parity array. Each parity disk must be at least as large as the largest single data disk. You can have one or two parity, but neither contains any of your data. Parity PLUS ALL other disks allows the data for a missing disk to be calculated. This is not really any different than the meaning of parity in other uses. Parity is simply an extra bit that allows a missing bit to be calculated from all the other bits. So, a single parity disk will allow a single missing disk to be calculated no matter how many data disks there are. An additional parity disk allows two missing disks. RAID1 is the mirroring you are thinking of. That is one of the options for the cache pool.

You really should try to get to the bottom of your problem. It is not normal to need to reboot frequently. Many people only reboot when installing a new version of Unraid.

Seems familiar, like on that same page as your post: https://forums.unraid.net/topic/61211-plugin-ca-appdata-backup-restore-v2/?do=findComment&comment=751154

Settings - Docker. Delete and recreate docker image. Use the Previous Apps feature on the Apps page and it will download and reinstall your containers using the same settings they were using before.

Then you should read the first post in this thread.

See Documentation link in first post in this thread. See first link in the Docker FAQ: https://forums.unraid.net/topic/57181-real-docker-faq/

Not clear from your post, are you running this on Unraid?

Post docker run command and diagnostics zip

For example: http://corntab.com/?c=30_23_*_*_1-5

It's your support thread, but I usually discourage users from linking to an external site for this purpose. I agree that we don't want syslogs pasted into the text of a post, but syslog as an attachment to a post is more convenient to create and more convenient to use. And there are a lot of sites someone could use, who knows how safe any particular one might be.

First link in the Docker FAQ: https://forums.unraid.net/topic/57181-real-docker-faq/

I was copying my Unraid data to another Unraid server I had created for backup when it happened to me. I saw that rsync was going in alphabetical folder order when it began to actually write the files, so I just started at the other end moving the empty folders to other disks before it began to write to them.

Not normal, in fact, sounds like your network has degraded to 100mb instead of 1000. Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

Do you know how to do this? Then, looking at the SAB website, it appears you can specify different folders for incomplete and complete downloads: https://sabnzbd.org/wiki/configuration/2.3/folders So, it looks like all the pieces are there for you to try it out for yourself.

I don't use this but I would be surprised if this wasn't fairly easy to accomplish. Map a path to a cache-no share and somewhere in SAB settings you can probably tell it to use that path for unpacking.

That will just take longer to fill. Nothing should be filling docker image. The usual cause is some application writing to a path that is not mapped. Common mistakes are using different lower/upper case when specifying paths, or using a relative instead of absolute path. I haven't found anyone needing more than 20G unless they have something misconfigured, and if you are writing into docker image, no amount may be enough.