<?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: Inaccessable Boot Device in ProLiant Deployment and Provisioning</title>
    <link>https://community.hpe.com/t5/proliant-deployment-and/inaccessable-boot-device/m-p/3804127#M3492</link>
    <description>O:&lt;BR /&gt;&lt;BR /&gt;The problem is that the OS does NOT know that there is a 6i controller in the new server.  You need to tell it that there is.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;In the following thread, I posted a file with the proper registry entry that is needed.  Run it and take your image.  It should work just fine afterwards.&lt;BR /&gt;&lt;BR /&gt;" &lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1034031" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1034031&lt;/A&gt; "&lt;BR /&gt;&lt;BR /&gt;Just inport the 6i.reg file, on the BL20p G2. Grab image. Deploy on G3. Run PSP.&lt;BR /&gt;&lt;BR /&gt;Steven</description>
    <pubDate>Mon, 12 Jun 2006 08:57:59 GMT</pubDate>
    <dc:creator>Steven Clementi</dc:creator>
    <dc:date>2006-06-12T08:57:59Z</dc:date>
    <item>
      <title>Inaccessable Boot Device</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/inaccessable-boot-device/m-p/3804126#M3491</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;We need to move one of our BL20p G2 Windows 2000 server images onto a BL20p G3 due to various upgrades taking place. But when we do this the server Blue Screens on boot up showing the error as being an Inaccessable Boot Device. We ahve applied the latest PSP but still the problem persists. The issues is around the fact that one has a 5i and the other a 6i controller. &lt;BR /&gt;&lt;BR /&gt;Does anybody have a fix for this so that we can get these production servers moved to their new enviornment?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;O</description>
      <pubDate>Mon, 12 Jun 2006 07:05:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/inaccessable-boot-device/m-p/3804126#M3491</guid>
      <dc:creator>Octavius</dc:creator>
      <dc:date>2006-06-12T07:05:13Z</dc:date>
    </item>
    <item>
      <title>Re: Inaccessable Boot Device</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/inaccessable-boot-device/m-p/3804127#M3492</link>
      <description>O:&lt;BR /&gt;&lt;BR /&gt;The problem is that the OS does NOT know that there is a 6i controller in the new server.  You need to tell it that there is.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;In the following thread, I posted a file with the proper registry entry that is needed.  Run it and take your image.  It should work just fine afterwards.&lt;BR /&gt;&lt;BR /&gt;" &lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1034031" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1034031&lt;/A&gt; "&lt;BR /&gt;&lt;BR /&gt;Just inport the 6i.reg file, on the BL20p G2. Grab image. Deploy on G3. Run PSP.&lt;BR /&gt;&lt;BR /&gt;Steven</description>
      <pubDate>Mon, 12 Jun 2006 08:57:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/inaccessable-boot-device/m-p/3804127#M3492</guid>
      <dc:creator>Steven Clementi</dc:creator>
      <dc:date>2006-06-12T08:57:59Z</dc:date>
    </item>
  </channel>
</rss>

