Operating System - HP-UX
1833304 Members
2811 Online
110051 Solutions
New Discussion

could not execute "vgchange" command.

 
Tan Shirley
Frequent Advisor

could not execute "vgchange" command.

Hi,

What happened was, one of my hard disk (dev/dsk/c3t10d0) was not detected by the system, hence my lvol which was in vg04 (whereby vg04 was on that particular hard disk) was not mounted when I execute bdf.

I to removed the hard disk, and plugged it back into the same slot, and do a ioscan -fnC, and then insf -e, and finally got to see the hard disk back. However, it appears to be /dev/dsk/c3t14d0 instead of /dev/dsk/c3t10d0. Therefore, I still can't see my vg04 and the lvol inside !
When I do a strings /etc/lvmtab, it still appears that vg04 is tied to /dev/dsk/c3t10d0.

Please advise what I could do in order to change the hard disk from /dev/dsk/c3t14d0 to /dev/dsk/c3t10d0 so that I could recover my vg04.

Thanks !
3 REPLIES 3
Michael Tully
Honored Contributor

Re: could not execute "vgchange" command.

Hi,

You didn't happen to change the SCSI address at
the back of the unit did you? If so change it
back. If not you could restore the information.

You could try this:

# vgchange -a n /dev/vg04 (doesn't matter the output)
# vgexport -m /tmp/vg04.mapfile -p -v /dev/vg04
if successful
# vgexport -m /tmp/vg04.mapfile -v /dev/vg04
# mkdir /dev/vg04
# ls /dev/*/group
(use the next available number 0x0NN0000)
# mknod /dev/vg04/group c 64 0x0NN0000
# vgimport -m /tmp/vg04.mapfile -p -v /dev/vg04
(if error post results, if not continue)
# vgimport -m /tmp/vg04.mapfile -v /dev/vg04
# vgchange -a y /dev/vg04

Michael
Anyone for a Mutiny ?
Patrick Wallek
Honored Contributor

Re: could not execute "vgchange" command.

Michael is right.

The t14 and t10 part of the disk address is the SCSI ID. That will NOT change by just taking the disk out and putting back into the enclosure. The SCSI id HAD to be changed by someone or something.

Change the id back to 10 and you should be OK.
Shahul
Esteemed Contributor

Re: could not execute "vgchange" command.

Hi

It is something funny. SCSI ID will not change just like that. If Ur earlier ID was c3t10d0, then it will remain as it is unless until U change the Jumpers. Are U sure U have not done anything with IDs? If yes, c3t14d0 is not the HDD which U are looking for. Make sure that Ur suspected HDD is getting detected as c3t10d0, After that try to vg activate.

Best of luck
Shahul