Server reboots whenever I write to onboard RAID (C232 chipset / WS2012 R2)

Keidos

Reputable
Mar 12, 2014
7
0
4,520
Short Version
I have an X11SSL motherboard, I’m using the onboard controller to run a RAID5 volume, and every time I interact with that volume, the computer forcibly shuts down.

Server Specs
CPU: Intel Xeon E3-1220 v5 SkyLake 3.0 GHz 8MB L3 Cache LGA 1151 80W BX80662E31220V5 Server Processor
CPU Cooler: Stock
Motherboard: SUPERMICRO MBD-X11SSL-O Micro ATX Server Motherboard LGA 1151 Intel C232
Memory: Crucial 32GB (2 x 16GB) 288-Pin DDR4 SDRAM ECC DDR4 2133 (PC4 17000) CT2K16G4RFD4213
Storage: Samsung 128GB SSD
Video Card: None - onboard
Case: NORCO RPC-450B Black 4U Rackmount Server Case
Power Supply: SeaSonic S12G S12G-550 550W ATX12V / EPS12V 80 PLUS GOLD Certified Active PFC Power Supply
Optical Drive: None
Array drives: (6) WD Red 3TB NAS Hard Disk Drive - 5400 RPM SATA 6 Gb/s 64MB Cache 3.5 Inch - WD30EFRX
Add-on card: SYBA SY-PEX40039 SATA III (6.0Gb/s) Controller Card

Details
The motherboard is in a server running Windows Server 2012 R2 Standard. It has a RAID5 array of 6x 3TB WD30EFRX drives. I don’t boot from the array – I’m using a PCIe SATA card to run a 7th drive, a 128 GB Samsung SSD.

I was able to create the RAID volume within the BIOS without issue. Finding the right driver for the controller in Windows was somewhat difficult, but installing both of these two files allowed the volume to appear in windows and gave me the management utility where I could see the array initializing.

Nearly every time I attempt to interact with that array in any way, the server unexpectedly reboots. This first happened after the array initialized, when I used the Disk Management utility to create a simple volume and format it as a single 12.7 TB NTFS partition. The second I hit the “finish” button to apply the format command, the machine rebooted. Windows Event Logs showed an unexpected shutdown, and the application event logs showed an error with Event ID 0 and no details whatsoever other than the source being the IAStorDataMgrSvc, which is the RAID management service.

I was able to boot back into windows and complete the format of the partition without issue. I was able to begin copying files to the partition. However any time that the array goes idle, the next time I try to copy data to the partition, the machine again reboots with the same useless error in the application logs.

Troubleshooting
I am in the process of downloading the huge Driver CD for this motherboard (linked from this page) to see if it has a better driver. What’s installed now, for the device, is…

Intel® C600+/C220+ series chipset SATA RAID Controller
Driver Provider: Intel Corporation
Driver Date: 5/21/2015
Driver Version: 4.3.0.1198

I’m not able to find a newer driver, from SuperMicro or from Intel. I've installed this package, but it didn't change the version number on the RAID controller driver.

Conclusion
Obviously, the server is unusable in this state. I'm not sure what's causing the reboots, and obviously windows logging isn't giving me much to work with. I could see the possibility that I have insufficient power, and I will try to rule that out this weekend when I have some free time. If that's not the cause, then I don't have any real leads. It seems like it could be a bad controller on the MoBo, a bad driver for WS2012 R2, or one-or-more bad drives. The last seems the least likely, as I would think my RAID controller software would let me know if it saw any drive errors.

Thanks in advance for any advice or suggestions!
 
Solution
Sigh... well that was quick.

I decided to blow off work and try the power supply test immediately. So far, yeah, it's looking promising.

Specifically I've just jumpered a little desktop power supply to think it's supposed to be running, after hooking it up to five of the array drives (taking that load off the server PSU). I kicked off a 2.5 TB copy about 10 minutes ago, and it's been rock solid. Looks like you should never trust online power supply calculators, even if you plan to double the size they recommend.
Sigh... well that was quick.

I decided to blow off work and try the power supply test immediately. So far, yeah, it's looking promising.

Specifically I've just jumpered a little desktop power supply to think it's supposed to be running, after hooking it up to five of the array drives (taking that load off the server PSU). I kicked off a 2.5 TB copy about 10 minutes ago, and it's been rock solid. Looks like you should never trust online power supply calculators, even if you plan to double the size they recommend.
 
Solution