<?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: EFI Boot Device Configuration in Integrity Servers</title>
    <link>https://community.hpe.com/t5/integrity-servers/efi-boot-device-configuration/m-p/4681694#M6748</link>
    <description>Between answering questions for a case I opened with support and reviewing various other threads based on the output of errors I got when booting, I found a partial if not full solution. Basically, I determined that the disk was in good shape, and that somehow booting needed something - it was this:&lt;BR /&gt;&lt;BR /&gt;1. at the efi shell, connected with the device that had my data... fsx: &lt;BR /&gt;&lt;BR /&gt;2. issued the command 'hpux -lq' &lt;BR /&gt;&lt;BR /&gt;where normally, it had been, 'hpux'&lt;BR /&gt;&lt;BR /&gt;More to do on this, but at least we booted!&lt;BR /&gt;&lt;BR /&gt;RC Park</description>
    <pubDate>Wed, 01 Sep 2010 22:06:40 GMT</pubDate>
    <dc:creator>RC Park</dc:creator>
    <dc:date>2010-09-01T22:06:40Z</dc:date>
    <item>
      <title>EFI Boot Device Configuration</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-boot-device-configuration/m-p/4681691#M6745</link>
      <description>Is there a clear how to guide on fixing problems when SAN/storage IDs may have changed?  I'm getting an error now also documented in this thread:&lt;BR /&gt;&lt;BR /&gt;Subject: RE: EFI displaying contents of /stand &lt;BR /&gt;URL: &lt;A href="http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1441354" target="_blank"&gt;http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1441354&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I'm hoping someone can help me figure out how to determine what changed so I can rescan or do what ever is necessary to reconnect with my SAN boot disk.&lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
      <pubDate>Tue, 31 Aug 2010 17:34:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-boot-device-configuration/m-p/4681691#M6745</guid>
      <dc:creator>RC Park</dc:creator>
      <dc:date>2010-08-31T17:34:32Z</dc:date>
    </item>
    <item>
      <title>Re: EFI Boot Device Configuration</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-boot-device-configuration/m-p/4681692#M6746</link>
      <description>In order to search the SAN for possible boot devices you need to adjust the EFIScanLevel of the appropriate FC card. After this, do a "reconnect -r" and "map -r".</description>
      <pubDate>Wed, 01 Sep 2010 05:53:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-boot-device-configuration/m-p/4681692#M6746</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2010-09-01T05:53:50Z</dc:date>
    </item>
    <item>
      <title>Re: EFI Boot Device Configuration</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-boot-device-configuration/m-p/4681693#M6747</link>
      <description>See also&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1435278" target="_blank"&gt;http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1435278&lt;/A&gt;</description>
      <pubDate>Wed, 01 Sep 2010 05:57:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-boot-device-configuration/m-p/4681693#M6747</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2010-09-01T05:57:05Z</dc:date>
    </item>
    <item>
      <title>Re: EFI Boot Device Configuration</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-boot-device-configuration/m-p/4681694#M6748</link>
      <description>Between answering questions for a case I opened with support and reviewing various other threads based on the output of errors I got when booting, I found a partial if not full solution. Basically, I determined that the disk was in good shape, and that somehow booting needed something - it was this:&lt;BR /&gt;&lt;BR /&gt;1. at the efi shell, connected with the device that had my data... fsx: &lt;BR /&gt;&lt;BR /&gt;2. issued the command 'hpux -lq' &lt;BR /&gt;&lt;BR /&gt;where normally, it had been, 'hpux'&lt;BR /&gt;&lt;BR /&gt;More to do on this, but at least we booted!&lt;BR /&gt;&lt;BR /&gt;RC Park</description>
      <pubDate>Wed, 01 Sep 2010 22:06:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-boot-device-configuration/m-p/4681694#M6748</guid>
      <dc:creator>RC Park</dc:creator>
      <dc:date>2010-09-01T22:06:40Z</dc:date>
    </item>
    <item>
      <title>Re: EFI Boot Device Configuration</title>
      <link>https://community.hpe.com/t5/integrity-servers/efi-boot-device-configuration/m-p/4681695#M6749</link>
      <description>"lq" is used to boot in quorum mode when one of your boot disk failed ( if you have 2 disk in vg00)&lt;BR /&gt;&lt;BR /&gt;are you sure this solved your issue?&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Sep 2010 05:37:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/integrity-servers/efi-boot-device-configuration/m-p/4681695#M6749</guid>
      <dc:creator>SoorajCleris</dc:creator>
      <dc:date>2010-09-02T05:37:38Z</dc:date>
    </item>
  </channel>
</rss>

