trurl

Are these SAS disks?

You should configure each of your WD RED disks to monitor SMART attributes 1 and 200. That one doesn't look good.

Wow, 17 posts before anyone asks for Diagnostics. Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

You have to rebuild it, or you have to New Config without it and rebuild parity instead.

Disk1 is completely full and probably split level for that share is forcing the files to go to disk1.

HACKED!!! Dec 30 09:05:20 SERVER nginx: 2020/12/30 09:05:20 [error] 8506#8506: *8967102 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 178.128.163.10, server: , request: "GET /system_api.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "107.179.228.5:8006" ... Jan 20 07:26:44 SERVER nginx: 2021/01/20 07:26:44 [error] 8506#8506: *12742830 open() "/usr/local/emhttp/c/version.js" failed (2: No such file or directory), client: 167.99.241.151, server: , request: "GET /c/version.js HTTP/1.1", host: "107.179.228.5:8006" ... Jan 27 12:34:37 SERVER nginx: 2021/01/27 12:34:37 [error] 8506#8506: *13851431 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 64.227.97.101, server: , request: "GET /system_api.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "107.179.228.5:8006" ... https://www.abuseipdb.com/check/178.128.163.10 UK https://www.abuseipdb.com/check/167.99.241.151 Germany https://www.abuseipdb.com/check/64.227.97.101 USA Also looks like you have a problem with cache disk. Feb 4 09:03:08 SERVER kernel: sd 1:0:5:0: [sdg] tag#537 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Feb 4 09:03:08 SERVER kernel: sd 1:0:5:0: [sdg] tag#537 Sense Key : 0x5 [current] Feb 4 09:03:08 SERVER kernel: sd 1:0:5:0: [sdg] tag#537 ASC=0x21 ASCQ=0x0 Feb 4 09:03:08 SERVER kernel: sd 1:0:5:0: [sdg] tag#537 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Feb 4 09:03:08 SERVER kernel: print_req_error: critical target error, dev sdg, sector 1953277894 Feb 4 09:03:08 SERVER kernel: BTRFS warning (device sdg1): failed to trim 1 device(s), last error -121

Not sure I understand the question. Each NAS has its own IP address, their ports won't conflict whatever they are since they are different IPs. Now for your diagnostics. Why do you have 50G docker.img? Have you had problems filling it? 20G should be more than enough, making it larger won't fix anything it will just make it take longer to fill. Your appdata, domains, and system shares are all on cache as they should be so that is good. The other shares you have with files on cache are set cache-yes, so those will be moved to the array when mover runs. However, mover can't move open files, and it won't move duplicates. Are you saying that mover isn't moving files as you expect? Or are you just saying that you are writing so much that you fill up cache?

Which user share(s) are involved?

You can go directly to the correct support thread for any of your dockers by clicking on its icon and selecting Support.

You can go directly to the correct support thread for any of your dockers by clicking on its icon and selecting Support

Do you allow access to your server from the internet? Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread.

No point in adding a formatted disk to the array. You must let Unraid format the disk after adding it to the array. If you add a disk to a new data slot in an array that already has valid parity, Unraid will clear it so parity remains valid. Thus, format before adding is pointless. If instead you use the disk to replace another assigned disk, it will be completely overwritten by rebuild. Thus, format before using as a replacement is pointless. And if you get Unraid to let you use a formatted disk in the array by doing New Config, you have to rebuild parity. Sorry to go sort of off-topic but misunderstanding "format", though common, can cause data loss. Many times we have seen people format an array disk that has data on it just because it is unmountable and needs filesystem repair. You can't recover a formatted disk from parity. Now, back to the show.

Looks like only appdata hasn't moved completely. Mover won't move open files but since you have docker disabled that shouldn't be the problem. And mover won't move duplicates, so if you already had some appdata files not on cache that might explain it. Go to Settings - Scheduler and enable Mover logging then try again with Mover and post new diagnostics so we can see what it is doing. You won't be enabling docker again until you have completed replacing cache and moving things back as explained in that wiki.

I have plex and 17 other dockers and they take less than half of 20G docker.img. All that plex stuff is in appdata and the plex templates have it that way by default. 20G should be plenty. Making it larger won't fix anything it will only make it take longer to fill. The usual cause of filling docker.img is an application writing to a path that isn't mapped. Linux is case-sensitive.

And the few plugins you have I don't think use that so I don't know why it would still be running.

Your configuration is completely contained in the config folder on the boot flash. If you setup another flash without your old config, then you are starting from scratch with no disks assigned. If you copy the old config then you will have exactly the same configuration as before. If you copy part of the old config, then you will have those parts of your old config and others would be default. This wiki gives some idea of how that would work: https://wiki.unraid.net/Upgrading_to_UnRAID_v6#Files_on_flash_drive In any case, your license .key file will not work with another flash so your license will have to be transferred.

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

This thread is pretty old and OP hasn't visited the forum for nearly that long. Probably a different version of Unraid back then, and you don't say what version you have. If you have adblocker or anything else that might interfere, whitelist your server. What browser? Does it occur on other browsers?

Any path that isn't mapped is inside docker.img

I will probably split your post and its replies into its own thread since OP might not be finished with this.

So have you solved your problem?

Go to Tools-Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread

Do not mix user shares and disk shares when moving or copying files. Linux doesn't know they are different views of the same files so could try to overwrite what it is trying to read if the source and destination paths work out that way.