<?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: LV missing after server's unexpected shutdown in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lv-missing-after-server-s-unexpected-shutdown/m-p/4592293#M553003</link>
    <description>you can try running vgchid on the PVs&lt;BR /&gt;Then try to import using following command..&lt;BR /&gt;#vgimport -v -s -m &lt;MAPFILENAME&gt; VGName&lt;BR /&gt;&lt;BR /&gt;you can run this command only if you had taken map file using -s option. &lt;BR /&gt;&lt;/MAPFILENAME&gt;</description>
    <pubDate>Tue, 02 Mar 2010 14:20:35 GMT</pubDate>
    <dc:creator>kashyapi</dc:creator>
    <dc:date>2010-03-02T14:20:35Z</dc:date>
    <item>
      <title>LV missing after server's unexpected shutdown</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lv-missing-after-server-s-unexpected-shutdown/m-p/4592289#M552999</link>
      <description>Hi, collegues&lt;BR /&gt;&lt;BR /&gt;I have following trouble: &lt;BR /&gt;&lt;BR /&gt;Server halted due to machine check, after reboot I try to activate volume group with Oracle data on it - it have ~240 LVs.&lt;BR /&gt;&lt;BR /&gt;I do "vgimport -m vgdb1.map -f vgdb1.pv vgdb1"&lt;BR /&gt;&lt;BR /&gt;For some LVs vgimport complains:&lt;BR /&gt;&lt;BR /&gt;Logical Volume is not defined on any physical volume.&lt;BR /&gt;"/dev/vgdb1/lv259" is missing Physical Volumes.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I checked PVs - it still correct, after reboot pathes and DSF names are still unchanged.&lt;BR /&gt;&lt;BR /&gt;Data on theese PVs appears by synchronization via HP XP CA, it seems that machine shutdown has led to crash of internal LVM structures on PVs. I wonder - can I recover from this failure or I have to resync devices? For some reason I dont want to do this.</description>
      <pubDate>Mon, 01 Mar 2010 08:56:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lv-missing-after-server-s-unexpected-shutdown/m-p/4592289#M552999</guid>
      <dc:creator>Maxim Yakimenko</dc:creator>
      <dc:date>2010-03-01T08:56:34Z</dc:date>
    </item>
    <item>
      <title>Re: LV missing after server's unexpected shutdown</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lv-missing-after-server-s-unexpected-shutdown/m-p/4592290#M553000</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;check the PV with pvdisplay.&lt;BR /&gt;&lt;BR /&gt;mikap</description>
      <pubDate>Mon, 01 Mar 2010 09:59:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lv-missing-after-server-s-unexpected-shutdown/m-p/4592290#M553000</guid>
      <dc:creator>Michal Kapalka (mikap)</dc:creator>
      <dc:date>2010-03-01T09:59:39Z</dc:date>
    </item>
    <item>
      <title>Re: LV missing after server's unexpected shutdown</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lv-missing-after-server-s-unexpected-shutdown/m-p/4592291#M553001</link>
      <description>Well, I did pvdisplay -v on first PV of group and found that info about some LVs extents located on this PV is gone. What's next? As I understand I have only one option - resync?</description>
      <pubDate>Mon, 01 Mar 2010 11:39:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lv-missing-after-server-s-unexpected-shutdown/m-p/4592291#M553001</guid>
      <dc:creator>Maxim Yakimenko</dc:creator>
      <dc:date>2010-03-01T11:39:41Z</dc:date>
    </item>
    <item>
      <title>Re: LV missing after server's unexpected shutdown</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lv-missing-after-server-s-unexpected-shutdown/m-p/4592292#M553002</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;normally, you should check :&lt;BR /&gt;&lt;BR /&gt;1. chcek MP ( vfp / event log )&lt;BR /&gt;2. /etc/rc.log&lt;BR /&gt;....&lt;BR /&gt;&lt;BR /&gt;3. dmesg &lt;BR /&gt;2. ioscan -fn |grep NO_HW&lt;BR /&gt;3. grep EMS /var/adm/syslog/syslog.log&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;if you have som problem with the VG... &lt;BR /&gt;&lt;BR /&gt;pvdisplay ( diskinfo ... )&lt;BR /&gt;&lt;BR /&gt;- what is your disk configuration ??&lt;BR /&gt;&lt;BR /&gt;check the disk on the Storage for some errors, you could also use xpinfo to gather more information.&lt;BR /&gt;&lt;BR /&gt;....&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;mikap&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Mar 2010 11:49:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lv-missing-after-server-s-unexpected-shutdown/m-p/4592292#M553002</guid>
      <dc:creator>Michal Kapalka (mikap)</dc:creator>
      <dc:date>2010-03-01T11:49:13Z</dc:date>
    </item>
    <item>
      <title>Re: LV missing after server's unexpected shutdown</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lv-missing-after-server-s-unexpected-shutdown/m-p/4592293#M553003</link>
      <description>you can try running vgchid on the PVs&lt;BR /&gt;Then try to import using following command..&lt;BR /&gt;#vgimport -v -s -m &lt;MAPFILENAME&gt; VGName&lt;BR /&gt;&lt;BR /&gt;you can run this command only if you had taken map file using -s option. &lt;BR /&gt;&lt;/MAPFILENAME&gt;</description>
      <pubDate>Tue, 02 Mar 2010 14:20:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lv-missing-after-server-s-unexpected-shutdown/m-p/4592293#M553003</guid>
      <dc:creator>kashyapi</dc:creator>
      <dc:date>2010-03-02T14:20:35Z</dc:date>
    </item>
  </channel>
</rss>

