<?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: message from dmesg in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/message-from-dmesg/m-p/3070873#M140619</link>
    <description>5 LUNS in vg8. I'd look either for a controller&lt;BR /&gt;or a storage device fault (can be checked if you have more LUNs from this storage used ).&lt;BR /&gt;"ioscan -fn" to see state (NO_HW,CLAIMED,UNKNOWN).Seek "scsi" errors in syslog.log , if found could also lead to physicall / logical scsi errors (ie termination,cable,bad set scsi id).&lt;BR /&gt;&lt;BR /&gt;Usually most storage arrays provide specific commands to check storage state.&lt;BR /&gt;&lt;BR /&gt;Zeev</description>
    <pubDate>Mon, 15 Sep 2003 10:58:54 GMT</pubDate>
    <dc:creator>Zeev Schultz</dc:creator>
    <dc:date>2003-09-15T10:58:54Z</dc:date>
    <item>
      <title>message from dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/message-from-dmesg/m-p/3070868#M140614</link>
      <description>Hi All, i received these messagge by dmesg &lt;BR /&gt;i think they can be very dangerous &lt;BR /&gt;anyone can help me ?&lt;BR /&gt;what do they mean ?&lt;BR /&gt;&lt;BR /&gt;thanks in advance&lt;BR /&gt;Fab&lt;BR /&gt;&lt;BR /&gt;Major 09/15/03 02:17:54 pemihp03 UX10/dmesg OS LVM LVM: Path (device 0x1f039000) to PV 13 in VG 8 Failed!&lt;BR /&gt;Major 09/15/03 02:17:54 pemihp03 UX10/dmesg OS LVM LVM: Path (device 0x1f019300) to PV 16 in VG 8 Failed!&lt;BR /&gt;Major 09/15/03 02:17:54 pemihp03 UX10/dmesg OS LVM LVM: Path (device 0x1f039100) to PV 14 in VG 8 Failed!&lt;BR /&gt;Major 09/15/03 02:17:54 pemihp03 UX10/dmesg OS LVM LVM: Path (device 0x1f005400) to PV 0 in VG 8 Failed!&lt;BR /&gt;Major 09/15/03 02:17:54 pemihp03 UX10/dmesg OS LVM LVM: Path (device 0x1f005500) to PV 1 in VG 8 Failed!&lt;BR /&gt;</description>
      <pubDate>Mon, 15 Sep 2003 07:38:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/message-from-dmesg/m-p/3070868#M140614</guid>
      <dc:creator>linux: ps_mon.cfg</dc:creator>
      <dc:date>2003-09-15T07:38:49Z</dc:date>
    </item>
    <item>
      <title>Re: message from dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/message-from-dmesg/m-p/3070869#M140615</link>
      <description>Looks like you have a hardware issue with a disk controller or SAN switch.  I would expect that a vgdisplay -v of your volume groups might give a little more information</description>
      <pubDate>Mon, 15 Sep 2003 07:47:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/message-from-dmesg/m-p/3070869#M140615</guid>
      <dc:creator>Mark Grant</dc:creator>
      <dc:date>2003-09-15T07:47:25Z</dc:date>
    </item>
    <item>
      <title>Re: message from dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/message-from-dmesg/m-p/3070870#M140616</link>
      <description>Youve lost connection so some of your disks. Contact your storage expert or supplier to investigate ASAP.&lt;BR /&gt;</description>
      <pubDate>Mon, 15 Sep 2003 08:05:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/message-from-dmesg/m-p/3070870#M140616</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2003-09-15T08:05:00Z</dc:date>
    </item>
    <item>
      <title>Re: message from dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/message-from-dmesg/m-p/3070871#M140617</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Could you check the ioscan output&lt;BR /&gt;and look for all the devices with the &lt;BR /&gt;state as "NO_HW".&lt;BR /&gt;&lt;BR /&gt;Is it a Direct attached storage or thru &lt;BR /&gt;SAN switch?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Fenil</description>
      <pubDate>Mon, 15 Sep 2003 08:05:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/message-from-dmesg/m-p/3070871#M140617</guid>
      <dc:creator>Pradeep_3</dc:creator>
      <dc:date>2003-09-15T08:05:17Z</dc:date>
    </item>
    <item>
      <title>Re: message from dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/message-from-dmesg/m-p/3070872#M140618</link>
      <description>You are correct concerning danger.&lt;BR /&gt;&lt;BR /&gt;If connected by fiber, you may get additional info from this command:&lt;BR /&gt;&lt;BR /&gt;fcmsutil /dev/td0&lt;BR /&gt;&lt;BR /&gt;replace td0 by the actual address of the card.&lt;BR /&gt;&lt;BR /&gt;A physical inspection of the fiber card itself for lights, connections and such is warranted, because the hardware folks will ask you that anyway.  Also a look at the lights on the fabric switch and the console for the disk array would be very helpful.&lt;BR /&gt;&lt;BR /&gt;It is possible that the disk admin(hopefully not yourself) has changed zoning or ownership on the disks, or the fabric switch itself has failed.  It depends how you are connected.&lt;BR /&gt;&lt;BR /&gt;Depending on whats actually on those disks, I'd be wary of whether production is going to be normal today.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 15 Sep 2003 10:32:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/message-from-dmesg/m-p/3070872#M140618</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-09-15T10:32:55Z</dc:date>
    </item>
    <item>
      <title>Re: message from dmesg</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/message-from-dmesg/m-p/3070873#M140619</link>
      <description>5 LUNS in vg8. I'd look either for a controller&lt;BR /&gt;or a storage device fault (can be checked if you have more LUNs from this storage used ).&lt;BR /&gt;"ioscan -fn" to see state (NO_HW,CLAIMED,UNKNOWN).Seek "scsi" errors in syslog.log , if found could also lead to physicall / logical scsi errors (ie termination,cable,bad set scsi id).&lt;BR /&gt;&lt;BR /&gt;Usually most storage arrays provide specific commands to check storage state.&lt;BR /&gt;&lt;BR /&gt;Zeev</description>
      <pubDate>Mon, 15 Sep 2003 10:58:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/message-from-dmesg/m-p/3070873#M140619</guid>
      <dc:creator>Zeev Schultz</dc:creator>
      <dc:date>2003-09-15T10:58:54Z</dc:date>
    </item>
  </channel>
</rss>

