Logged into my server to see that two drives are listed as failed. The Parity 2 disk is fairly new, so I’m doubting that it failed at the same time as the older Disk 1 drive.  I’ve attached a screenshot of the GUI and my diagnostics.

homeserver-diagnostics-20200128-2113.zip

Any idea what is filling your syslog with these?

Jan 28 21:14:25 HomeServer avahi-daemon[8523]: Record [HomeServer.local#011IN#011AAAA fe80::85f:1cff:feb1:cca5 ; ttl=120] not fitting in legacy unicast packet, dropping.
Jan 28 21:14:25 HomeServer avahi-daemon[8523]: Record [HomeServer.local#011IN#011A 10.242.170.2 ; ttl=120] not fitting in legacy unicast packet, dropping.
Jan 28 21:14:25 HomeServer avahi-daemon[8523]: Record [_device-info._tcp.local#011IN#011PTR HomeServer._device-info._tcp.local ; ttl=4500] not fitting in legacy unicast packet, dropping.
Jan 28 21:14:25 HomeServer avahi-daemon[8523]: Record [HomeServer._device-info._tcp.local#011IN#011TXT "model=Xserve" ; ttl=4500] not fitting in legacy unicast packet, dropping.
Jan 28 21:14:25 HomeServer avahi-daemon[8523]: Record [HomeServer._device-info._tcp.local#011IN#011SRV 0 0 0 HomeServer.local ; ttl=120] not fitting in legacy unicast packet, dropping.
Jan 28 21:14:25 HomeServer avahi-daemon[8523]: Record [_sftp-ssh._tcp.local#011IN#011PTR HomeServer._sftp-ssh._tcp.local ; ttl=4500] not fitting in legacy unicast packet, dropping.
Jan 28 21:14:25 HomeServer avahi-daemon[8523]: Record [HomeServer._sftp-ssh._tcp.local#011IN#011TXT  ; ttl=4500] not fitting in legacy unicast packet, dropping.
Jan 28 21:14:25 HomeServer avahi-daemon[8523]: Record [HomeServer._sftp-ssh._tcp.local#011IN#011SRV 0 0 22 HomeServer.local ; ttl=120] not fitting in legacy unicast packet, dropping.
Jan 28 21:14:25 HomeServer avahi-daemon[8523]: Record [_ssh._tcp.local#011IN#011PTR HomeServer._ssh._tcp.local ; ttl=4500] not fitting in legacy unicast packet, dropping.
Jan 28 21:14:25 HomeServer avahi-daemon[8523]: Record [HomeServer._ssh._tcp.local#011IN#011TXT  ; ttl=4500] not fitting in legacy unicast packet, dropping.

Difficult to wade through all that.

 

Since you have dual parity your data is probably going to be OK.

 

The disabled disks are not reporting SMART. Most likely a connection issue. Check all connections, both ends, SATA and power, including any power splitters. Then reboot and post new diagnostics.

Likely a connection issue, disks dropped offline at the same time, still good to check SMART, also syslog rotated and doesn't show the boot process, so check that LSI controllers are using the latest firmware (p20.00.07.00), earlier p20 releases for example have known issues.

Welp, I've had quite the afternoon to say the least.  After opening the case and attempting to reseat the SATA and power cables on the two missing drives my server wouldn't boot anymore and I was getting Kernel Panic errors at boot.  I recreated the USB key as per some of the threads that I found and I'm able to boot successfully now.  The kicker is that it would appear that the two disks are being detected again, but now I've got 3 other disks that aren't being detected.  Disk 16 is located in a Supermicro DAS. 

homeserver-diagnostics-20200129-1548.zip

I went through all of the cabling again and all of my drives are being detected and I’m running through a recovery of Disk 1 and Parity 2.  Thanks for the help guys!  Now I need to looking into flashing my IBM M1015 and Intel RES2SV240.

8 hours ago, bisk said:

Now I need to looking into flashing my IBM M1015 and Intel RES2SV240.

Intel SAS expander is already on the latest firmware, LSI should be updated, though the version you're on is not known to be especially problematic, still it is quite old.