none
Need Help with HP MS Server EX470 Hardware Issue RRS feed

  • Question

  • Beginning on 12-15 the Event Log for my HP WHS started throwing a bunch of SiSRAID2 Event 9 errors (see graphics below).  On several occasions the server would reboot on its own and throw "Recovered from a Serious Error" dialogues after the reboot.  A couple of those time the Microsoft suggested problem pointed to hardware issues involving memory.  I'd done the 2GM RAM upgrade many months ago so I figured maybe the 2GB G.Skill memory chip was going bad, so I removed the chip and reinstalled the original 512MB RAM chip that came stock with the server, but the errors persist.

    Since the problem is likely not RAM I decided to look at my hard disks.  All the SCSI disks (4 total) in the unit show as "Healthy" but, other than Chkdsk I have no real way of diagnosing them for integrity.  Is there a utility I can use for this that I can monitor?  With the headless server web interface I'm not sure how to run diagnostics to check for problems when I can't monitor the utility.

    Any help or suggestions would be terrific.  I love the WHS, it's saved my bacon a couple times and really does take the burden off maintaining backups for all my PCs.  But I think I have a problem creeping up...

    Here are links to 3 screenshots that might help.

    Event Log Dialogue (SiSRAID2 Error)
    Event Properties Dialogue (SiSRAID2 Error)
    Event Properties Dialogue - System Error 1003

    Thanks for taking the time to assist!
    Doug



    Saturday, December 27, 2008 8:06 PM

Answers

  • Problem solved!  Turns out a reconditioned 500GB drive I received from Western Digital (warranty replacement) doesn't seem to get along with the MSS.  The drive works fine in my desktop PC but when used in the MSS drive pool it causes SiSRAID2 errors to be thrown periodically along with spontaneous reboots and general server instability.

    Details:  I called HP on Monday and sent them all the logs (using the Toolkit) and they said they'd get back to me in a day or so after they had time to analyze the information.  While waiting for their return call (still waiting  :? ) it dawned on me that the reconditioned drive I installed in mid-December might be the problem.  Although it showed as completely healthy in the system I had a hunch it might be the culprit.  I used the normal process to remove the drive (did not have any data on it yet), powered down the MSS and removed it from the unit.  After booting back up all has been well for nearly 24 hours with zero SiSRAID2 errors.  The MSS is stable and all appears well.  Provided I remain error-free for the next couple days, I'll reply back here to close the loop.

    Doug
    • Marked as answer by SonCoder Wednesday, December 31, 2008 4:07 AM
    Wednesday, December 31, 2008 4:06 AM

All replies

  • Hi Doug,
    the message points definitively to an hardware issue. You could check, if the SATA cables are still seated properly on both ends (maybe during the memory upgrade the contacts have been hurt). Also maybe, one disk is no longer connected properly in the tray - maybe pulling out and in helps. Or a disk is about to fail and responds slower due to another fault. IF you have other trays still free, you can try to move the disk to another tray as well. (For each of these actions shut down the server properly.
    The health status in the console responds very delayed to some errors, which is an unfortunate, but known issue.
    If you login via Remote Desktop to your WHS, click Start/Run, type diskmgmt.msc and click OK, are all disks still visible?

    If the actions above did not fix the behavior, you should contact HP to get the disk or the system replaced/repaired under warranty or help to find the reason.

    Best greetings from Germany
    Olaf
    Saturday, December 27, 2008 10:00 PM
    Moderator
  • Hi Olaf... thanks for the response.  Yes, all the disks are visible and each shows as "healthy".  Just the other night I had the server torn down to swap out the RAM and made sure I reassembled it correctly and that each of the disks was fully seated as well as the three wired connectors attached to the back plane.

    Also, unfortunately, I've had the WHS for just over a year so it is out of warranty.  I'll work this problem the best I can using the resources available on the internet (like you!).  If all that fails I just might pay HP for some of their support.

    I'm tearing the server back down tonight to put the 2GB RAM stick back in since I now know RAM wasn't the problem.  I'll be sure to pay special attention to all the connections during the process.

    Again, thanks for your help!
    Doug
    Sunday, December 28, 2008 3:16 AM
  • Problem solved!  Turns out a reconditioned 500GB drive I received from Western Digital (warranty replacement) doesn't seem to get along with the MSS.  The drive works fine in my desktop PC but when used in the MSS drive pool it causes SiSRAID2 errors to be thrown periodically along with spontaneous reboots and general server instability.

    Details:  I called HP on Monday and sent them all the logs (using the Toolkit) and they said they'd get back to me in a day or so after they had time to analyze the information.  While waiting for their return call (still waiting  :? ) it dawned on me that the reconditioned drive I installed in mid-December might be the problem.  Although it showed as completely healthy in the system I had a hunch it might be the culprit.  I used the normal process to remove the drive (did not have any data on it yet), powered down the MSS and removed it from the unit.  After booting back up all has been well for nearly 24 hours with zero SiSRAID2 errors.  The MSS is stable and all appears well.  Provided I remain error-free for the next couple days, I'll reply back here to close the loop.

    Doug
    • Marked as answer by SonCoder Wednesday, December 31, 2008 4:07 AM
    Wednesday, December 31, 2008 4:06 AM