<?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: vgcreate failure in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768188#M643687</link>
    <description>Pete!!!...&lt;BR /&gt;&lt;BR /&gt;I followed the other message in the thread and you said in one of them&lt;BR /&gt;&lt;BR /&gt;"&lt;BR /&gt;and didn't like SAM's choice of minor number so I manually removed the group file and did my own mknod. That was the start of my problems.  "&lt;BR /&gt;&lt;BR /&gt;That might be the problem as the volume group was already active by the time you removed your group device. You would have recreated the group file and then exported the volume group to get rid of it.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;-Sri&lt;BR /&gt;</description>
    <pubDate>Fri, 19 Jul 2002 19:23:12 GMT</pubDate>
    <dc:creator>Sridhar Bhaskarla</dc:creator>
    <dc:date>2002-07-19T19:23:12Z</dc:date>
    <item>
      <title>vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768152#M643651</link>
      <description>I'm trying to re-create a volume group.  Sam can't see it yet when it tries to create it, it says the physical volume is already recorded in /etc/lvmtab.  I've tried re-creating lvmtab with vgscan but it complains "The Volume Group /dev/vg99 was not matched with any Physical Volumes."&lt;BR /&gt;&lt;BR /&gt;I can't go forward and I can't go back - it's the proverbial Catch-22.&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Fri, 19 Jul 2002 15:45:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768152#M643651</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2002-07-19T15:45:41Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768153#M643652</link>
      <description>Pete,&lt;BR /&gt;&lt;BR /&gt; Did you mv lvmtab prior to vgscan?&lt;BR /&gt;Also IF you know for a fact that the the vg99 is no longer used, try to vgexport it. Then also IF you know the PV is no longer unused do a pvcreate -f on it.&lt;BR /&gt;Then rerun your vgscan again prior to vgcreate.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Jeff</description>
      <pubDate>Fri, 19 Jul 2002 15:50:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768153#M643652</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2002-07-19T15:50:39Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768154#M643653</link>
      <description>Sounds like the VG exists, but in an odd state. Can you use vgextend to add a disk to the VG, and then use vgscan? I know that you need at least one disk to remove it. That still would leave the ? of how the last disk got removed...&lt;BR /&gt;&lt;BR /&gt;Tom</description>
      <pubDate>Fri, 19 Jul 2002 15:51:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768154#M643653</guid>
      <dc:creator>Tom Maloy</dc:creator>
      <dc:date>2002-07-19T15:51:17Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768155#M643654</link>
      <description>DOOOOOHHHHH....PV no longer used.....&lt;BR /&gt;&lt;BR /&gt;Jeff</description>
      <pubDate>Fri, 19 Jul 2002 15:51:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768155#M643654</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2002-07-19T15:51:27Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768156#M643655</link>
      <description>Jeff/Tom,&lt;BR /&gt;&lt;BR /&gt;Hang on - I'm re-trying the vgscan after making absolutely sure that I moved it first.  I'll get back to you in a few minutes.&lt;BR /&gt;&lt;BR /&gt;Pete&lt;BR /&gt;&lt;BR /&gt;P.S.  Jeff, when I went back and looked at my wizard congratulatory thread yesterday I noticed that it was you and Steven at the head of the list again - he started it and you had the first response.  Are you two my guardian angels, or what?</description>
      <pubDate>Fri, 19 Jul 2002 15:55:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768156#M643655</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2002-07-19T15:55:13Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768157#M643656</link>
      <description>Hi Pete:&lt;BR /&gt;&lt;BR /&gt;Make sure that the minor number of the volume group you are trying to create is unique.  Do:&lt;BR /&gt;&lt;BR /&gt;# ls -l /dev/vg*/group&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Fri, 19 Jul 2002 15:57:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768157#M643656</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2002-07-19T15:57:58Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768158#M643657</link>
      <description>"vgexport /dev/vg99" should work. Does /dev/vg99 and /dev/vg99/group exist?&lt;BR /&gt;&lt;BR /&gt;Marty</description>
      <pubDate>Fri, 19 Jul 2002 15:57:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768158#M643657</guid>
      <dc:creator>Martin Johnson</dc:creator>
      <dc:date>2002-07-19T15:57:59Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768159#M643658</link>
      <description>OK, vgscan finished and said:&lt;BR /&gt;The Volume Group /dev/vg99 was not matched with any Physical Volumes.&lt;BR /&gt;*** LVMTAB has been created successfully.&lt;BR /&gt;*** If PV links are configured in the system.&lt;BR /&gt;*** Do the following to resync information on disk.&lt;BR /&gt;*** #1. vgchange -a y&lt;BR /&gt;*** #2. lvlnboot -R&lt;BR /&gt;&lt;BR /&gt;Now, however, when SAM tries to create the vg, it says&lt;BR /&gt;"A volume group is already using this major and minor number"&lt;BR /&gt;&lt;BR /&gt;Aarghh!</description>
      <pubDate>Fri, 19 Jul 2002 16:02:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768159#M643658</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2002-07-19T16:02:46Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768160#M643659</link>
      <description>Look for duplicate minor numbers in the /dev/vgXX/group file information. Perhaps one got "fat-fingered".&lt;BR /&gt;&lt;BR /&gt;Tom</description>
      <pubDate>Fri, 19 Jul 2002 16:07:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768160#M643659</guid>
      <dc:creator>Tom Maloy</dc:creator>
      <dc:date>2002-07-19T16:07:56Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768161#M643660</link>
      <description>I've tried removing /dev/vg99 and still it complains that the major and minor number are in use.  I tried a different vgname (vg22) and it still complains.  Vgexport complains that vg99 is not listed in lvmtab.  Looking at /dev/vg*/group shows that the minor number SAM is trying to use should be unique (SAM's trying to use 0x040000):&lt;BR /&gt;ll /dev/vg*/group&lt;BR /&gt;crw-r-----   1 root       sys         64 0x000000 Feb 14  2000 /dev/vg00/group&lt;BR /&gt;crw-rw-rw-   1 root       root        64 0x010000 Jul 13 09:12 /dev/vg01/group&lt;BR /&gt;crw-rw-rw-   1 root       root        64 0x020000 Jul 13 09:12 /dev/vg02/group&lt;BR /&gt;crw-r--r--   1 root       sys         64 0x030000 Jun 27  2000 /dev/vgswap/group&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 19 Jul 2002 16:08:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768161#M643660</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2002-07-19T16:08:09Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768162#M643661</link>
      <description>I suspect that you some "abnormality" in some of your VG configuration. The minor number (0x040000) may not appear to be used in all the /dev/vg*/group files but it may still be in the kernel. Can you try to manually creating it (with command lines) but use another minor number (say 0x080000 or what ever).</description>
      <pubDate>Fri, 19 Jul 2002 16:15:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768162#M643661</guid>
      <dc:creator>S.K. Chan</dc:creator>
      <dc:date>2002-07-19T16:15:00Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768163#M643662</link>
      <description>Thought to add a note:&lt;BR /&gt;&lt;BR /&gt;If possible bring system to single user mode, unmount all data file systems and try:&lt;BR /&gt;&lt;BR /&gt;1) vgexport&lt;BR /&gt;2) check lvmtab&lt;BR /&gt;3) do vgscan -a&lt;BR /&gt;4) Create new vg with unique number&lt;BR /&gt;5) Add disk&lt;BR /&gt;&lt;BR /&gt;In either case, vgexport should work very easily. Carefully check the settings and try resolving one by one !</description>
      <pubDate>Fri, 19 Jul 2002 16:15:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768163#M643662</guid>
      <dc:creator>Helen French</dc:creator>
      <dc:date>2002-07-19T16:15:31Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768164#M643663</link>
      <description>Hi Pete,&lt;BR /&gt;&lt;BR /&gt; No I just wanted to see you squirm a little again ;~)&lt;BR /&gt;Steve &amp;amp; I just happened to post @ the same time.&lt;BR /&gt;&lt;BR /&gt;Back to the issue @ hand:&lt;BR /&gt;1) It is possible (but unprobable) that there's a misconfigured LV minor number in a VG. Look down thru them all to make sure you don't have am 0x040002 or such.&lt;BR /&gt;&lt;BR /&gt;2) Possible that something was/is linked to the old /dev/vg99/group entry or vice/versa.&lt;BR /&gt;&lt;BR /&gt;2) highly possible that the kernel thinks there's an 64  0x040000  device out there.&lt;BR /&gt;&lt;BR /&gt;For now manually create it with 64 0x050000 &amp;amp; track it down after the next reboot. May be gone after a reboot....&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;Jeff</description>
      <pubDate>Fri, 19 Jul 2002 16:24:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768164#M643663</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2002-07-19T16:24:03Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768165#M643664</link>
      <description>I tried the manual method.&lt;BR /&gt;mkdir /dev/vg99&lt;BR /&gt;mknod /dev/vg99/group c 64 0x050000&lt;BR /&gt;pvcreate /dev/rdsk/c18t1d2&lt;BR /&gt;pvcreate /dev/rdsk/c18t1d3&lt;BR /&gt;vgcreate /dev/vg99 /dev/dsk/c18t1d2 /dev/dsk/c18t1d3&lt;BR /&gt;Increased the number of physical extents per physical volume to 17326.&lt;BR /&gt;vgcreate: Volume group "/dev/vg99" could not be created:&lt;BR /&gt;Device busy&lt;BR /&gt;&lt;BR /&gt;lsof /dev/dsk/c18t1d2 shows nothing.&lt;BR /&gt;&lt;BR /&gt;Unless someone comes up with something brilliant, I think I'm going to give up for now and come in this weekend when I can re-boot this server.</description>
      <pubDate>Fri, 19 Jul 2002 16:48:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768165#M643664</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2002-07-19T16:48:50Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768166#M643665</link>
      <description>I'd physically check those drives.&lt;BR /&gt;Are they active - light on?&lt;BR /&gt;If you're sure of just which they are &amp;amp; they're hot-swappable, I'd pull them for 10-20 seconds &amp;amp; reseat them.&lt;BR /&gt;Something may have them tied up for some reason.&lt;BR /&gt;&lt;BR /&gt;Also if this is a shared array, be damn sure that another system doesn't have it mitts on 'em.&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;Jeff</description>
      <pubDate>Fri, 19 Jul 2002 17:05:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768166#M643665</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2002-07-19T17:05:51Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768167#M643666</link>
      <description>Hi Pete:&lt;BR /&gt;&lt;BR /&gt;DOes 'diskinfo' yield good information (like a disk size &amp;gt; 0)?:&lt;BR /&gt;&lt;BR /&gt;# diskinfo /dev/rdsk/c18t1d2&lt;BR /&gt;&lt;BR /&gt;Second, can you do the 'vgcreate' without this disk?&lt;BR /&gt;&lt;BR /&gt;I'm beginning to think you have a bad disk.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Fri, 19 Jul 2002 17:09:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768167#M643666</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2002-07-19T17:09:43Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768168#M643667</link>
      <description>Jeff/James,&lt;BR /&gt;&lt;BR /&gt;It's a pair of RAID 5 luns in an FC60 array.  No failure lights.  Diskinfo looks good.  I really don't think there's anything wrong with the disk(s).  I'll run a *little* dd just to prove that they can be exercised - it would probably take hours to dd the whole 140 MB.&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Fri, 19 Jul 2002 17:16:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768168#M643667</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2002-07-19T17:16:09Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768169#M643668</link>
      <description>The dd was successful - I read about a gig off of each lun.  I think, at this point, a re-boot is in order so I'll come in Sunday and see if that helps or makes things worse and post results on Monday.&lt;BR /&gt;&lt;BR /&gt;My thanks to all.&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Fri, 19 Jul 2002 17:24:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768169#M643668</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2002-07-19T17:24:57Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768170#M643669</link>
      <description>Hi&lt;BR /&gt;Can you check pvdisplay on those disks?&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;Prashant.</description>
      <pubDate>Fri, 19 Jul 2002 17:31:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768170#M643669</guid>
      <dc:creator>Deshpande Prashant</dc:creator>
      <dc:date>2002-07-19T17:31:39Z</dc:date>
    </item>
    <item>
      <title>Re: vgcreate failure</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768171#M643670</link>
      <description>pvdisplay /dev/dsk/c18t1d2&lt;BR /&gt;pvdisplay: Couldn't find the volume group to which&lt;BR /&gt; physical volume "/dev/dsk/c18t1d2" belongs.&lt;BR /&gt;pvdisplay: Cannot display physical volume "/dev/dsk/c18t1d2".&lt;BR /&gt;Same for the other.</description>
      <pubDate>Fri, 19 Jul 2002 17:34:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgcreate-failure/m-p/2768171#M643670</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2002-07-19T17:34:59Z</dc:date>
    </item>
  </channel>
</rss>

