I am running a multi terabit SSD for my cache.  According to the guides it says when the cache fills the data writes direct onto the array.  Well, the array was in the middle of a move and I had data coming in from two sources and very large files.  My diagnostic logs look like a blood bath.  I have a SATA onboard controller that supports 6 drives.  On that I had the parity plus cache and also a spare SSD that is in the array.  There are also 8 drives on a SAS to SATA PCIe 8x controller.  It has 12 hours to go on a read check and I would assume decisions would need to come after that as to replacing what hardware.  I had two Toshiba 4tb 128 meg of cache drives what are in the same serial number range that were side by side on ports on the motherboard that and those were the failing drives this time.  Any drive coming out of unraid with that failure has never recovered when placed on other controllers.

 

Earlier in the day I attempted to mount a multi-terabit SSD and that all failed.  You will see that goofing around in the logs as well.

gumby-diagnostics-20211225-2120.zip

According to the diagnostics, both parity drives, the cache drive and disk9 have dropped offline.    Do they have anything in common (power, disk controller, etc) that might have affected them all at the same time?

thank you, yes, that is the motherboard controller... in it's entirety.

I moved the parity to a third controller.  Cache seems to be working so I left it on the motherboard.  Now I need to learn how to get the parity un disabled and working on it's new controller.

Dec 25 18:03:17 Gumby kernel: ahci 0000:02:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000e address=0xa1bc0000 flags=0x0050]

 

Problem with the onboard SATA controller, quite common with some Ryzen boards, looks for a BIOS update or avoid using it.

thank you so much!  I will do that.

There was a new BIOS that was several months newer.  My total bandwidth across all three controllers well over tripped as result of the update.  So, something was obviously going wrong with the July last year version of BIOS.