trurl

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

You would use Unassigned Devices to mount the remote shares and then include them in the mappings.

Do you know which plex docker you were running? Some from that long ago time are deprecated now, but you may be able to keep the library when you migrate to a new plex docker. The "official" plex docker has no support thread on this forum so if you decide to use it you will have to go to the plex forums. Linuxserver.io (the one I use) and binhex plex dockers are often used these days. See here about migrating to another plex docker:

👍

Also that /boot/unmenu/uu line should be removed.

Is that the only thing you updated? You didn't update Unraid itself so it is no longer running the NVidia build did you?

That is how you have mover scheduled. Mover moves cache-yes shares from cache to array and moves cache-prefer shares from array to cache. But unless something else is putting files in a cache-yes or cache-prefer share, then once the files have been successfully moved there is nothing else for mover to do the next time it runs.

I do see one share with that setting. No way to know from diagnostics if that is the only share you typically write to or not.

That is so old I have to wonder how you had plex installed. Was it even a docker? Was Tools - Diagnostics even available then? If so post them. Probably the best idea is going to be a clean install, keeping only your disks assignments (config/super.dat) and the license .key (config/*.key). Study the Upgrade wiki linked below and come back with more information about your current setup and any questions. https://wiki.unraid.net/Upgrading_to_UnRAID_v6

Hello Advanced Member 😉 The usual advice is to set the Minimum for each user share to larger than the largest file you expect to write to the share. Unraid has no way to know in advance how large a file will become when it chooses a disk for the file. If a disk has less than Minimum, it will choose another disk. Note that doesn't mean the space will not be used. Here are some examples: A share has 10G Minimum, a disk has 11G free. The disk can be chosen. You write a 9G file to the disk. It now has 2G free, which is less than Minimum, so the disk won't be chosen again. A share has 10G Minimum, a disk has 11G free. The disk can be chosen. You write a 12G file. The write fails when the disk runs out of space.

My guess is overfilling your disks is probably what is corrupting things. Quit writing to your server until you get more capacity, and quit caching so much. Most of your shares have no Minimum Free

already answered and only that port. Do you know how to do port forwarding on your router?

Why have you allocated 50G to docker image? Have you had problems filling it? 20G should be more than enough and when I see someone with a docker image larger I suspect they have something misconfigured with their dockers.

You must be overlooking something or left something out in your description. Something is writing new files to the server, or possibly something (not mover) is moving files from one user share to another or possibly one disk to another. But mover can't be the only thing going on here because once it has successfully moved files they are in their final locations according to the user share settings. And mover is the only thing builtin that moves files, so some addon (docker or plugin) would need to be involved somehow, or some user is involved in writing or moving files on the server.

no need and would be pointless Report back when rebuild completes or if it looks like it is having problems and post new diagnostics.

Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

Settings - Docker, disable and delete image. Then enable will recreate docker image.

Did you check connections as I suggested?

You're having problems connecting on multiple disks. Check all connections, both ends, power and SATA, including any power splitters. Reseat controller card if that applies.

The COMPLETE Diagnostics are better, preferably before rebooting. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post. Since you have a disabled disk, it didn't really do a parity check, it just did a read check. The posted link also tells you how to rebuild to the same disk, and the SMART you posted looks OK. You should rebuild parity since it is invalid now anyway.

Do you mean your trial has already expired after one day? That suggests an issue with the time on your server. Try booting from another USB port, preferably USB2.

For some reason your diagnostics aren't there. Try posting again.

The user name for the console and webUI is 'root'. Unless you have set a password, leave the password blank.

memtest is on the boot menu and must be started and run by itself.

Have you done memtest?