3 Replies Latest reply on Jun 8, 2016 10:24 AM by Intel Corporation

    iaStorB event 129 Reset to device, \Device\RaidPort0, was issued.

    jabouley

      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

        • 1. Re: iaStorB event 129 Reset to device, \Device\RaidPort0, was issued.
          Intel Corporation
          This message was posted on behalf of Intel Corporation

          I have checked your motherboard specifications and I noticed that you are currently running an Intel® server chipset. Based on the platform, I would recommend to contact your motherboard maker, in this case Asus support. https://www.asus.com/Commercial-Servers-Workstations/Z10PAD8/HelpDesk/
          Try posting this inquiry at: https://vip.asus.com/forum/

          Allan. 

           

          • 2. Re: iaStorB event 129 Reset to device, \Device\RaidPort0, was issued.
            jabouley

            Hi Allen,

             

            Thank you for your response.  I have contacted ASUS and they were not helpful at all.  After contacting Samsung, they had me send one of the drives back for repair as it didn't have the most recent firmware.  After receiving the "repaired" drive, I have had no problems for two months.  However, the symptoms were exactly the same.  I am suspecting that the drives are going to sleep and not waking up properly which is causing the "reset" warning in the Event Logs.

             

            I noticed that there is an option in the Intel Driver to disable Link Power Management (LPM).  Therefore, I have updated the BIOS and Intel drivers to the latest and disabled the LPM in the Windows registry as follows.  Do you think this has something to do with the issue?

             

             

            [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorB\Parameters\Port0]

            "LPM"=dword:00000000

            "LPMDSTATE"=dword:00000000

            "DIPM"=dword:00000000

            [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorB\Parameters\Port1]

            "LPM"=dword:00000000

            "LPMDSTATE"=dword:00000000

            "DIPM"=dword:00000000

            [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorB\Parameters\Port2]

            "LPM"=dword:00000000

            "LPMDSTATE"=dword:00000000

            "DIPM"=dword:00000000

            [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorB\Parameters\Port3]

            "LPM"=dword:00000000

            "LPMDSTATE"=dword:00000000

            "DIPM"=dword:00000000

            [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorB\Parameters\Port4]

            "LPM"=dword:00000000

            "LPMDSTATE"=dword:00000000

            "DIPM"=dword:00000000

            [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorB\Parameters\Port5]

            "LPM"=dword:00000000

            "LPMDSTATE"=dword:00000000

            "DIPM"=dword:00000000

            • 3. Re: iaStorB event 129 Reset to device, \Device\RaidPort0, was issued.
              Intel Corporation
              This message was posted on behalf of Intel Corporation

              I would recommend to keep checking on the Asus forums for support on your Intel® server chipset. Please bear in mind that Intel does not assist with registry issues. 

              Allan.