<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ML150 G3 Restarts in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216896#M80110</link>
    <description>Well my system went completely offline this morning, The system reset and then all the fans were running flat out, no POST no video or anything.&lt;BR /&gt;&lt;BR /&gt;I have for some time been suspecting that the problem was related to cold as it "nearly" always happens in the early hours when the room is at the coldest. I am in Australia so it doesn't get very cold the room rarely gets beow 12 celicius. But this morning was around 8-10&lt;BR /&gt;&lt;BR /&gt;I disconnected EVERYTHING (incl RAM)out of the system except motherboard and CPU with no change, I tested all the PSU outputs and they were ok.&lt;BR /&gt;&lt;BR /&gt;When I removed the CPU I noticed one of the gold contacts had some oxidation/ discoloration possibly due to a bad contact. I VERY carefully cleaned the contact as well as I could (there was a matching discoloration on the m/b socket) &lt;BR /&gt;&lt;BR /&gt;The system immediately came back up. I can't say of course whether this was just because by this time the room was back up to around 20 celcius. ALSO the CPU is DEFINITELY suspect as I could not get the contact completely clean.&lt;BR /&gt;&lt;BR /&gt;MY QUESTION now is, if I get a new CPU can I use it in the SECOND socket, or does there have to be a CPU in socket 1? I would rather not have to immediately replace m/b AND cpu if I can help it.&lt;BR /&gt;&lt;BR /&gt;MTIA</description>
    <pubDate>Wed, 09 Jul 2008 00:51:25 GMT</pubDate>
    <dc:creator>Brian Messenger</dc:creator>
    <dc:date>2008-07-09T00:51:25Z</dc:date>
    <item>
      <title>ML150 G3 Restarts</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216887#M80101</link>
      <description>&lt;!--!*#--&gt;System is ML150 G3 approx 2 years old&lt;BR /&gt;Single Xeon Dual Core 1.86GHz Processor 3GB RAM&lt;BR /&gt;Proliant BIOS O07 3/31/2008 &lt;BR /&gt;2 x 500GB SATA Hard Disks setup as RAID1 array&lt;BR /&gt;Running Windows SBS 2003 with all SPs &amp;amp; updates (probably not relevant)&lt;BR /&gt;&lt;BR /&gt;All HP drivers also are the latest&lt;BR /&gt;&lt;BR /&gt;System is intermittently resetting, runs for anything from 24 - 96 hours. Usually happens early hours of the morning 3am - 6am but has done it during the day&lt;BR /&gt;&lt;BR /&gt;This is a hard reset (not a clean windows shutdown) there are no errors in the Windows event logs other than when the server comes up there is an event that says last shutdown was unexpected&lt;BR /&gt;&lt;BR /&gt;I have noted some similar posts in these forums and have Disabled the OS Watchdog in BIOS&lt;BR /&gt;&lt;BR /&gt;DMI log is empty&lt;BR /&gt;&lt;BR /&gt;The BMC System log has the same four entries each time&lt;BR /&gt;&lt;BR /&gt;GEN ID 20 00&lt;BR /&gt;SEL MSG REV 04&lt;BR /&gt;SENSOR TYPE 04 - Fan&lt;BR /&gt;SENSOR NUMBER 32 - CPU1 Fan&lt;BR /&gt;SEL EVENT TYPE 01 - Threshold&lt;BR /&gt;EVENT DESCRIPTION Lower Critical Going Low, Assertion&lt;BR /&gt;SEL EVENT DATA 52 FF FE&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;GEN ID 20 00&lt;BR /&gt;SEL MSG REV 04&lt;BR /&gt;SENSOR TYPE 02 - Voltage&lt;BR /&gt;SENSOR NUMBER 32 - CPU1 VCore&lt;BR /&gt;SEL EVENT TYPE 01 - Threshold&lt;BR /&gt;EVENT DESCRIPTION Upper Critical Going Low, Deassertion&lt;BR /&gt;SEL EVENT DATA 58 FF A4&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;GEN ID 20 00&lt;BR /&gt;SEL MSG REV 04&lt;BR /&gt;SENSOR TYPE 02 - Voltage&lt;BR /&gt;SENSOR NUMBER 32 - CPU1 VCore&lt;BR /&gt;SEL EVENT TYPE 01 - Threshold&lt;BR /&gt;EVENT DESCRIPTION Upper Critical Going High, Assertion&lt;BR /&gt;SEL EVENT DATA 59 FF A4&lt;BR /&gt;&lt;BR /&gt;GEN ID 20 00&lt;BR /&gt;SEL MSG REV 04&lt;BR /&gt;SENSOR TYPE 27 - LAN&lt;BR /&gt;SENSOR NUMBER 5D LOM Link Status&lt;BR /&gt;SEL EVENT TYPE 03 - Digital Discrete&lt;BR /&gt;EVENT DESCRIPTION State Asserted, Assertion&lt;BR /&gt;SEL EVENT DATA 01 FF FF&lt;BR /&gt;&lt;BR /&gt;My thinking is that this is Power Supply, but possibilities are also Motherboard or CPU. Given these are premium priced parts I would like to get it right first time "if possible" :-) &lt;BR /&gt;&lt;BR /&gt;I ran Insight Diags overnight once and the server did reset but there was nothing in the server logs to indicate any errors. This is a production server so I can't have it offline for an extended period, most frustrating!&lt;BR /&gt;&lt;BR /&gt;MTIA</description>
      <pubDate>Mon, 16 Jun 2008 06:07:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216887#M80101</guid>
      <dc:creator>Brian Messenger</dc:creator>
      <dc:date>2008-06-16T06:07:49Z</dc:date>
    </item>
    <item>
      <title>Re: ML150 G3 Restarts</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216888#M80102</link>
      <description>Hi, when you ran the Insight Diags off line edition did the server reboot while the diags were running? If you have a maintenance window during nights try to run the test but choose at least 15 or 20 so that we can make sure the server is going to be Stressed during the whole night. If the server does not shutdown while doing those tests and if they come out clean then chances are that you are having a SW issue.&lt;BR /&gt;&lt;BR /&gt;Pls let me know.</description>
      <pubDate>Tue, 17 Jun 2008 17:30:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216888#M80102</guid>
      <dc:creator>RaMpaNTe</dc:creator>
      <dc:date>2008-06-17T17:30:26Z</dc:date>
    </item>
    <item>
      <title>Re: ML150 G3 Restarts</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216889#M80103</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;thanks for the response, as per my original post the server did reset during the diagnostics, which pretty much eliminates a software error. But thas fryour reply</description>
      <pubDate>Tue, 17 Jun 2008 19:38:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216889#M80103</guid>
      <dc:creator>Brian Messenger</dc:creator>
      <dc:date>2008-06-17T19:38:19Z</dc:date>
    </item>
    <item>
      <title>Re: ML150 G3 Restarts</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216890#M80104</link>
      <description>Om so try the following, minimize the server to its base config, ie minumum memory, no PCI cards etc. Run one loop and see if the server reboots if not then start adding the components you have removed one by one so you can find which one is causing the issue. Then call Hp to get the part replaced (If the server is under warranty or contract)  If not willing to spend more time on this then I would suggest you to replace the power supply.&lt;BR /&gt;&lt;BR /&gt;TY</description>
      <pubDate>Wed, 18 Jun 2008 03:31:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216890#M80104</guid>
      <dc:creator>RaMpaNTe</dc:creator>
      <dc:date>2008-06-18T03:31:22Z</dc:date>
    </item>
    <item>
      <title>Re: ML150 G3 Restarts</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216891#M80105</link>
      <description>Thanks I will give this a go, but running diags for just a pass or two may not tell me anything as the system rarely resets in anything less than 24 hours and when I did run the insight diags and it reset all I know is that the system had been running for around 2 hours when I left for the evening and had reset when I returned approx 12 hours later. &lt;BR /&gt;&lt;BR /&gt;I appreciate the input, I was hoping someone might be able to comment on what the SEL entries were telling me as these are CONSISTENT on EVERY reset&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Wed, 18 Jun 2008 04:52:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216891#M80105</guid>
      <dc:creator>Brian Messenger</dc:creator>
      <dc:date>2008-06-18T04:52:52Z</dc:date>
    </item>
    <item>
      <title>Re: ML150 G3 Restarts</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216892#M80106</link>
      <description>Hi Brian,&lt;BR /&gt;I'm experiencing a very similar problem with my client's ML110G4.&lt;BR /&gt;There is an exact correlation (apart from the minor clock offsets) between the SEL and the SBS2003 event log.&lt;BR /&gt;i.e. SEL has Lower Critical Going Low, Assertion then event log has unexpected shutdown.&lt;BR /&gt;Interestingly the SEL logs are all at 51 minutes past the hour (+/- 30 seconds). The hour appears to be random. So what happens to my server at HH:51 ??&lt;BR /&gt;&lt;BR /&gt;I'm thinking/hoping power supply too but just a guess really. Would love to find out more.&lt;BR /&gt;</description>
      <pubDate>Tue, 01 Jul 2008 08:08:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216892#M80106</guid>
      <dc:creator>David J Campbell</dc:creator>
      <dc:date>2008-07-01T08:08:31Z</dc:date>
    </item>
    <item>
      <title>Re: ML150 G3 Restarts</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216893#M80107</link>
      <description>Hi David&lt;BR /&gt;&lt;BR /&gt;the restarts on my server became more frequent for a few days.&lt;BR /&gt;&lt;BR /&gt;i.e. started at around 4:00am and very similarly to you restarted almost exactly an hour apart for three or four times.&lt;BR /&gt;&lt;BR /&gt;I stripped my system back to absolute essentials, no hard drives, 1GB RAM and ran HP Insight Diags overnight and NO RESET I then put everything back one piece at a time. I did a thorough scan of both SATAand found no errors. Everything has now been back together for two days and still NO resets. I have done a thorough visual inspection without finding anything. At this stage I still don't know if it is fixed as at some stages I have gone four or five days without an issue&lt;BR /&gt;&lt;BR /&gt;I'm the same as you I wish someone could tell me what those SEL entries indicated&lt;BR /&gt;&lt;BR /&gt;Regards</description>
      <pubDate>Tue, 01 Jul 2008 08:33:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216893#M80107</guid>
      <dc:creator>Brian Messenger</dc:creator>
      <dc:date>2008-07-01T08:33:33Z</dc:date>
    </item>
    <item>
      <title>Re: ML150 G3 Restarts</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216894#M80108</link>
      <description>Hi Brian,&lt;BR /&gt;I called HP Support and they offered me similar advice: ie reseat the CPU. So I did that today and will see how we go. They seemed to think it wasn't likely to be the power supply since the voltage is regulated on the motherboard. So I presume from that that the power supply is an all or nothing proposition. They also suggested I try a new processor to rule the existing processor in or out as the culprit. I don't have any other devices attached to the motherboard so I guess it's one or the other. Still under warranty...I think :)&lt;BR /&gt;How's your box going?&lt;BR /&gt;David</description>
      <pubDate>Sun, 06 Jul 2008 09:47:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216894#M80108</guid>
      <dc:creator>David J Campbell</dc:creator>
      <dc:date>2008-07-06T09:47:39Z</dc:date>
    </item>
    <item>
      <title>Re: ML150 G3 Restarts</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216895#M80109</link>
      <description>Hi David&lt;BR /&gt;&lt;BR /&gt;mine reset shortly after my last post. I stripped all non essentials out again and ran diags overnight and it reset again, I am beginning to think as HP suggest that it is motherboard. My system is not under warranty, so it becomes a pricey proposition to "try" a new motherboard or processor. Sill not much choice I guess.&lt;BR /&gt;&lt;BR /&gt;Thanks for your input&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Brian</description>
      <pubDate>Sun, 06 Jul 2008 20:43:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216895#M80109</guid>
      <dc:creator>Brian Messenger</dc:creator>
      <dc:date>2008-07-06T20:43:33Z</dc:date>
    </item>
    <item>
      <title>Re: ML150 G3 Restarts</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216896#M80110</link>
      <description>Well my system went completely offline this morning, The system reset and then all the fans were running flat out, no POST no video or anything.&lt;BR /&gt;&lt;BR /&gt;I have for some time been suspecting that the problem was related to cold as it "nearly" always happens in the early hours when the room is at the coldest. I am in Australia so it doesn't get very cold the room rarely gets beow 12 celicius. But this morning was around 8-10&lt;BR /&gt;&lt;BR /&gt;I disconnected EVERYTHING (incl RAM)out of the system except motherboard and CPU with no change, I tested all the PSU outputs and they were ok.&lt;BR /&gt;&lt;BR /&gt;When I removed the CPU I noticed one of the gold contacts had some oxidation/ discoloration possibly due to a bad contact. I VERY carefully cleaned the contact as well as I could (there was a matching discoloration on the m/b socket) &lt;BR /&gt;&lt;BR /&gt;The system immediately came back up. I can't say of course whether this was just because by this time the room was back up to around 20 celcius. ALSO the CPU is DEFINITELY suspect as I could not get the contact completely clean.&lt;BR /&gt;&lt;BR /&gt;MY QUESTION now is, if I get a new CPU can I use it in the SECOND socket, or does there have to be a CPU in socket 1? I would rather not have to immediately replace m/b AND cpu if I can help it.&lt;BR /&gt;&lt;BR /&gt;MTIA</description>
      <pubDate>Wed, 09 Jul 2008 00:51:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml150-g3-restarts/m-p/4216896#M80110</guid>
      <dc:creator>Brian Messenger</dc:creator>
      <dc:date>2008-07-09T00:51:25Z</dc:date>
    </item>
  </channel>
</rss>

