<?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: Read_efi_hdr: physio failed in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/read-efi-hdr-physio-failed/m-p/4022790#M746005</link>
    <description>Hi Rubin,&lt;BR /&gt;&lt;BR /&gt;Explaination for : read_efi_hdr: physio failed is..&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Command "ioscan -e" which display the EFI device path when available.&lt;BR /&gt;&lt;BR /&gt;This commands leaves the devices partially open. Accessing a disk in this state will result in the syslog message.&lt;BR /&gt;&lt;BR /&gt;This is a known issue and fixed with Patch: PHKL_33432 superseeded by PHKL_34588&lt;BR /&gt;&lt;BR /&gt;Now about Floating exception(coredump).. in one of my case installing the FSLibEnh patch resolved the issue..&lt;BR /&gt;&lt;BR /&gt;FSLibEnh     B.11.23.07   libc enhancemnts for VxFS4.1 and 5.0&lt;BR /&gt;  &lt;BR /&gt;from Sep 2006 media&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Prashanth&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Prashanth</description>
    <pubDate>Tue, 19 Jun 2007 14:46:49 GMT</pubDate>
    <dc:creator>Prashanth.D.S</dc:creator>
    <dc:date>2007-06-19T14:46:49Z</dc:date>
    <item>
      <title>Read_efi_hdr: physio failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/read-efi-hdr-physio-failed/m-p/4022789#M746004</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;On a rx8640 running HP-UX 11.23 we are seeing some weird messages pop up in dmesg. These messages happen when we do an 'ioscan -fn  &amp;amp;&amp;amp; insf -e', which incidentally takes much longer than normal (2 hours).&lt;BR /&gt;&lt;BR /&gt;The message is:&lt;BR /&gt;&lt;BR /&gt;read_efi_hdr: physio failed&lt;BR /&gt;&lt;BR /&gt;We started looking at dmesg because the scan took so much longer than usual; it might be unrelated.&lt;BR /&gt;&lt;BR /&gt;Also (and again maybe completely unrelated) idisk coredumps when trying to verify volumes on the SAN. Is that normal behaviour? I could imagine this not working however the coredump worries me a little:&lt;BR /&gt;&lt;BR /&gt;# idisk -v /dev/rdsk/c24t8d5&lt;BR /&gt;Floating exception(coredump)</description>
      <pubDate>Tue, 19 Jun 2007 08:50:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/read-efi-hdr-physio-failed/m-p/4022789#M746004</guid>
      <dc:creator>Rubin Simons</dc:creator>
      <dc:date>2007-06-19T08:50:34Z</dc:date>
    </item>
    <item>
      <title>Re: Read_efi_hdr: physio failed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/read-efi-hdr-physio-failed/m-p/4022790#M746005</link>
      <description>Hi Rubin,&lt;BR /&gt;&lt;BR /&gt;Explaination for : read_efi_hdr: physio failed is..&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Command "ioscan -e" which display the EFI device path when available.&lt;BR /&gt;&lt;BR /&gt;This commands leaves the devices partially open. Accessing a disk in this state will result in the syslog message.&lt;BR /&gt;&lt;BR /&gt;This is a known issue and fixed with Patch: PHKL_33432 superseeded by PHKL_34588&lt;BR /&gt;&lt;BR /&gt;Now about Floating exception(coredump).. in one of my case installing the FSLibEnh patch resolved the issue..&lt;BR /&gt;&lt;BR /&gt;FSLibEnh     B.11.23.07   libc enhancemnts for VxFS4.1 and 5.0&lt;BR /&gt;  &lt;BR /&gt;from Sep 2006 media&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Prashanth&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Prashanth</description>
      <pubDate>Tue, 19 Jun 2007 14:46:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/read-efi-hdr-physio-failed/m-p/4022790#M746005</guid>
      <dc:creator>Prashanth.D.S</dc:creator>
      <dc:date>2007-06-19T14:46:49Z</dc:date>
    </item>
  </channel>
</rss>

