<?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: error messages appear in syslog.log using XP512 in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/error-messages-appear-in-syslog-log-using-xp512/m-p/4053839#M24604</link>
    <description>the first 2 digits after the device 0x1f=31 is the driver of the device i.e. sdisk. The following 2 digits 0f=15 is the instance number of the device. Hence you are seeing most of the devices for this XP512 on path c15t#d# have timed out. However, they have eventually come back online. You might want to investigate the reason for such timeout. Could be san issue, pv timeout value, XP controller busy/bottleneck etc.</description>
    <pubDate>Mon, 13 Aug 2007 21:43:00 GMT</pubDate>
    <dc:creator>tkc</dc:creator>
    <dc:date>2007-08-13T21:43:00Z</dc:date>
    <item>
      <title>error messages appear in syslog.log using XP512</title>
      <link>https://community.hpe.com/t5/disk-enclosures/error-messages-appear-in-syslog-log-using-xp512/m-p/4053837#M24602</link>
      <description>dear all,&lt;BR /&gt;i've got following error messages in syslog.log continually:&lt;BR /&gt;Jul 29 05:16:41 emis3 vmunix: LVM: Recovered Path (device 0x1f0f0000) to PV 0 in&lt;BR /&gt; VG 1.&lt;BR /&gt;Jul 29 05:16:41 emis3 vmunix: LVM: vg[1]: pvnum=1 (dev_t=0x1f0f0100) is POWERFAI&lt;BR /&gt;LED&lt;BR /&gt;Jul 29 05:16:41 emis3 vmunix: LVM: vg[1]: pvnum=2 (dev_t=0x1f0f0200) is POWERFAI&lt;BR /&gt;LED&lt;BR /&gt;Jul 29 05:16:41 emis3 vmunix: LVM: vg[1]: pvnum=3 (dev_t=0x1f0f0300) is POWERFAI&lt;BR /&gt;LED&lt;BR /&gt;Jul 29 05:16:47 emis3 inetd[17748]: registrar/tcp: Connection from emis3 (172.24&lt;BR /&gt;.1.11) at Sun Jul 29 05:16:47 2007&lt;BR /&gt;Jul 29 05:17:04 emis3 vmunix: LVM: Restored PV 1 to VG 1.&lt;BR /&gt;Jul 29 05:17:32 emis3 vmunix: LVM: Restored PV 2 to VG 1.&lt;BR /&gt;Jul 29 05:18:00 emis3 vmunix: LVM: Restored PV 3 to VG 1.&lt;BR /&gt;Jul 29 05:18:28 emis3 vmunix: LVM: Recovered Path (device 0x1f0f0000) to PV 0 in&lt;BR /&gt; VG 1.&lt;BR /&gt;Jul 29 05:18:28 emis3 vmunix: LVM: Recovered Path (device 0x1f0f0100) to PV 1 in&lt;BR /&gt; VG 1.&lt;BR /&gt;Jul 29 05:18:28 emis3 vmunix: LVM: Recovered Path (device 0x1f0f0200) to PV 2 in&lt;BR /&gt; VG 1.&lt;BR /&gt;Jul 29 05:18:28 emis3 vmunix: LVM: Recovered Path (device 0x1f0f0300) to PV 3 in&lt;BR /&gt; VG 1.&lt;BR /&gt;Jul 29 05:18:28 emis3 vmunix: LVM: Restored PV 0 to VG 1.&lt;BR /&gt;Jul 29 05:18:33 emis3 vmunix: LVM: Recovered Path (device 0x1f0f0000) to PV 0 in&lt;BR /&gt; VG 1.&lt;BR /&gt;Jul 29 05:18:33 emis3 vmunix: LVM: vg[1]: pvnum=1 (dev_t=0x1f0f0100) is POWERFAI&lt;BR /&gt;LED&lt;BR /&gt;Jul 29 05:18:33 emis3 vmunix: LVM: vg[1]: pvnum=2 (dev_t=0x1f0f0200) is POWERFAI&lt;BR /&gt;LED&lt;BR /&gt;Jul 29 05:18:33 emis3 vmunix: LVM: vg[1]: pvnum=3 (dev_t=0x1f0f0300) is POWERFAI&lt;BR /&gt;LED&lt;BR /&gt;Jul 29 05:18:47 emis3 inetd[17798]: registrar/tcp: Connection from emis3 (172.24&lt;BR /&gt;.1.11) at Sun Jul 29 05:18:47 2007&lt;BR /&gt;Jul 29 05:18:56 emis3 vmunix: LVM: Restored PV 1 to VG 1.&lt;BR /&gt;Jul 29 05:19:24 emis3 vmunix: LVM: Restored PV 2 to VG 1.&lt;BR /&gt;Jul 29 05:19:52 emis3 vmunix: LVM: Restored PV 3 to VG 1.&lt;BR /&gt;Jul 29 05:20:20 emis3 vmunix: LVM: Recovered Path (device 0x1f0f0000) to PV 0 in&lt;BR /&gt; VG 1.&lt;BR /&gt;Jul 29 05:20:20 emis3 vmunix: LVM: Recovered Path (device 0x1f0f0100) to PV 1 in&lt;BR /&gt; VG 1.&lt;BR /&gt;Jul 29 05:20:20 emis3 vmunix: LVM: Recovered Path (device 0x1f0f0200) to PV 2 in&lt;BR /&gt; VG 1.&lt;BR /&gt;Jul 29 05:20:20 emis3 vmunix: LVM: Recovered Path (device 0x1f0f0300) to PV 3 in&lt;BR /&gt; VG 1.&lt;BR /&gt;Jul 29 05:20:20 emis3 vmunix: LVM: Restored PV 0 to VG 1.&lt;BR /&gt;&lt;BR /&gt;what could be the causes?&lt;BR /&gt;&lt;BR /&gt;thanks a lot</description>
      <pubDate>Mon, 13 Aug 2007 05:54:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/error-messages-appear-in-syslog-log-using-xp512/m-p/4053837#M24602</guid>
      <dc:creator>stephen peng</dc:creator>
      <dc:date>2007-08-13T05:54:17Z</dc:date>
    </item>
    <item>
      <title>Re: error messages appear in syslog.log using XP512</title>
      <link>https://community.hpe.com/t5/disk-enclosures/error-messages-appear-in-syslog-log-using-xp512/m-p/4053838#M24603</link>
      <description>&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=367067&amp;amp;admit=-682735245+1187007243871+28353475" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=367067&amp;amp;admit=-682735245+1187007243871+28353475&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1144626" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1144626&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 13 Aug 2007 07:18:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/error-messages-appear-in-syslog-log-using-xp512/m-p/4053838#M24603</guid>
      <dc:creator>AwadheshPandey</dc:creator>
      <dc:date>2007-08-13T07:18:10Z</dc:date>
    </item>
    <item>
      <title>Re: error messages appear in syslog.log using XP512</title>
      <link>https://community.hpe.com/t5/disk-enclosures/error-messages-appear-in-syslog-log-using-xp512/m-p/4053839#M24604</link>
      <description>the first 2 digits after the device 0x1f=31 is the driver of the device i.e. sdisk. The following 2 digits 0f=15 is the instance number of the device. Hence you are seeing most of the devices for this XP512 on path c15t#d# have timed out. However, they have eventually come back online. You might want to investigate the reason for such timeout. Could be san issue, pv timeout value, XP controller busy/bottleneck etc.</description>
      <pubDate>Mon, 13 Aug 2007 21:43:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/error-messages-appear-in-syslog-log-using-xp512/m-p/4053839#M24604</guid>
      <dc:creator>tkc</dc:creator>
      <dc:date>2007-08-13T21:43:00Z</dc:date>
    </item>
    <item>
      <title>Re: error messages appear in syslog.log using XP512</title>
      <link>https://community.hpe.com/t5/disk-enclosures/error-messages-appear-in-syslog-log-using-xp512/m-p/4053840#M24605</link>
      <description>another thing, look at the ems events captured in the file /var/opt/resmon/log/event.log. That will probably show you all the events related to the messages you saw in the syslog.log.</description>
      <pubDate>Mon, 13 Aug 2007 21:47:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/error-messages-appear-in-syslog-log-using-xp512/m-p/4053840#M24605</guid>
      <dc:creator>tkc</dc:creator>
      <dc:date>2007-08-13T21:47:34Z</dc:date>
    </item>
  </channel>
</rss>

