<?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: lvlnboot in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lvlnboot/m-p/4196543#M689802</link>
    <description>Most probably someone used the command manually. First lvlnboot -v then /usr/sbin/lvlnboot -v.&lt;BR /&gt;&lt;BR /&gt;If you do it again manually, you could recreate it.&lt;BR /&gt;&lt;BR /&gt;Other reason may be there was ignite backup at that time. &lt;BR /&gt;&lt;BR /&gt;rgds.</description>
    <pubDate>Tue, 13 May 2008 09:17:01 GMT</pubDate>
    <dc:creator>Rasheed Tamton</dc:creator>
    <dc:date>2008-05-13T09:17:01Z</dc:date>
    <item>
      <title>lvlnboot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvlnboot/m-p/4196538#M689797</link>
      <description>All of a sudden I got this entries in the syslog :-&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;May 13 16:19:01 server vmunix: 0/2/1/0.1.0.0.0.0 tgt&lt;BR /&gt;May 13 16:19:01 server vmunix: 0/2/1/0.1.0.255.0.0 tgt&lt;BR /&gt;May 13 16:19:01 server vmunix: 0/2/1/0.1.0.0.0.0.0 sctl&lt;BR /&gt;May 13 16:19:01 server vmunix: 0/2/1/0.1.0.255.0.0.0 sctl&lt;BR /&gt;May 13 16:19:01 server vmunix: 0/2/1/0.1.0.0.0.0.1 sdisk&lt;BR /&gt;May 13 16:19:01 server vmunix: 0/4/1/0.1.0.0.0.0 tgt&lt;BR /&gt;May 13 16:19:01 server vmunix: 0/4/1/0.1.0.255.0.0 tgt&lt;BR /&gt;May 13 16:19:01 server vmunix: 0/4/1/0.1.0.0.0.0.0 sctl&lt;BR /&gt;May 13 16:19:01 server vmunix: 0/4/1/0.1.0.255.0.0.0 sctl&lt;BR /&gt;May 13 16:19:01 server vmunix: 0/4/1/0.1.0.0.0.0.1 sdisk&lt;BR /&gt;May 13 16:19:46 server LVM[28673]: lvlnboot -v&lt;BR /&gt;May 13 16:20:06 server LVM[28741]: /usr/sbin/lvlnboot -v&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Can anyone tell me what is happening? I didn't do anything on the server.</description>
      <pubDate>Tue, 13 May 2008 08:12:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvlnboot/m-p/4196538#M689797</guid>
      <dc:creator>dctw</dc:creator>
      <dc:date>2008-05-13T08:12:22Z</dc:date>
    </item>
    <item>
      <title>Re: lvlnboot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvlnboot/m-p/4196539#M689798</link>
      <description>These are normal messages and there is absolutely nothing to worry about.&lt;BR /&gt;&lt;BR /&gt;Was there any OS Backup going on or someone executed ioscan etc ??</description>
      <pubDate>Tue, 13 May 2008 08:18:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvlnboot/m-p/4196539#M689798</guid>
      <dc:creator>Mridul Shrivastava</dc:creator>
      <dc:date>2008-05-13T08:18:36Z</dc:date>
    </item>
    <item>
      <title>Re: lvlnboot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvlnboot/m-p/4196540#M689799</link>
      <description>We didn't do anything.&lt;BR /&gt;Nor having ioscan or backup on the server.</description>
      <pubDate>Tue, 13 May 2008 08:21:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvlnboot/m-p/4196540#M689799</guid>
      <dc:creator>dctw</dc:creator>
      <dc:date>2008-05-13T08:21:00Z</dc:date>
    </item>
    <item>
      <title>Re: lvlnboot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvlnboot/m-p/4196541#M689800</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Check weather any cron script is not running for ioscan or lvlnboot.&lt;BR /&gt;&lt;BR /&gt;Else it is normal it some times Hp diag tool also the few commands to check the errors.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Avinash</description>
      <pubDate>Tue, 13 May 2008 08:38:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvlnboot/m-p/4196541#M689800</guid>
      <dc:creator>Avinash Agarkar</dc:creator>
      <dc:date>2008-05-13T08:38:32Z</dc:date>
    </item>
    <item>
      <title>Re: lvlnboot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvlnboot/m-p/4196542#M689801</link>
      <description>Maybe you opened SAM's disk section?&lt;BR /&gt;&lt;BR /&gt;SAM will gather some information - any LVM command used will be recorded in syslog.</description>
      <pubDate>Tue, 13 May 2008 08:47:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvlnboot/m-p/4196542#M689801</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-05-13T08:47:07Z</dc:date>
    </item>
    <item>
      <title>Re: lvlnboot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvlnboot/m-p/4196543#M689802</link>
      <description>Most probably someone used the command manually. First lvlnboot -v then /usr/sbin/lvlnboot -v.&lt;BR /&gt;&lt;BR /&gt;If you do it again manually, you could recreate it.&lt;BR /&gt;&lt;BR /&gt;Other reason may be there was ignite backup at that time. &lt;BR /&gt;&lt;BR /&gt;rgds.</description>
      <pubDate>Tue, 13 May 2008 09:17:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvlnboot/m-p/4196543#M689802</guid>
      <dc:creator>Rasheed Tamton</dc:creator>
      <dc:date>2008-05-13T09:17:01Z</dc:date>
    </item>
    <item>
      <title>Re: lvlnboot</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvlnboot/m-p/4196544#M689803</link>
      <description>And the first lines (about vmunix) mean that the server has detected new hardware, and looking atthe hardware paths, it is on a SAN.</description>
      <pubDate>Wed, 14 May 2008 05:43:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvlnboot/m-p/4196544#M689803</guid>
      <dc:creator>Wim Rombauts</dc:creator>
      <dc:date>2008-05-14T05:43:51Z</dc:date>
    </item>
  </channel>
</rss>

