trurl

According to those diagnostics, appdata, domains, system shares are all configured to not use cache so will not be moved because there is no Mover action because there is no Secondary

SMART for those Unassigned Devices looks OK, but both disks were logging critical medium errors before they disconnected. So definitely do the extended test on both.

Good news is both emulated disks are mountable so rebuild should be OK after hardware problems are resolved. Both disks disconnected and reconnected as Unassigned Devices. Do the extended tests on the Unassigned Devices.

But it seemed to quit doing that so maybe you fixed whatever was doing that. You will have to reboot to clear the log.

Much of your syslog is errors where something is trying to access a user share that no longer exists. Apr 5 06:24:48 TresCommas smbd[234119]: chdir_current_service: vfs_ChDir(/mnt/user/copyparty) failed: No such file or directory. Current token: uid=99, gid=100, 5 groups: 100 98 3003 3004 3002

On the Docker page, check the uptime of each of your containers and see which have been restarting themselves (short uptime).

What do you get from command line with this? ls -lah /mnt

Post a screenshot of your User Shares page

Start the array in normal (not maintenance) mode and post new diagnostics. Setup Syslog Server.

Are you trying to access a Public, Secure, or Private share?

No data disk can be larger than either parity disk. Assuming you will not be using a new data disk larger than either parity disk, since you have dual parity, you can rebuild 2 disks at the same time, whether parity or data. So you could replace one parity and one data disk at the same time.

Or in multiple pools depending. You can have multiple pools outside the array, each pool can have multiple disks. Multidisk pools must be btrfs or ZFS.

Would probably save a lot of back and forth and guess work if you Attach Diagnostics ZIP to your NEXT post in this thread.

SSDs in the array cannot be trimmed, and can only be written at parity speed. HDDs in array, with or without parity. SSDs in a pool outside the array.

Do you have an attached keyboard and monitor?

32 Reported_Uncorrect is the reason for 👎 . Might be OK for now Click on disk2 to get to its page, then do extended self-test.

Ideally, Docker/VM related shares - appdata, domains, system - would have all files on cache or other pool outside the array, so Docker/VM will perform better, and so array disks can spin down since these files are always open.

Unassigned Devices

Nothing else. No data in array anyway.

If you have to constantly New Config parity isn't doing anything for you anyway.

/usr is in RAM with the rest of OS files so changes there won't persist

You could run Dockers/VMs from the SSD and have additional storage with USB as Unassigned Devices. Or even an array without parity. No parity would mean the array can't be out of sync so nothing would need rebuild. Of course no parity also means nothing can be rebuilt.

USB is the reason it can't identify the drives. The USB interface is adding characters to the serial. And USB is probably the reason for the read errors we were having on disk2 earlier. You will have to New Config everything again. This time, in addition to checking the Parity Valid box, also check the Maintenance mode box. Then start the array. That will get all drives accepted again without altering any of them in any way since they won't be mounted in Maintenance mode. Then you can stop the array, unassign disk1. Then start the array with nothing assigned as disk1. Might as well start in Maintenance mode so no drives will be changed. That will disable disk1 again so we can try rebuild again. We won't be able to see if emulated disk1 is mountable in Maintenance mode, but at this point that would be the least of our concerns. Then stop the array, reassign disk1, start the array to try rebuild again. If there are any errors in the ERRORS column for any drive post new diagnostics. No guarantees anything will be recoverable. You would at least have the added expense of UFS Explorer Standard Edition. Might be simpler to just start over after you get a working setup.