<?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: booting problem in Netservers</title>
    <link>https://community.hpe.com/t5/netservers/booting-problem/m-p/3692900#M8481</link>
    <description>Hi Ramesh,&lt;BR /&gt;&lt;BR /&gt;When troubleshooting an issue like this start by stripping the system down to the bare minimum configuration.  It would also help to know at which point in the POST the system hangs.  If it hangs at "Firmware spinning up drives", it means you have a hard drive that is not responding and hanging up the controller.&lt;BR /&gt;&lt;BR /&gt;If it says "Firmware Initializing, then the RAID controller is probably suspect.  In this situation, I always start by reseating the cache module on the RAID controller.&lt;BR /&gt;&lt;BR /&gt;If none of these conditions exist or if the lockups are in different sections of the POST, it could be a thermal lockup.  If the server has 2 CPU's try pulling one of them and then the other. &lt;BR /&gt;&lt;BR /&gt;Let us know what you find out,&lt;BR /&gt;&lt;BR /&gt;Sean T. Craig Sr. C.E.T., M.C.P.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 16 Dec 2005 16:53:39 GMT</pubDate>
    <dc:creator>Sean T. Craig</dc:creator>
    <dc:date>2005-12-16T16:53:39Z</dc:date>
    <item>
      <title>booting problem</title>
      <link>https://community.hpe.com/t5/netservers/booting-problem/m-p/3692898#M8479</link>
      <description>In HP netserver lc2000 with windows 2003 o/s not booting in first screen itself it hange no response from the keyboard and monitor got green led</description>
      <pubDate>Fri, 16 Dec 2005 06:58:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/booting-problem/m-p/3692898#M8479</guid>
      <dc:creator>Ramesh P</dc:creator>
      <dc:date>2005-12-16T06:58:25Z</dc:date>
    </item>
    <item>
      <title>Re: booting problem</title>
      <link>https://community.hpe.com/t5/netservers/booting-problem/m-p/3692899#M8480</link>
      <description>Dear Ramesh,&lt;BR /&gt;&lt;BR /&gt;I suspect the system board. Please check the SMPS voltages also, if all voltages are not correct then also it would lead to this condition.&lt;BR /&gt;&lt;BR /&gt;With Regards,&lt;BR /&gt;&lt;BR /&gt;Siva.</description>
      <pubDate>Fri, 16 Dec 2005 08:14:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/booting-problem/m-p/3692899#M8480</guid>
      <dc:creator>Sivakumar TS</dc:creator>
      <dc:date>2005-12-16T08:14:47Z</dc:date>
    </item>
    <item>
      <title>Re: booting problem</title>
      <link>https://community.hpe.com/t5/netservers/booting-problem/m-p/3692900#M8481</link>
      <description>Hi Ramesh,&lt;BR /&gt;&lt;BR /&gt;When troubleshooting an issue like this start by stripping the system down to the bare minimum configuration.  It would also help to know at which point in the POST the system hangs.  If it hangs at "Firmware spinning up drives", it means you have a hard drive that is not responding and hanging up the controller.&lt;BR /&gt;&lt;BR /&gt;If it says "Firmware Initializing, then the RAID controller is probably suspect.  In this situation, I always start by reseating the cache module on the RAID controller.&lt;BR /&gt;&lt;BR /&gt;If none of these conditions exist or if the lockups are in different sections of the POST, it could be a thermal lockup.  If the server has 2 CPU's try pulling one of them and then the other. &lt;BR /&gt;&lt;BR /&gt;Let us know what you find out,&lt;BR /&gt;&lt;BR /&gt;Sean T. Craig Sr. C.E.T., M.C.P.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 16 Dec 2005 16:53:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/booting-problem/m-p/3692900#M8481</guid>
      <dc:creator>Sean T. Craig</dc:creator>
      <dc:date>2005-12-16T16:53:39Z</dc:date>
    </item>
  </channel>
</rss>

