<?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: VGCHDID problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vgchdid-problem/m-p/5059440#M605787</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The messages exactly tells you what the problem is.&lt;BR /&gt;There is a VG BC1_xpvggendata5 already imported on the server and which is using  disk c28t3d4. &lt;BR /&gt;Do a strings /etc/lvmtab | grep c28t3d4 to reconfirm this.&lt;BR /&gt;&lt;BR /&gt;Proabaly, you did not export the VGs for the BC before doing the BC synchronisation ?&lt;BR /&gt;Now you can do &lt;BR /&gt;ll /dev/BC1_xpvggendata5/group   #[Note the minor number for the VG]&lt;BR /&gt;vgexport -v -p -m BC1_xpvggendata5.map /dev/BC1_xpvggendata5    # [To have the map file to be used when you do vgimport later ] &lt;BR /&gt;vgchange -a n /dev/BC1_xpvggendata5 #[Deactivate VG]&lt;BR /&gt;vgexport /dev/BC1_xpvggendata5    #[Export VG]&lt;BR /&gt;vgchgid /dev/rdsk/c28t3d4&lt;BR /&gt;mkdir /dev/BC1_xpvggendata5    &lt;BR /&gt;mknod /dev/BC1_xpvggendata5/group c 64 0xNN0000   #[ Us the minor number noted earlier]&lt;BR /&gt;vgimport -m BC1_xpvggendata5.map /dev/BC1_xpvggendata5 /dev/dsk/c28t3d4&lt;BR /&gt;vgchange -a y /dev/BC1_xpvggendata5&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Ninad</description>
    <pubDate>Sat, 21 Jul 2007 14:33:01 GMT</pubDate>
    <dc:creator>Ninad_1</dc:creator>
    <dc:date>2007-07-21T14:33:01Z</dc:date>
    <item>
      <title>VGCHDID problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgchdid-problem/m-p/5059438#M605785</link>
      <description>Hi,&lt;BR /&gt;I am facing this error when im doing VGCHGID&lt;BR /&gt;&lt;BR /&gt;vgchgid /dev/rdsk/c28t3d4&lt;BR /&gt;vgchgid: disk "/dev/rdsk/c28t3d4" is already in vg "/dev/BC1_xpvggendata5".&lt;BR /&gt;&lt;BR /&gt;wat does that mean???</description>
      <pubDate>Sat, 21 Jul 2007 04:49:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgchdid-problem/m-p/5059438#M605785</guid>
      <dc:creator>Fenny_1</dc:creator>
      <dc:date>2007-07-21T04:49:02Z</dc:date>
    </item>
    <item>
      <title>Re: VGCHDID problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgchdid-problem/m-p/5059439#M605786</link>
      <description>You need to change the id before importing and activating the volume group. &lt;BR /&gt;&lt;BR /&gt;Before importing the volume group, run the vgchgid command for the business copy luns. Once that's done, do your vgimport.&lt;BR /&gt;&lt;BR /&gt;To fix what you have now, deactivate the volume, vgexport, vgchgid then vgimport.&lt;BR /&gt;&lt;BR /&gt;If this system only has access to the business copy, then you're fine to keep it as is without changing the vgid. Otherwise you'll end up with two VGs having disks that share the same id... which would cause problems w/ lvm.&lt;BR /&gt;&lt;BR /&gt;-denver&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 21 Jul 2007 07:21:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgchdid-problem/m-p/5059439#M605786</guid>
      <dc:creator>Denver Osborn</dc:creator>
      <dc:date>2007-07-21T07:21:57Z</dc:date>
    </item>
    <item>
      <title>Re: VGCHDID problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgchdid-problem/m-p/5059440#M605787</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The messages exactly tells you what the problem is.&lt;BR /&gt;There is a VG BC1_xpvggendata5 already imported on the server and which is using  disk c28t3d4. &lt;BR /&gt;Do a strings /etc/lvmtab | grep c28t3d4 to reconfirm this.&lt;BR /&gt;&lt;BR /&gt;Proabaly, you did not export the VGs for the BC before doing the BC synchronisation ?&lt;BR /&gt;Now you can do &lt;BR /&gt;ll /dev/BC1_xpvggendata5/group   #[Note the minor number for the VG]&lt;BR /&gt;vgexport -v -p -m BC1_xpvggendata5.map /dev/BC1_xpvggendata5    # [To have the map file to be used when you do vgimport later ] &lt;BR /&gt;vgchange -a n /dev/BC1_xpvggendata5 #[Deactivate VG]&lt;BR /&gt;vgexport /dev/BC1_xpvggendata5    #[Export VG]&lt;BR /&gt;vgchgid /dev/rdsk/c28t3d4&lt;BR /&gt;mkdir /dev/BC1_xpvggendata5    &lt;BR /&gt;mknod /dev/BC1_xpvggendata5/group c 64 0xNN0000   #[ Us the minor number noted earlier]&lt;BR /&gt;vgimport -m BC1_xpvggendata5.map /dev/BC1_xpvggendata5 /dev/dsk/c28t3d4&lt;BR /&gt;vgchange -a y /dev/BC1_xpvggendata5&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Ninad</description>
      <pubDate>Sat, 21 Jul 2007 14:33:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgchdid-problem/m-p/5059440#M605787</guid>
      <dc:creator>Ninad_1</dc:creator>
      <dc:date>2007-07-21T14:33:01Z</dc:date>
    </item>
    <item>
      <title>Re: VGCHDID problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgchdid-problem/m-p/5059441#M605788</link>
      <description>Hi,&lt;BR /&gt;Thanks for everyone's valuable help. My problem resolved.</description>
      <pubDate>Sat, 21 Jul 2007 14:51:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgchdid-problem/m-p/5059441#M605788</guid>
      <dc:creator>Fenny_1</dc:creator>
      <dc:date>2007-07-21T14:51:51Z</dc:date>
    </item>
  </channel>
</rss>

