remotevisitor

Have you read the docker section in the official Unraid documentation at https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications Does it provide the information you need?

Yes it is ok to move file between 2 disk shares. However you must never copy file between a disk share and a user share ( eg from Disk1/Movie to Share/Movie in your example) or vice versa; if you do this you will end up with all the copied files being zero length. It is for this reason that disk shares are not shared by default to help prevent users doing this.

Actually this is a case when the deprecated /mnt/user0 can still be useful. As you mention if you have a file on the cache drive is in another share and you move it to your /mnt/user/test share, Unraid counter-intuitively renames it and leaves it on the cache drive. It can do this because the cache drive is included in the share in /mnt/user/test. However, if you instead move it to your /mnt/user0/test share, it will correctly move the file into the array, rather than just renaming it. It must do this because the cache drive is not included in your /mnt/user0/test share.

Although you have the test share set to Array Only, have you confirmed that the cache disk does not already include files/folders for that share? That setting will only ensure *new* files and folders will be created in the array. I will not prevent existing files and folders already on the cache drive for that share from appearing in the share.

And if the files are not in the config directory, then no password has yet been set.

I think the instructions in the manual that you have quoted are slightly wrong (should not have "boot" in the name) as the files to delete are: config/shadow config/smbpasswd The names as quoted with the "boot" in the name is what they would be when the flash drive is mounted within Unraid itself.

Incorrect. It is as itimpi said, any storage device (excluding the boot USB drive) connected when the array is started count towards the allowed limi (whether they are in the data array or not). From the Unraid manual … What is an attached storage device? Attached storage devices refer to the total number of storage devices you are allowed to have connected to the server before starting the array, not counting the USB Flash boot device. There are no other limitations in the software based on the license type. Non-storage devices such as GPUs do not count against the license tier limits.

Read the last sub-section on https://docs.unraid.net/unraid-os/manual/shares/disk-shares/

For minimum free space % issue see

One common mistake which prevents a disk being unmounted ishaving a console open with the current directory on the disk that won’t unmount. Changing directory to somewhere else then allows the unmount to proceed. I’ve been guilty of this mistake in the past.

I’m on 6.12.2 with no problems. However, as no-one else has come up with any suggestions, it may be worth trying to roll back to 6.11.x if it is easy for you to do, if only to show whether or not the problem is specific to the 6.12 release. However from your original description I think you suggested that the problems were occurring even before you updated to 6.12, in which case there would be little point rolling back. I know how frustrated I would be if it was failing for no apparent reason on my system. The only other thing I could suggest is maybe try setting it up with a small library with only a few items in it, in case it is something in the media library causing it to fail (although I cannot really see how this could cause the whole docker to fail), if only to rule this out as the cause.

Not seeing this problem with the docker on my system. Does it run if you manually start it (is the problem only with autostart). What version of Unraid are you running? Have you recently upgraded to the latest 6.12 version?

Is the current directory for your shell in a user share? If so this would prevent the user shares from being stopped.

You should probably configure "Notifications" to at least send your emails if something important needs your attention: Settings -> Notification Settings -> SMTP settings

You have a conflict between the standard Parity Check setting "Accumulation duration" which is set to 14 hours and the Parity Check Tuning setting "Increment Pause" setting to 00:30 (which is causing your parity check to pause 30 minutes after midnight) I suggest you set the Parity Check setting "Cumulative parity check" to "No" and then set the Parity Check Tuning setting "Increment pause" to the time you want it to pause (11:30). This means all the pausing/resuming is handled only by the Parity Check Tuning plugin. You should also change the Parity Check setting "Day of the week" to a specific day …. The current setting will restart the parity check every day of the 1 week of the selected month. How do I know this? Because I made the same mistake when I recently changed from monthly to 2 monthly and the parity check was making no progress each night. I had the luxury of being to able chat with my brother (who is the author of the Parity Check Tuning plugin) to work out what was going wrong.