<?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 Recreating /etc/lvmtab problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/recreating-etc-lvmtab-problem/m-p/3564676#M622971</link>
    <description>I have a customer who has somehow managed to remove all the volume groups except for /dev/vg00 from the lvmtab.  Either that,  or the file has become corrupted.  Also,  at the same time the controller number of the disk devices (c#1t3d0) for both paths has changed to a different number.  So, who knows what they were up to over there.&lt;BR /&gt;&lt;BR /&gt;I had them strings the /etc/lvmtab file, and as I thought, only /dev/vg00 was in there.&lt;BR /&gt;&lt;BR /&gt;I then had them do a vgscan -a -v -p to see if we could rebuild the /etc/lvmtab file from the lvm headers on the disk.  The /dev/vg* directories and group info are all still there, so I thought this should work?&lt;BR /&gt;&lt;BR /&gt;Here is the output:&lt;BR /&gt;&lt;BR /&gt;vgscan: The physical volume "/dev/dsk/c0t6d0s2" is already recorded in&lt;BR /&gt;the "/etc/lvmtab" file.&lt;BR /&gt;vgscan: The physical volume "/dev/dsk/c3t6d0" is already recorded in the&lt;BR /&gt;"/etc/lvmtab" file.&lt;BR /&gt;Couldn't stat physical volume "/dev/dsk/c1t2d0":&lt;BR /&gt;Invalid argument&lt;BR /&gt;Physical Volume "/dev/dsk/c9t0d0" is not part of a Volume Group&lt;BR /&gt;Physical Volume "/dev/dsk/c14t0d0" is not part of a Volume Group&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;/dev/vg00&lt;BR /&gt;/dev/dsk/c0t6d0s2&lt;BR /&gt;/dev/dsk/c3t6d0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Following Physical Volumes belong to one Volume Group.&lt;BR /&gt;Unable to match these Physical Volumes to a Volume Group.&lt;BR /&gt;Use the vgimport command to complete the process.&lt;BR /&gt;/dev/dsk/c9t0d1&lt;BR /&gt;/dev/dsk/c14t0d1&lt;BR /&gt;&lt;BR /&gt;Following Physical Volumes belong to one Volume Group.&lt;BR /&gt;Unable to match these Physical Volumes to a Volume Group.&lt;BR /&gt;Use the vgimport command to complete the process.&lt;BR /&gt;/dev/dsk/c9t0d2&lt;BR /&gt;/dev/dsk/c14t0d2&lt;BR /&gt;&lt;BR /&gt;Following Physical Volumes belong to one Volume Group.&lt;BR /&gt;Unable to match these Physical Volumes to a Volume Group.&lt;BR /&gt;Use the vgimport command to complete the process.&lt;BR /&gt;/dev/dsk/c9t0d3&lt;BR /&gt;/dev/dsk/c14t0d3&lt;BR /&gt;&lt;BR /&gt;Following Physical Volumes belong to one Volume Group.&lt;BR /&gt;Unable to match these Physical Volumes to a Volume Group.&lt;BR /&gt;Use the vgimport command to complete the process.&lt;BR /&gt;/dev/dsk/c9t0d4&lt;BR /&gt;/dev/dsk/c14t0d4&lt;BR /&gt;&lt;BR /&gt;Following Physical Volumes belong to one Volume Group.&lt;BR /&gt;Unable to match these Physical Volumes to a Volume Group.&lt;BR /&gt;Use the vgimport command to complete the process.&lt;BR /&gt;/dev/dsk/c9t0d5&lt;BR /&gt;/dev/dsk/c14t0d5&lt;BR /&gt;&lt;BR /&gt;Following Physical Volumes belong to one Volume Group.&lt;BR /&gt;Unable to match these Physical Volumes to a Volume Group.&lt;BR /&gt;Use the vgimport command to complete the process.&lt;BR /&gt;/dev/dsk/c9t0d6&lt;BR /&gt;/dev/dsk/c14t0d6&lt;BR /&gt;&lt;BR /&gt;The Volume Group /dev/vg_d01 was not matched with any Physical Volumes.&lt;BR /&gt;The Volume Group /dev/vg_d02 was not matched with any Physical Volumes.&lt;BR /&gt;The Volume Group /dev/vg_d03 was not matched with any Physical Volumes.&lt;BR /&gt;The Volume Group /dev/vg_d04 was not matched with any Physical Volumes.&lt;BR /&gt;The Volume Group /dev/vg_d05 was not matched with any Physical Volumes.&lt;BR /&gt;The Volume Group /dev/vg_d06 was not matched with any Physical Volumes.&lt;BR /&gt;The Volume Group /dev/vg_migrate was not matched with any Physical&lt;BR /&gt;Volumes.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Shouldnt this have worked?  I thought vgscan compared the group device major and minor from /dev/vg-whatever to the lvm headers on the disk.&lt;BR /&gt;&lt;BR /&gt;Is there any other action I can take?  I do not know which physical disk device belongs to what volume group.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance!</description>
    <pubDate>Wed, 15 Jun 2005 10:59:37 GMT</pubDate>
    <dc:creator>Aharon Chernin_1</dc:creator>
    <dc:date>2005-06-15T10:59:37Z</dc:date>
    <item>
      <title>Recreating /etc/lvmtab problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/recreating-etc-lvmtab-problem/m-p/3564676#M622971</link>
      <description>I have a customer who has somehow managed to remove all the volume groups except for /dev/vg00 from the lvmtab.  Either that,  or the file has become corrupted.  Also,  at the same time the controller number of the disk devices (c#1t3d0) for both paths has changed to a different number.  So, who knows what they were up to over there.&lt;BR /&gt;&lt;BR /&gt;I had them strings the /etc/lvmtab file, and as I thought, only /dev/vg00 was in there.&lt;BR /&gt;&lt;BR /&gt;I then had them do a vgscan -a -v -p to see if we could rebuild the /etc/lvmtab file from the lvm headers on the disk.  The /dev/vg* directories and group info are all still there, so I thought this should work?&lt;BR /&gt;&lt;BR /&gt;Here is the output:&lt;BR /&gt;&lt;BR /&gt;vgscan: The physical volume "/dev/dsk/c0t6d0s2" is already recorded in&lt;BR /&gt;the "/etc/lvmtab" file.&lt;BR /&gt;vgscan: The physical volume "/dev/dsk/c3t6d0" is already recorded in the&lt;BR /&gt;"/etc/lvmtab" file.&lt;BR /&gt;Couldn't stat physical volume "/dev/dsk/c1t2d0":&lt;BR /&gt;Invalid argument&lt;BR /&gt;Physical Volume "/dev/dsk/c9t0d0" is not part of a Volume Group&lt;BR /&gt;Physical Volume "/dev/dsk/c14t0d0" is not part of a Volume Group&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;/dev/vg00&lt;BR /&gt;/dev/dsk/c0t6d0s2&lt;BR /&gt;/dev/dsk/c3t6d0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Following Physical Volumes belong to one Volume Group.&lt;BR /&gt;Unable to match these Physical Volumes to a Volume Group.&lt;BR /&gt;Use the vgimport command to complete the process.&lt;BR /&gt;/dev/dsk/c9t0d1&lt;BR /&gt;/dev/dsk/c14t0d1&lt;BR /&gt;&lt;BR /&gt;Following Physical Volumes belong to one Volume Group.&lt;BR /&gt;Unable to match these Physical Volumes to a Volume Group.&lt;BR /&gt;Use the vgimport command to complete the process.&lt;BR /&gt;/dev/dsk/c9t0d2&lt;BR /&gt;/dev/dsk/c14t0d2&lt;BR /&gt;&lt;BR /&gt;Following Physical Volumes belong to one Volume Group.&lt;BR /&gt;Unable to match these Physical Volumes to a Volume Group.&lt;BR /&gt;Use the vgimport command to complete the process.&lt;BR /&gt;/dev/dsk/c9t0d3&lt;BR /&gt;/dev/dsk/c14t0d3&lt;BR /&gt;&lt;BR /&gt;Following Physical Volumes belong to one Volume Group.&lt;BR /&gt;Unable to match these Physical Volumes to a Volume Group.&lt;BR /&gt;Use the vgimport command to complete the process.&lt;BR /&gt;/dev/dsk/c9t0d4&lt;BR /&gt;/dev/dsk/c14t0d4&lt;BR /&gt;&lt;BR /&gt;Following Physical Volumes belong to one Volume Group.&lt;BR /&gt;Unable to match these Physical Volumes to a Volume Group.&lt;BR /&gt;Use the vgimport command to complete the process.&lt;BR /&gt;/dev/dsk/c9t0d5&lt;BR /&gt;/dev/dsk/c14t0d5&lt;BR /&gt;&lt;BR /&gt;Following Physical Volumes belong to one Volume Group.&lt;BR /&gt;Unable to match these Physical Volumes to a Volume Group.&lt;BR /&gt;Use the vgimport command to complete the process.&lt;BR /&gt;/dev/dsk/c9t0d6&lt;BR /&gt;/dev/dsk/c14t0d6&lt;BR /&gt;&lt;BR /&gt;The Volume Group /dev/vg_d01 was not matched with any Physical Volumes.&lt;BR /&gt;The Volume Group /dev/vg_d02 was not matched with any Physical Volumes.&lt;BR /&gt;The Volume Group /dev/vg_d03 was not matched with any Physical Volumes.&lt;BR /&gt;The Volume Group /dev/vg_d04 was not matched with any Physical Volumes.&lt;BR /&gt;The Volume Group /dev/vg_d05 was not matched with any Physical Volumes.&lt;BR /&gt;The Volume Group /dev/vg_d06 was not matched with any Physical Volumes.&lt;BR /&gt;The Volume Group /dev/vg_migrate was not matched with any Physical&lt;BR /&gt;Volumes.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Shouldnt this have worked?  I thought vgscan compared the group device major and minor from /dev/vg-whatever to the lvm headers on the disk.&lt;BR /&gt;&lt;BR /&gt;Is there any other action I can take?  I do not know which physical disk device belongs to what volume group.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance!</description>
      <pubDate>Wed, 15 Jun 2005 10:59:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/recreating-etc-lvmtab-problem/m-p/3564676#M622971</guid>
      <dc:creator>Aharon Chernin_1</dc:creator>
      <dc:date>2005-06-15T10:59:37Z</dc:date>
    </item>
    <item>
      <title>Re: Recreating /etc/lvmtab problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/recreating-etc-lvmtab-problem/m-p/3564677#M622972</link>
      <description>vgscan -a &lt;BR /&gt;&lt;BR /&gt;This will re-create the /etc/lvmtab file.&lt;BR /&gt;&lt;BR /&gt;mv /etc/lvmtab /etc/lvmtab.save&lt;BR /&gt;&lt;BR /&gt;first.&lt;BR /&gt;&lt;BR /&gt;The problem here is that you may be forced to vgimport your volume groups, depending on what was actually done to corrupt /etc/lvmtab&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 15 Jun 2005 11:05:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/recreating-etc-lvmtab-problem/m-p/3564677#M622972</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2005-06-15T11:05:46Z</dc:date>
    </item>
    <item>
      <title>Re: Recreating /etc/lvmtab problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/recreating-etc-lvmtab-problem/m-p/3564678#M622973</link>
      <description>You ran (vgscan -a -v -p) in preview mode. It will not recreate lvmtab.&lt;BR /&gt;vgscan -av will do it for you. before that take a backup of lvmtab file.&lt;BR /&gt;&lt;BR /&gt;-USA..</description>
      <pubDate>Wed, 15 Jun 2005 11:08:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/recreating-etc-lvmtab-problem/m-p/3564678#M622973</guid>
      <dc:creator>Uday_S_Ankolekar</dc:creator>
      <dc:date>2005-06-15T11:08:22Z</dc:date>
    </item>
    <item>
      <title>Re: Recreating /etc/lvmtab problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/recreating-etc-lvmtab-problem/m-p/3564679#M622974</link>
      <description>Thanks for the replies.&lt;BR /&gt;&lt;BR /&gt;I ran it in preview mode first to see what changes it would do.  Most of the disks came back with "Unable to match these Physical Volumes to a Volume Group.", so I figured there wouldnt be any changes the command would be making to the lvmtab file.&lt;BR /&gt;&lt;BR /&gt;I do not have any of their mapfiles, can I do a vgimport without a mapfile?  Can I even do a vgimport without knowing what volume group these devices belong to?</description>
      <pubDate>Wed, 15 Jun 2005 11:19:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/recreating-etc-lvmtab-problem/m-p/3564679#M622974</guid>
      <dc:creator>Aharon Chernin_1</dc:creator>
      <dc:date>2005-06-15T11:19:00Z</dc:date>
    </item>
    <item>
      <title>Re: Recreating /etc/lvmtab problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/recreating-etc-lvmtab-problem/m-p/3564680#M622975</link>
      <description>If you think the physical disks are good and have data then you can test create a VG and mount it to see what data it has.&lt;BR /&gt;&lt;BR /&gt;Here is the doc that  explains the process&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000076088069" target="_blank"&gt;http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000076088069&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;-USA..</description>
      <pubDate>Wed, 15 Jun 2005 11:40:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/recreating-etc-lvmtab-problem/m-p/3564680#M622975</guid>
      <dc:creator>Uday_S_Ankolekar</dc:creator>
      <dc:date>2005-06-15T11:40:26Z</dc:date>
    </item>
    <item>
      <title>Re: Recreating /etc/lvmtab problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/recreating-etc-lvmtab-problem/m-p/3564681#M622976</link>
      <description>&lt;BR /&gt;My guess, the VGEXPORT removed the volgroup definitions from /etc/lvmtab.&lt;BR /&gt;&lt;BR /&gt;maybe next time, this might help:&lt;BR /&gt;&lt;BR /&gt;EXPORT on System B:&lt;BR /&gt;&lt;BR /&gt;vgexport -v -m /etc/lvmconf/vgXX.map /dev/vgXX&lt;BR /&gt;&lt;BR /&gt;vgchange -a n /dev/vgXX&lt;BR /&gt;&lt;BR /&gt;on the other sytem you would like to import them, do:&lt;BR /&gt;&lt;BR /&gt;rcp or ftp the /etc/lvmconf/vgXX.map file over to the other system A.&lt;BR /&gt;&lt;BR /&gt;IMPORT on System A:&lt;BR /&gt;mkdir /dev/vgXX&lt;BR /&gt;mknod /dev/vgXX/group c 64 0x0?000&lt;BR /&gt;where the '?' is a unique number on your system.&lt;BR /&gt;&lt;BR /&gt;vgimport -v -m /etc/lvmconf/vgXX.map /dev/vgXX /dev/dsk/cXtXdX  &amp;lt;.&amp;gt;  &amp;lt;.&amp;gt;  &lt;BR /&gt;&amp;lt;.&amp;gt; all the associated extended disks that are needed.&lt;BR /&gt;&lt;BR /&gt;vgchange -a y /dev/vgXX&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Jun 2005 11:51:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/recreating-etc-lvmtab-problem/m-p/3564681#M622976</guid>
      <dc:creator>D Block 2</dc:creator>
      <dc:date>2005-06-15T11:51:46Z</dc:date>
    </item>
  </channel>
</rss>

