JorgeB

Yes, I was referring to used and free, though one could argue that total is also correct since it's the total pool size before accounting for parity. I, and I think most, care about used space and especially about free space, I have five raid5 pools, four of them use different size devices, so it would be pain if I had to account for parity size every time I look at free space. Thanks for changing, hopefully this will be the last time.

Those should give you decent speeds.

Unraid doesn't support SAS multipath.

Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

https://unraid.net/blog/top-support-and-forum-questions-answered

You also have the RAM overclocked, max speed for your config is 1866Mhz, it's at 3000Mhz.

Parity reached 63C in this latest cycle (and 71C in the past), that's way too hot.

Yep.

Please post the diagnostics: Tools -> Diagnostics

Please post the diagnostics: Tools -> Diagnostics

Syslog is spammed with errors and can't see the beginning of the problem, please reboot and post new diags once the errors begin.

Depends mostly on the SSDs used, cheap TLC or QLC models can have slower sustained writes than disks, also make sure to enable turbo write since it also helps with SSDs.

See if you can get the diags on the console by typing "diagnostics", then attach them here.

There as a read failure, i.e., bad sectors, you should replace it.

Look on the flash driver config\plugins folder for dynamix.plg, if that file exists delete it and reboot.

NVMe devices don't have SMART tests. Please post the diagnostics: Tools -> Diagnostics

No, balance is what "removes" the member pool. LT most likely did that because some times a balance leaves some old profile chunks unconverted, note that the "soft" balance will only balance those chunks, if there are any, it won't re-balance what is already balanced.

You can try running the server in safe mode without dockers/VMs for a few days, if it crashes like that it's likely a hardware problem, if it doesn't start turning the services on one by one.

Should be, again if working correctly, also did you try Unraid stable? Just in case there's some compatibility issue with the beta.

Correct, that's the one in use.

Yes

That is also a problem, but the UUID can only be duplicate with another mounted disk, for example if that disk was once part of the array and then upgraded, you can change the UUID for that disk in the UD settings.

Also both disabled disks are on the same Marvell controller, those are not recommended and possibly the reason the disks got disabled, but grab diags before rebooting if it happens again so we can confirm.

With dual parity you could rebuild both at the same time.

That's not the problem, looks like an UD issue, you should post on the plugin support thread: Oct 4 16:01:08 Tower unassigned.devices: Successfully mounted '/dev/sdaa2' on '/mnt/disks/'. Oct 4 16:01:08 Tower unassigned.devices: Issue spin down timer for device '/dev/sdaa'. ### [PREVIOUS LINE REPEATED 1 TIMES] ### Oct 4 16:04:20 Tower unassigned.devices: Unmounting disk ''... Oct 4 16:04:20 Tower unassigned.devices: Cannot unmount '/dev/sdaa2'. UD did not mount the device. Oct 4 16:04:20 Tower unassigned.devices: Disk '' could not be unmounted. Oct 4 16:04:31 Tower unassigned.devices: Issue spin down timer for device '/dev/sdaa'. Oct 4 16:04:32 Tower unassigned.devices: Unmounting disk ''... Oct 4 16:04:32 Tower unassigned.devices: Cannot unmount '/dev/sdaa2'. UD did not mount the device. Oct 4 16:04:32 Tower unassigned.devices: Disk '' could not be unmounted.