<?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: Lost Volume Groups in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608004#M234002</link>
    <description>Just want to make few points.&lt;BR /&gt;&lt;BR /&gt;You would see vg entry in /etc/lvmtab only when there is corresponding vg conf file in /etc/lvmconf . During system startup vgscan is run to read these conf files for each vgs and it also queries the pvs whcih are supposed to be under those vgs. Then it update the conf file if required.&lt;BR /&gt;&lt;BR /&gt;As said by Raj , we have to make sure all the required things for those VG are in the system like physical disks ( EMC disks ), vg group file etc..&lt;BR /&gt;&lt;BR /&gt;It is very rare that the LVM header from those disks ( 100 !!! ) are overwritten . &lt;BR /&gt;Maybe something is wrong at EMC side if you are not getting any single LUN from EMC!!!Hence you have to verify them first using ioscan then pvdisplay . Check the vg config files in /etc/lvmconf&lt;BR /&gt;&lt;BR /&gt;You have to be very careful and look around to make sure all before doing anything.&lt;BR /&gt;&lt;BR /&gt;Let us know if you have doubts or confusion.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Sat, 20 Aug 2005 15:12:26 GMT</pubDate>
    <dc:creator>Sameer_Nirmal</dc:creator>
    <dc:date>2005-08-20T15:12:26Z</dc:date>
    <item>
      <title>Lost Volume Groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3607999#M233997</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;Recently I have been doing Nclass Upgrades from 11.0 &amp;gt; 11.11 running Oracle and Peoplesoft. Very good luck so far with doing upgrades v.s cold install. Here is what has happened this time.&lt;BR /&gt;&lt;BR /&gt;1) I shutdown and installed 2 new larger internal disks for the OS. (all went well)&lt;BR /&gt;&lt;BR /&gt;2) Booted off of the ignite tape to resize filesystes. (Went well)&lt;BR /&gt;&lt;BR /&gt;3) Let the system rebuild and reboot. (all went well)&lt;BR /&gt;&lt;BR /&gt;when the system came up, I am missing a few volume groups for my oracle data. All of the root vg00 is fine.&lt;BR /&gt;&lt;BR /&gt;I am missing: /dev/vgfinap and /dev/vgfindb&lt;BR /&gt;&lt;BR /&gt;I dont see the entry in /etc/lvmtab anymore for these 2 volume groups. My /etc/fstab looks OK. The disks in these volume groups are a bunch of EMC fibre attached disks. Each one is populated on ? 18 Gbyte disk, so there are probably somewhere around 100 disks. Any idea how I can start to get my disks back. I am sure my data on the disks are still OK.&lt;BR /&gt;&lt;BR /&gt;I proceeded to continue with the upgrade to 11.11. That seems to be going OK so far. I just need to get my disks and vg's back.&lt;BR /&gt;&lt;BR /&gt;EMERGENCY: Production Oracle Upgrade In Progress.</description>
      <pubDate>Sat, 20 Aug 2005 13:59:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3607999#M233997</guid>
      <dc:creator>Nobody's Hero</dc:creator>
      <dc:date>2005-08-20T13:59:15Z</dc:date>
    </item>
    <item>
      <title>Re: Lost Volume Groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608000#M233998</link>
      <description>Hi,&lt;BR /&gt;maby vgscan will help you</description>
      <pubDate>Sat, 20 Aug 2005 14:22:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608000#M233998</guid>
      <dc:creator>Slawomir Gora</dc:creator>
      <dc:date>2005-08-20T14:22:27Z</dc:date>
    </item>
    <item>
      <title>Re: Lost Volume Groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608001#M233999</link>
      <description>Already tried that..no go....&lt;BR /&gt;&lt;BR /&gt;vgimport maybe ????</description>
      <pubDate>Sat, 20 Aug 2005 14:23:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608001#M233999</guid>
      <dc:creator>Nobody's Hero</dc:creator>
      <dc:date>2005-08-20T14:23:40Z</dc:date>
    </item>
    <item>
      <title>Re: Lost Volume Groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608002#M234000</link>
      <description>Hi Robert,&lt;BR /&gt;Do you know which disks were for that two Volume group , i.e vgfinap and vgfindb.&lt;BR /&gt;&lt;BR /&gt;If you know the disks device number , u can check as follows:&lt;BR /&gt;&lt;BR /&gt;1. iocan -fnC disk  [ check for that disks are visible by the system]. &lt;BR /&gt;&lt;BR /&gt;2. Check if the vg directory is present in the dev directory , with the group file , else need to create, with mknod.&lt;BR /&gt;&lt;BR /&gt;3. use # vgimport /dev/vgfinap /dev/dsk/cxtxdx /dev/dsk/cytydy  .. (Total no of disks contains for that vg) &lt;BR /&gt;&lt;BR /&gt;4. Activate the vg.&lt;BR /&gt;&lt;BR /&gt;5. Add entry in /etc/fstab. and mount the Filesystems. [ You need to have details of previous bdf output, to match lvol-&amp;gt; to fs.]&lt;BR /&gt;Hope this will help you to analyse what caused the problem and to get back the vg.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;RajD.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 20 Aug 2005 14:31:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608002#M234000</guid>
      <dc:creator>Raj D.</dc:creator>
      <dc:date>2005-08-20T14:31:30Z</dc:date>
    </item>
    <item>
      <title>Re: Lost Volume Groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608003#M234001</link>
      <description>Run vgcfgrestore -l -n &lt;VG-NAME&gt; for those missing vgs. If the Vg's lvm conf file is up to date , then it should show the disks under VG.&lt;BR /&gt;Check all those EMC luns using pvdisplay&lt;BR /&gt;&lt;BR /&gt;It may be posible that LVM header has been overwritten or corrupted on those disks.&lt;BR /&gt;Just we do while adding new disks, you can use vgcfgrestore -n &lt;VG-NAME&gt; /dev/rdsk/c?t?d?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/VG-NAME&gt;&lt;/VG-NAME&gt;</description>
      <pubDate>Sat, 20 Aug 2005 14:41:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608003#M234001</guid>
      <dc:creator>Sameer_Nirmal</dc:creator>
      <dc:date>2005-08-20T14:41:59Z</dc:date>
    </item>
    <item>
      <title>Re: Lost Volume Groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608004#M234002</link>
      <description>Just want to make few points.&lt;BR /&gt;&lt;BR /&gt;You would see vg entry in /etc/lvmtab only when there is corresponding vg conf file in /etc/lvmconf . During system startup vgscan is run to read these conf files for each vgs and it also queries the pvs whcih are supposed to be under those vgs. Then it update the conf file if required.&lt;BR /&gt;&lt;BR /&gt;As said by Raj , we have to make sure all the required things for those VG are in the system like physical disks ( EMC disks ), vg group file etc..&lt;BR /&gt;&lt;BR /&gt;It is very rare that the LVM header from those disks ( 100 !!! ) are overwritten . &lt;BR /&gt;Maybe something is wrong at EMC side if you are not getting any single LUN from EMC!!!Hence you have to verify them first using ioscan then pvdisplay . Check the vg config files in /etc/lvmconf&lt;BR /&gt;&lt;BR /&gt;You have to be very careful and look around to make sure all before doing anything.&lt;BR /&gt;&lt;BR /&gt;Let us know if you have doubts or confusion.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 20 Aug 2005 15:12:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608004#M234002</guid>
      <dc:creator>Sameer_Nirmal</dc:creator>
      <dc:date>2005-08-20T15:12:26Z</dc:date>
    </item>
    <item>
      <title>Re: Lost Volume Groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608005#M234003</link>
      <description>Try to issue this command on all the disks:&lt;BR /&gt;&lt;BR /&gt;echo 0x2010?2X|adb /dev/dsk/cXtYdZ|expand|tr -d " "|sed "s/2010:/VGID /"&lt;BR /&gt;&lt;BR /&gt;You should see the VGID of each disk and it might be helpfull to see which disks belong toget her to which VG. The info is taken from the kernel itself, by supplying the debugger specific offset.&lt;BR /&gt;&lt;BR /&gt;Alex.</description>
      <pubDate>Sat, 20 Aug 2005 15:38:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608005#M234003</guid>
      <dc:creator>Alex Lavrov.</dc:creator>
      <dc:date>2005-08-20T15:38:09Z</dc:date>
    </item>
    <item>
      <title>Re: Lost Volume Groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608006#M234004</link>
      <description>Take a look at syslog and also /etc/rc.log to see if volume groups failed to activate because of missing disks. When the system boots up, each volume group is activated but a failure there will not remove the /dev/directories. Something else has happened either during the backup or the recovery steps. You need to look carefully at the Ignite log when you created the tape. Hopefully, you used the -v option and saved a copy of this file on another system. Ignite keeps a log of the last make_tape_recovery in the file:&lt;BR /&gt; &lt;BR /&gt;/var/opt/ignite/recovery/latest/recovery.log&lt;BR /&gt; &lt;BR /&gt;However, to recover the missing volume groups, you'll need import the missing volumes and for that, you need a vgdisplay of the lvol names (unless they are all default names lvol1, lvol2, lvol3, ...). Start by creating the missing directories and re-creating the group device file. You'll need to choose the group minor number either from previous documentation or by finding a unique number from the command:&lt;BR /&gt; &lt;BR /&gt;ll /dev/*/group&lt;BR /&gt; &lt;BR /&gt;Then use the vgimport command, but check the /etc/lvmconf directory for the last mapfiles.</description>
      <pubDate>Sat, 20 Aug 2005 17:17:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608006#M234004</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-08-20T17:17:26Z</dc:date>
    </item>
    <item>
      <title>Re: Lost Volume Groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608007#M234005</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You can plug in the old OS disks if still available to find out these details related to these VG's. Then you can use the vgimport command to import these VG's. Are these EMC disks visible to system in ioscan.&lt;BR /&gt;&lt;BR /&gt;Data indeed should be intact and importing back will solve the issue.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Devender</description>
      <pubDate>Mon, 22 Aug 2005 00:09:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608007#M234005</guid>
      <dc:creator>Devender Khatana</dc:creator>
      <dc:date>2005-08-22T00:09:54Z</dc:date>
    </item>
    <item>
      <title>Re: Lost Volume Groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608008#M234006</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Normely after a upgrade SAN device must be propegated again over the system.&lt;BR /&gt;Try insf -e to make the disk visible. If not check at the EMC side if the node is viseble.&lt;BR /&gt;&lt;BR /&gt;grtz. Mark</description>
      <pubDate>Mon, 22 Aug 2005 00:27:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608008#M234006</guid>
      <dc:creator>Mark Nieuwboer</dc:creator>
      <dc:date>2005-08-22T00:27:20Z</dc:date>
    </item>
    <item>
      <title>Re: Lost Volume Groups</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608009#M234007</link>
      <description>Hi,&lt;BR /&gt;Try to use this commands:&lt;BR /&gt;#symcfg discover&lt;BR /&gt;#powermt check&lt;BR /&gt;#powermt config&lt;BR /&gt;#powermt display&lt;BR /&gt;#powermt save</description>
      <pubDate>Mon, 22 Aug 2005 00:41:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lost-volume-groups/m-p/3608009#M234007</guid>
      <dc:creator>morganelan</dc:creator>
      <dc:date>2005-08-22T00:41:07Z</dc:date>
    </item>
  </channel>
</rss>

