This morning I woke up and got on unRAID. I clicked on "dockers" and it waited a while, then everything turned white (it's usually black) and then there was an error (that I didn't capture, but that indicated there was a missing file.) I went to "main" and everything was white and took about 5 minutes to show the drives, which I quickly took a screenshot of. Remembering the docker error, I went to /boot and it was completely empty. I tried a "powerdown" from my SSH connection, but it didnt seem to be doing anything. I powered it off and removed the drive, checked it on my desktop and copied all the files over, just in case.

When I plugged it back in, it started up, registered the unclean shutdown, and seemed to be fine, otherwise. It's doing the parity check and it is going at about 5MB/s, which it says will take 13 days. I have no idea what the problem is. Any help anyone could provide would be great. Also, any tips for what to look for in the diagnostics output would be helpful too. Although, I realize that is a pretty general thing and probably amounts to additional Linux experience/education. I think I may move to Arch from Ubunt, which will probably force me to learn a lot more that will be useful.

Thanks for any help anyone is able to give.

zion-diagnostics-20171027-0832.zip

t's doing the parity check and it is going at about 5MB/s, which it says will take 13 days

 

This is because IRQ16 used by the SAS2LP got disable, rebooting will fix it (but it may happen again).

 

 

Ah, interesting. Can you think of a cause for this or something I should change to stop it from happening again? 

Thanks so much for the help. I am going to stop the current parity check and reboot to see if it fixes that. 

Thanks again.

Bios update and/or using the controller in a different slot may help avoiding this in the future, newer/different kernel can also help.

Thanks. I rebooted and it started the parity check around 98 MB/s. I will check for a BIOS update and see if i can figure out a way to move anything around. My slots might be full up in there now. I was just trying to figure out a way to remove a card that had 1 SATA drive connected to it, so that I could replace it with a SAS expander. 

 

I noticed the following:

 16:     904665          0          0          0          0          0          0          0  IR-IO-APIC  16-fasteoi   ehci_hcd:usb1, mvsas

Is that saying that one of the SAS controllers and a USB port are sharing an IRQ? Could that be the (or a) problem? Or...did I completely misunderstand what it is saying?

They are sharing IRQ16 and that by itself is not a problem, but if it keeps getting disable you'll need to try the options above.

Great, thank you. I guess by problem, I was really asking if that could be why unRAID died. I think that the USB it disabled must've been my unRAID drive. When I went to /boot, it was empty, and if it was disabled, I guess that explains why.

Thanks for all the help.