Then I suspect some HBA issue, still worth to try the beta, if the normal update isn't working you install it manually, download the zip:

https://s3.amazonaws.com/dnld.lime-technology.com/next/unRAIDServer-6.9.0-beta25-x86_64.zip

Then extract it and copy all the bz* files to the flash drive overwriting existing ones, then reboot.

 

 

LSI LOGIC LSI00301 no luck. Not a single drive is recognized with unRAID

Well, that problem vanishes changing the SAS cable. So far so good. A bit slow but I am testing reliability first.

unraid-diagnostics-20200913-1125.zip

 

Well well, or better unwell. 2 Copy jobs and the system dies. No usable errors on client side. I just don't get it.

Wait for the parity sync to finish, trying to use the array while it's not done will result in very bad performance.

OK, Bad performance I expected. But disconnects? I'll wait and test later. Thank you for your advice.

 

But later how often do you check parity? It can't be that I can't use unRAID for 3 Days everytime parity is checking.

2 minutes ago, Snuups said:

But later how often do you check parity?

We usually recommend once a month.

 

2 minutes ago, Snuups said:

It can't be that I can't use unRAID for 3 Days everytime parity is checking.

Your parity devices are still invalid, Unraid is doing a parity sync, not a check, only after parity is valid you can do a check, if you cancel/shutdown the array before the sync is done it will start over from the beginning next time array is started.

 

Ah! I get it. Good to know. Thank you.

26 minutes ago, Snuups said:

It can't be that I can't use unRAID for 3 Days everytime parity is checking.

You can use the Parity Tuning Plugin to offload the parity check to idle hours.   It means elapsed time goes up but the impact on daily usage goes down.   Since a parity check tends to be a relatively rare event as it is basically a confidence check this normally does not matter.

I did that. Works great! Thank you.