<?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: Microserver bay malfunction in HPE ProLiant Servers - Netservers</title>
    <link>https://community.hpe.com/t5/hpe-proliant-servers-netservers/microserver-bay-malfunction/m-p/5613339#M19848</link>
    <description>&lt;P&gt;The resolution was to add missed screws or the drive interface panel (each panel should have 2 screws but aparently assembler forgot of them). This caused SATA interface was not firmly connected to the SATA interface of the drives. Bay&amp;nbsp;0 has cables behind and that made it worked fine.&amp;nbsp;To add missed drive I had to remove case fan (4 Torx 10 screws). Now everythiong works fine.&lt;/P&gt;</description>
    <pubDate>Mon, 09 Apr 2012 16:44:57 GMT</pubDate>
    <dc:creator>Nitraner</dc:creator>
    <dc:date>2012-04-09T16:44:57Z</dc:date>
    <item>
      <title>Microserver bay malfunction</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-netservers/microserver-bay-malfunction/m-p/5611227#M19845</link>
      <description>&lt;P&gt;Hi all!&lt;/P&gt;&lt;P&gt;Looking for advice here...&lt;/P&gt;&lt;P&gt;I have N36 Microserver bundled with 160 GB HDD.&lt;/P&gt;&lt;P&gt;The issue is that no drives are recognized in bays 1 and 2 (but hdd's spindles run fine)&lt;/P&gt;&lt;P&gt;Bay 0 sees fine 160GB and 3TB drives, bay 3 sees only 160GB drive.&lt;/P&gt;&lt;P&gt;Aparently this behavior is from the beginning (I did not use bays 1-3 for more than a year).&lt;/P&gt;&lt;P&gt;Drives&amp;nbsp;are fine, moved between bays while box is powered off and firmly attached. Latest BIOS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I believe this hardware issue and could be resulted by oxidation of SATA interface contacts. How to clean them safely?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any other sugestions/experience?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance folks!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Apr 2012 16:10:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-netservers/microserver-bay-malfunction/m-p/5611227#M19845</guid>
      <dc:creator>Nitraner</dc:creator>
      <dc:date>2012-04-06T16:10:39Z</dc:date>
    </item>
    <item>
      <title>Re: Microserver bay malfunction</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-netservers/microserver-bay-malfunction/m-p/5613339#M19848</link>
      <description>&lt;P&gt;The resolution was to add missed screws or the drive interface panel (each panel should have 2 screws but aparently assembler forgot of them). This caused SATA interface was not firmly connected to the SATA interface of the drives. Bay&amp;nbsp;0 has cables behind and that made it worked fine.&amp;nbsp;To add missed drive I had to remove case fan (4 Torx 10 screws). Now everythiong works fine.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Apr 2012 16:44:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-netservers/microserver-bay-malfunction/m-p/5613339#M19848</guid>
      <dc:creator>Nitraner</dc:creator>
      <dc:date>2012-04-09T16:44:57Z</dc:date>
    </item>
  </channel>
</rss>

