trurl

Is there no disk currently assigned as disk4?

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

Marvell according to that Amazon link

Looks like icydock has separate SATA connections, so the controller for those disks are also on motherboard or else a controller card plugged in to the motherboard. I did notice a Marvell controller in your diagnostics, they are known to cause problems for some time, though they might work if you disable IOMMU (VT-D) in your BIOS.

Disk not reporting SMART. Check all connections, power and SATA, both ends, including splitters. Why is your syslog full of failed login attempts? Are you sharing your network with hackers?

Best to use the support thread for the specific container for help on that.

Looks like the missing disks aren't connected. Are they on the same controller or same power cable?

prefer is the only setting that will move them to cache, but they can't be moved while the files are open, so you have to go to Settings - Docker and disable then run mover before enabling Docker again That only controls how it is accessed over the network, has nothing to do with dockers. You should delete them.

Where exactly are you seeing this button? Doesn't seem like anything to do with Unraid. Post a screenshot.

🖖

The disk has to be rebuilt to enable it again since it is out-of-sync with parity. Safest approach is to replace and keep the original in case of problems, but if we decide the disk is OK it is also possible to rebuild to the same disk if you don't have or don't want to buy another. For WD Reds you should also set it to monitor attributes 1 and 200. Click on the disk to get to its settings and add those Custom attributes. Looks like it recently passed extended SMART test, but it is showing those attributes non-zero, and syslog is showing IDNF and UNC errors. Run another extended test.

Maybe flash problems? If the templates for your installed containers can't be read from flash then those containers will still exist but they can't be worked with in the webUI. Go to the Docker page and move the slider at upper right from Basic to Advanced. Do you see any orphan containers in the list?

Your appdata and system shares both have files on the array.

Shouldn't cause this particular issue, but why is your system share on the array?

No, but the fact that the checks were getting different sectors is what made me suspect RAM. You might try again after checking all connections. Then controller would be next suspect I think. Tell us more about your hardware. Very difficult for us to support a version of Unraid we haven't seen in years. And latest version has a lot more to help us troubleshoot. When you get stable again you should upgrade.

Assuming you have parity you are going to rebuild the replacement so no need to restore.

Do you mean unassigned?

@SpencerJ

Make a new backup whenever you make any important changes in the webUI. Go to Main - Boot Device - Flash - Flash Backup to download a zipped backup of flash. The CA Backup plugin will also let you schedule backup of appdata, libvirt, and flash. The OS doesn't actually run from the flash drive. The flash drive just contains the archives of the OS. These archives don't change except for upgrades, and are unpacked fresh at each boot into RAM. The OS runs completely in RAM. Settings you make in the webUI are stored on flash so they can be reapplied at boot. Think of it as firmware except easier to work with and unbrickable.

post new diagnostics

The upgrade wiki shows how to test that belief

Split level is really about keeping things together. So a season doesn't get split. It overrides other settings like allocation method that might cause Unraid to choose a different disk than where episodes for the season are already.

0 0 is root user and root group 99 100 is nobody user and users group. This is what you need to access files from another computer on the network.