I've had this issue happen a few times now and i'm trying to work out what the exact cause is. The server will work fine for a few weeks and then just die. last time i had this issue, someone did suggest that it might be my sata controller as i'm using a ryzen board. I swapped a few bits around so i'm not sure if that's still the same issue or if something else has gone wrong  tower-diagnostics-20220802-1844.zip

Problems with the onboard SATA controller, quite common with some Ryzen servers, best bet is to use an add-on controller (or a different board).

i'm pretty sure you're the same person that told me it was probably that last time. I guess my theory of some ports being ok was wrong in the end. I'll just have to switch my ssds over to the hba and sacrafice trim support then

4 minutes ago, nmills3 said:

i'm pretty sure you're the same person that told me it was probably that last time

Most likely

 

 

this might be a really stupid question, but when a drive stops working like in this kind of situation. shouldn't unraid failover to using the parity data instead? I know that if you restart an array that's missing a disk it will emulate the contents but shouldn't it also do that "live" if a disk stops working for some reason?

12 hours ago, nmills3 said:

but when a drive stops working like in this kind of situation

It's not one drive, all devices connected to the controller drop offline, you just get one disabled disk because Unraid only disables as many disks as there are parity drives, but obviously the server cannot continue to work correctly. 

ah ok, thanks for the explanation. for some reason when this happens the UI doesn't like to show me any drives offline so it can be a bit hard to understand what's happened but your explanation makes sense

It should stop displaing temps for all dropped drives, that's a clue to which ones dropped, you also won't be able to get SMART attributes for them.