trurl

Do you have any actual symptoms besides the FCP notice? Have you done memtest?

Never try again. We don't want it unzipped and if you post the dozens of separate attachments that you would get from unzipping I would delete them all since nobody would bother to download them separately.

Might be possible to rebuild disk1 from the original parity. Did you write anything to your server during parity rebuild? Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.

first link in the docker FAQ:

By mappings, I assume you mean dockers? Are you mapping them with the slave access mode?

You can go directly to the correct support thread for any of your plugins by going to the Plugins page in the Unraid webUI and selecting its Support Thread link. Similarly, you can go directly to the correct support thread for any of your dockers by clicking on its icon on the Dashboard or Dockers page and selecting Support. Finally, there is also a (?) link to the support thread for any plugin or docker on its listing on the Apps page.

Are you using the Unassigned Devices plugin for this?

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

Post them

Rebuilding to 8TB should only take about a day. Post diagnostics

Bad disks are probably the least common reason for disabling. Please attach your Diagnostics to your NEXT post instead of linking to unknown external sites.

The reason I ask is because there is a Marvell controller showing up in your diagnostics. Is this a separate controller card? Or is it some of the motherboard ports?

Which controller is disk3 and disk4 connected to?

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

You can format while building parity or after. If you format while building parity you can even begin using the disks while parity is building, but of course it will slow things down if you try to do too much.

You have 2 plugins that are no longer in CA.

The above is correct, because the below is not correct. The old drives were empty and the new drives are clear, very different things. An empty drive has a filesystem and its metadata that represents an empty top level folder ready to receive new files and folders. A clear drive has every bit set to zero. A clear drive can be ADDED to an array with valid parity because those zeros have no effect on the parity calculation. A clear drive cannot REPLACE an empty drive (or indeed anything except another clear drive) without either rebuilding parity or rebuilding the clear drive so it becomes an empty drive.

You have tried SAFE mode boot?

Not sure but don't usually see those in syslogs. Shutdown, put flash in PC. While there checkdisk and make a backup of the config folder. Then delete those extra keys in config folder on flash. Put flash in server, preferably USB2 port, and reboot. Then report results. If still problems post new diagnostics.

Sorry, looked at your diagnostics again, and you do have flash problems. Jun 4 03:09:38 Tower shfs: error: get_key_info, 591: Invalid argument (22): get_message: /boot/config/._Plus.key (-3) Jun 4 03:09:38 Tower shfs: error: get_key_info, 591: Invalid argument (22): get_message: /boot/config/._Trial.key (-3) Jun 4 03:09:38 Tower shfs: error: get_key_info, 591: Invalid argument (22): get_message: /boot/config/._Basic.key (-3) You also apparently have 3 different license keys on flash. Which license do you have?

Those last diagnostics you posted did have all log space used, but syslog wasn't very big, so something else is to blame. Looks like you installed everything in NerdPack. Why? You shouldn't install anything you don't need and may not even know what it's for. atop is one likely cause of your problem, but I suggest uninstalling most of NerdPack. Then you will have to reboot to clear log space.

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

Can you ping github.com for example?

You can see the cfg for every user share in the diagnostics, that is why I asked about that share that was filling cache because it was cache-prefer. The usual docker/VM things are in the correct shares according to the diagnostics, but it is possible some docker or something could have open files on that other share, such as seeding torrents.