<?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 EFI Shell in Integrity Servers</title>
    <link>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/4246665#M4107</link>
    <description>how do I recreae or create the FSx: at the efi shell level. map -r , reconnect -r and resetting the sever does not show the FSx:&lt;BR /&gt;directory. also there is no O/S on the server right now so the disks are blank.</description>
    <pubDate>Tue, 05 Aug 2008 16:56:05 GMT</pubDate>
    <dc:creator>PCD_HPUX Group</dc:creator>
    <dc:date>2008-08-05T16:56:05Z</dc:date>
    <item>
      <title>EFI Shell</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/4246665#M4107</link>
      <description>how do I recreae or create the FSx: at the efi shell level. map -r , reconnect -r and resetting the sever does not show the FSx:&lt;BR /&gt;directory. also there is no O/S on the server right now so the disks are blank.</description>
      <pubDate>Tue, 05 Aug 2008 16:56:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/4246665#M4107</guid>
      <dc:creator>PCD_HPUX Group</dc:creator>
      <dc:date>2008-08-05T16:56:05Z</dc:date>
    </item>
    <item>
      <title>Re: EFI Shell</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/4246666#M4108</link>
      <description>The "fsx" are EFI readable partitions (FAT32), containing the OS loader and some other files.&lt;BR /&gt;&lt;BR /&gt;This partition will be created during OS installation or disk mirroring.</description>
      <pubDate>Tue, 05 Aug 2008 17:00:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/4246666#M4108</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-08-05T17:00:04Z</dc:date>
    </item>
    <item>
      <title>Re: EFI Shell</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/4246667#M4109</link>
      <description>great response, so heres the complete senario.&lt;BR /&gt;I have a rx2660 that I am trying to boot up using a sas drive from another rx2660 server that I installed a 11i.v3 O/S on, but this drive is not part of the ir mirror which have no O/S on them. &lt;BR /&gt;I am doing this to see if we can elminate our make tape recovery for our remote locations and use disk only.&lt;BR /&gt;But because of network banwidth igniting over the network would take a long time.&lt;BR /&gt;So if I understand correctly without an initial O/S install on the ir sas drives, I won't have acess to the FSx: at the efi shell level.</description>
      <pubDate>Tue, 05 Aug 2008 17:31:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/4246667#M4109</guid>
      <dc:creator>PCD_HPUX Group</dc:creator>
      <dc:date>2008-08-05T17:31:54Z</dc:date>
    </item>
    <item>
      <title>Re: EFI Shell</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/4246668#M4110</link>
      <description>after swapping drives did you go into drvcfg and configure the controller to recognize the drives ?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 05 Aug 2008 17:34:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/4246668#M4110</guid>
      <dc:creator>Tim Nelson</dc:creator>
      <dc:date>2008-08-05T17:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: EFI Shell</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/4246669#M4111</link>
      <description>I already did this kind of "roaming", but this is maybe the better solution:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=DynRootDisk" target="_blank"&gt;http://h20392.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=DynRootDisk&lt;/A&gt;</description>
      <pubDate>Tue, 05 Aug 2008 18:19:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/4246669#M4111</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-08-05T18:19:31Z</dc:date>
    </item>
    <item>
      <title>Re: EFI Shell</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/4246670#M4112</link>
      <description>This is what I did in sequence order.&lt;BR /&gt;1. system has three sas drives all blank.&lt;BR /&gt;on slots 6,7,8.&lt;BR /&gt;2. create ir mirror with 7 &amp;amp; 8. made 6 a hotspare.&lt;BR /&gt;3. syschronize 7 &amp;amp; 8&lt;BR /&gt;&lt;BR /&gt;4. inserted sas drive with 11i.v3 O/S into slot 1.&lt;BR /&gt;&lt;BR /&gt;server see's all 4 sas drives&lt;BR /&gt;&lt;BR /&gt;drvcfg -s &lt;BR /&gt;&lt;BR /&gt;but hold on I am retrying the sycn again and will update this space tomorrow,&lt;BR /&gt;I am sycn'ing the drive with the O/S on it with another blank drive, but will take an hour.</description>
      <pubDate>Tue, 05 Aug 2008 18:43:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/4246670#M4112</guid>
      <dc:creator>PCD_HPUX Group</dc:creator>
      <dc:date>2008-08-05T18:43:28Z</dc:date>
    </item>
    <item>
      <title>Re: EFI Shell</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/4246671#M4113</link>
      <description>If all drives are blank you have nothing to synchronize - right?&lt;BR /&gt;&lt;BR /&gt;Consider to LVM mirror the 11.31 disk to the IR disk set, sync, shutdown, remove the original disk (to keep the contents), boot again and remove the info about the missing disk.</description>
      <pubDate>Tue, 05 Aug 2008 18:55:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-shell/m-p/4246671#M4113</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-08-05T18:55:22Z</dc:date>
    </item>
  </channel>
</rss>

