I have a Windows 2012 R2 Server running Asus Z10PA-D8 series motherboard.
The drives are arranged into two Raid arrays.
Raid 1 = 2 x Samsung 850 EVO 256GB SSD
Raid1 = 2 x Seagate 2TB traditional Hard Drives ST2000NM0033
On March 22, 2016 we had a problem where the server appears to lockup. Upon investigating, the screen was black and the keyboard and mouse were unresponsive. We noticed that one of the SSD drives was continually blinking in rapid succession. A forced power recovered the server and all raid arrays rebuilt. After this happened several more time, I contacted Samsung and they did a warranty repair on one of the SSD's. They determined that the drive needed a firmware update. Since the drive was repaired we have had no other issues with the server until today.
The server appeared to freeze again with the same symptoms of no video, keyboard or mouse. Instead of forcing the server to power down, I removed the blinking SSD Port 1. The server immediately started responding and recognized that the drive was removed. I reinserted the drive and it rebuilt the RAID 1 array and the server is working normally.
Looking into the SYSTEM Event Log there are hundreds of events all showing the same message that occurs before the server actually stopped responding.
Log Name: System
Source: iaStorB
Date: 5/30/2016 1:43:13 AM
Event ID: 129
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Server2012
Description:
Reset to device, \Device\RaidPort0, was issued.
We have never had a problem with the Seagate drives only the Samsung.
My question is, why does the software issue hundreds of reset events and then lock the system? In the event of an actual failure, I would hope that the server would not lock but report the fact that a failure has occurred.
Is this a known problem and if so how to prevent this from occurring in the future.
Thank you,
J