Operating System - HP-UX
1753435 Members
4447 Online
108794 Solutions
New Discussion юеВ

vg01 config hosed in SAM, now can't create additional groups

 
SOLVED
Go to solution
Matthew Byrd
New Member

vg01 config hosed in SAM, now can't create additional groups

Hello everyone. I'm running a 715/50 with HP-UX 10.20. I tried to configure a second hard drive as part of a new volume (vg01). SAM was unable to create the group, and told me to check the device minor number of the new device file "group" in /dev/vg01, which showed major/minor of 64/0x0010000 (unique on this system). vg00 has a group file on a different minor number. I have already added this drive to vg00 just to get it running for now, but I am really perplexed as to how to fix the larger issue. I have already deleted/rebuilt the lgtab, and have deleted the vg01 directory from /dev. It doesn't show up anywhere that I can see, and the scan comes back clean with just vg00, but there is obviously some file stopping this process. Any pointers ?
6 REPLIES 6
Karthik S S
Honored Contributor
Solution

Re: vg01 config hosed in SAM, now can't create additional groups

Hi Mathew,

The minor number should be 0x010000 not 0x0010000 ... I think that will solve your problem.

-Karthik S S
For a list of all the ways technology has failed to improve the quality of life, please press three. - Alice Kahn
Michael Tully
Honored Contributor

Re: vg01 config hosed in SAM, now can't create additional groups

Try to create it manually:

# pvcreate /dev/rdsk/cxtydz (sub your disk id here)
# mkdir /dev/vg01
# mknod /dev/vg01/group c 64 0x010000
# vgcreate /dev/vg01 /dev/dsk/cxtydz

Once this is successful, you should be able to create whatever logical volumes you like. I believe SAM tries to use the next available minor number. You can use whatever number you like (within reason) like 0x020000 or 0x030000
Anyone for a Mutiny ?
Steven E. Protter
Exalted Contributor

Re: vg01 config hosed in SAM, now can't create additional groups

You may need to go through a vgexport vgimport process to restore the situation.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Brian Vance
Advisor

Re: vg01 config hosed in SAM, now can't create additional groups

The procedure above should work. One tip to choose a minor number.
ls -l /dev/*/group will give a list of already used minor numbers.
Gerhard Roets
Esteemed Contributor

Re: vg01 config hosed in SAM, now can't create additional groups

Hi

Maybe the number is typed incorrectly in itrc. I can not say where the mistake is off course.

His minor number was, with the number of digits below.
0x0010000
001234567
A minor number should only contain 6 digits.

If i do an "mknod 0x0010000" the machine rewrites is to "0x010000" as a side note. This is off course correct behaviour in this case.

Regards
Gerhard
Matthew Byrd
New Member

Re: vg01 config hosed in SAM, now can't create additional groups

Thanks, everyone, I'll take a look at it, and see if my memory was correct about the minor number. I am pretty sure it was showing *7* digits, though. I remember thinking it was an odd-looking number when I first saw it. If the minor number really is hosed, I'll try to do the mknod first, then go the vgexport/vgimport route. Thanks for all your help ! - Matt