trurl

If you put it in a folder named "extra" on flash it will be automatically re-installed on boot, no script required. That method isn't discussed a lot these days with all the plugins and dockers we have for additional functionality, but that is how it was done on older versions of Unraid. Any slackware compatible package (.txz .tgz) in the "extra" folder on the flash drive is installed with the installpkg command when Unraid boots. Use this technique sparingly. It may not be supported and it is easy to get yourself in trouble by installing packages that conflict with other packages installed by your plugins.

You had it in your previous post.

No. He's asking what it looks like if you uninstall the Unassigned Devices plugin. Without the plugin the Unraid webUI will still list the Unassigned Devices, but you can't mount them or otherwise use them. That functionality comes from the plugin.

Maybe obvious, but are you building parity during any of this testing?

Personally I wouldn't put spaces in a user share name just to avoid these sorts of problems.

Try clearing your browser cache and if you have additional browsers open close them. If it persists go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.

Yes. And one of you is writing and the other isn't. So it's not clear that you are experiencing the same thing. Other things to consider might be the Cache-Dirs plugin. Or anything else that might scan your disks such as plex. You could try to eliminate these factors to see if it changes. Not happening to me either even without safe mode.

You might try turning on turbo write and then turning it back off.

Are you using the CA Auto Turbo Write plugin?

Are you using Turbo Write? Reading all disks to update parity is the way Turbo Write works.

Any idea why your rootfs is so small? Here is my df for comparison. Filesystem 1K-blocks Used Available Use% Mounted on rootfs 7983956 601824 7382132 8% / tmpfs 32768 540 32228 2% /run devtmpfs 8099316 0 8099316 0% /dev tmpfs 8150308 0 8150308 0% /dev/shm cgroup_root 8192 0 8192 0% /sys/fs/cgroup tmpfs 131072 352 130720 1% /var/log /dev/sdb1 15625200 1412976 14212224 10% /boot /dev/loop0 8832 8832 0 100% /lib/modules /dev/loop1 6016 6016 0 100% /lib/firmware /dev/md1 5858614812 4563266544 1295348268 78% /mnt/disk1 /dev/md2 5858614812 3323099748 2535515064 57% /mnt/disk2 /dev/md3 5859091740 2690272584 3168819156 46% /mnt/disk3 /dev/md4 5859091740 2405855300 3453236440 42% /mnt/disk4 /dev/md5 3905587740 1865502912 2040084828 48% /mnt/disk5 /dev/sdh1 268617352 73319972 193616492 28% /mnt/cache shfs 27341000844 14847997088 12493003756 55% /mnt/user0 shfs 27609618196 14921317060 12686620248 55% /mnt/user /dev/sda1 488383484 250356216 238027268 52% /mnt/disks/Oyen /dev/loop2 20971520 2486252 16738676 13% /var/lib/docker shm 65536 0 65536 0% /var/lib/docker/containe rs/ce32886c13b7085ae5229ca8d26695317041de10faec7596de678dc99451b579/mounts/shm shm 65536 8 65528 1% /var/lib/docker/containe rs/8001d1d443fcb95a6f3a0ad9f6d5195ea3b5d0f6c24d4cfb93b2ba3db8edca5c/mounts/shm shm 65536 0 65536 0% /var/lib/docker/containe rs/183d9f0e0744b2fff921229f526b5b256b318fd6c179094e101268d3a7054047/mounts/shm shm 65536 0 65536 0% /var/lib/docker/containe rs/c0ffc7f6f24f1a50ecfc93dcfce8aa8dafb10ba2087af41ef80321a0450ee87f/mounts/shm You might try rebooting to see if it goes back to normal

And how do you define best? If you are just trying to get the current split level for files that were written before you applied the split level, you could just move them to cache and let mover take care of it. Since you probably only have enough cache for small batches you would have to move them manually to cache then let mover move them back to the array. Also might be worth noting that high-water allocation will keep things together most of the time without bothering with split level.

It's not useful to not publish a diagnostic.

du -sh /mnt/user0/downloads/nzbget

Those are from the Unassigned Devices plugin. You should report it there.

I and many others have monthly parity check scheduled.

Nobody else has reported this, but you may be the only one who has tried it with the max number of disks in the array.

/boot is where your flash drive is mounted, so /boot/config is the config folder I was talking about. There should be a number of files and folders in there. If there aren't then maybe that is your problem. My guess is your flash drive has dropped offline and is not really mounted anymore. Often this is a problem with the USB port. USB2 is more reliable. You won't be able to work with it from the CLI anyway. I was talking about putting it in your PC to

They are not in Europe. Everything about your configuration is in the config folder on the flash drive. If you make a copy of that config folder, you can prepare the flash as a new install with whichever version and copy your config back to it.

I think the other reports had to do with displaying much larger than true, as in PB instead of TB. Where are your diagnostics?

Or just leave SMB Security to No for Public access (turn on Help will explain this) and turn on the share switch for the drive on the UD page.

That is not your docker run command. First link in the Docker FAQ:

Post your docker run command

Not for me