make_recovery -A -C

[augusto cossa]

Hi,

I was doing a make_recovery -A -C and it ended as foolowed below:********
Started - Tue Jun 19 09:38:02 2001
********
make_recovery -A -C -d /dev/rmt/0mn
/usr/sbin/vgdisplay -v "vg00"
/usr/sbin/vgdisplay -v "vg00"
/usr/sbin/vgdisplay -v "vg01"
/usr/sbin/vgdisplay -v "vg02"
/usr/sbin/vgdisplay -v "vg03"
/usr/sbin/vgdisplay -v
"/opt/ignite/bin/save_config" -f "/var/opt/ignite/recovery/config.recover" "vg00
" >> "/var/opt/ignite/logs/makrec.log1" 2>&1
/usr/sbin/vgcfgbackup "vg00" >> /var/opt/ignite/logs/makrec.log1 2>&1
Volume Group configuration for /dev/vg00 has been saved in /etc/lvmconf/vg00.con
f
/usr/sbin/vgcfgbackup "vg01" >> /var/opt/ignite/logs/makrec.log1 2>&1
Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.con
f
/usr/sbin/vgexport -p -m /etc/lvmconf/vg01.mapfile vg01 >> /var/opt/ignite/logs/
makrec.log1 2>&1
Volume group "vg01" is still active.
/usr/sbin/vgcfgbackup "vg02" >> /var/opt/ignite/logs/makrec.log1 2>&1
Volume Group configuration for /dev/vg02 has been saved in /etc/lvmconf/vg02.con
f
/usr/sbin/vgexport -p -m /etc/lvmconf/vg02.mapfile vg02 >> /var/opt/ignite/logs/
makrec.log1 2>&1
Volume group "vg02" is still active.
/usr/sbin/vgcfgbackup "vg03" >> /var/opt/ignite/logs/makrec.log1 2>&1
vgcfgbackup: Warning: couldn't query physical volume "/dev/dsk/c0t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgcfgbackup: Warning: couldn't query all of the physical volumes.
vgcfgbackup: Couldn't query physical volume "/dev/dsk/c0t14d0":
The specified path does not correspond to physical volume attached to
this volume group
vgcfgbackup: Couldn't query physical volume "/dev/dsk/c0t14d0":
The specified path does not correspond to physical volume attached to
this volume group

********
Ended Unsuccessfully - Tue Jun 19 09:40:16 2001
********

Anybody can help me to fixed this problem?

Regards,
Augusto Cossa

[Vincent Stedema]

Hi,

Can you query the device with pvdisplay -v /dev/dsk/c0t14d0 ? Does the device file show up in an ioscan -funCdisk listing?

If the disk IS connected to your system, to which VG should it belong?

Vincent

[augusto cossa]

Vicent,

when I try to query with pvdisplay -v /dev/dsk/c0t14d0 the result is:

mlm01[179] / # pvdisplay -v /dev/dsk/c0t14d0
pvdisplay: Warning: couldn't query physical volume "/dev/dsk/c0t14d0":
The specified path does not correspond to physical volume attached to
this volume group
pvdisplay: Couldn't query the list of physical volumes.
pvdisplay: Couldn't retrieve the names of the physical volumes
belonging to volume group "/dev/vg03".
pvdisplay: Cannot display physical volume "/dev/dsk/c0t14d0".

the ioscan -fnC disk display is:mlm01[180] / # ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 2 8/4.12.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
/dev/dsk/c0t12d0 /dev/rdsk/c0t12d0
disk 3 8/4.13.0 sdisk CLAIMED DEVICE SEAGATE ST39175LC
/dev/dsk/c0t13d0 /dev/rdsk/c0t13d0
disk 0 8/12.5.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c1t5d0 /dev/rdsk/c1t5d0
disk 5 8/12.8.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC
/dev/dsk/c1t8d0 /dev/rdsk/c1t8d0
disk 6 8/12.9.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC
/dev/dsk/c1t9d0 /dev/rdsk/c1t9d0
disk 7 8/12.10.0 sdisk CLAIMED DEVICE SEAGATE ST39236LC
/dev/dsk/c1t10d0 /dev/rdsk/c1t10d0
disk 1 8/16/5.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 6x/32x
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0

Thanks,
Augusto

[John Waller]

Augusto,

Are you running this box in a ServiceGuard cluster??

I have seen this exact message when trying to run a make_recovery on a node within a ServiceGuard cluster. It occurs for any packages which are currently running on another node when you issue the command. If a package is on an alternate node make_recovery can not queary the Volume Group or any disks associated with that VG

[Vincent Stedema]

Augusto,

The output from ioscan shows that there's no disk with device file /dev/dsk/c0t14d0 connected to your system. Does the vg03 volume group still exist (try vgdisplay -v vg03) ? Or was it removed recently?

It may also be that the device is not responding and doesn't show up in the ioscan -fnCdisk output because the OS sees it as an unknown device. An ioscan -fn will tell you if this is the case.

It could also be that your /etc/lvmtab is out of sync with the current configuration on the system. You can use vgscan to re-scan all physical volumes for volume group information and re-create /etc/lvmtab. Be sure to save a copy of the current /etc/lvmtab, though. You might want to take a look at the man-page for vgscan for more information.

Vincent

[Bill McNAMARA_1]

As mentioned by the others you've got a missing disk.

The disk with scsi ID 14 connected to 8/4 is no longer present. Verify cableing.
If you delivberately change SCSI parameters, ID, lun number etc, you MUST update lvm.

You may want to do a vgdisplay -v vg02 just to see if there is any potential corruption issue.
You may have lvol problems now.

Watch out with vgscan because it will create a vailid lvmtab, but will not create it correctly, with all nice path balancing and redundancy corectly, it will create the lvmtab in numerical order of the device file discovery, you may want to verify the configuration is good and modify it after its created...

Later,
Bill

[Mike Shilladay]

Hi Augusto,

It would appear from the replies you have had so far that the disk at c0t14d0 has "gone missing in active service".

From the info on the replies I would suggest that the disk is not mirrored and that the device has gone offline. Check the output from the command "strings /etc/lvmtab" that will tell you what disk are in the volume group vg03.

I would also suggest that the machine is not in a MC/ServiceGuard cluster as mentioned in an earlier response, because the disks in a cluster can be seen but not activated, so an Ignite tape will not bail out unsuccessfully, it will notify the user that it cannot do anyhting with that volume group BUT will continue.

You may want to check diagnostics to see what the state of the suspect disk is, although the ioscan output doesn't indicate a that a disk on c0t14d0 has ever existed since the last reboot. When did you last reboot?
Does your machine run HP predictive? If your machine has been rebooted after the disk has failed but before Predictive ran, then predictive may not have noticed the disk has failed. Are the disks the Hot Swap type, you may find that the someone has unwittingley removed and not re-housed the drive correctly.

Hope this is of use.

Mike.

[Shahul]

Hi

I think this is because of invalid entry in /etc/lvmtab. U can try these

#cd /etc
#mv lvmtab lvmtab.old
#vgscan

This will recreate the lvmtab file with available Vgs. I hope this will solve ur problem.

Best of luck
shahul

[augusto cossa]

This is to thank to you all for your support an d i would like to say that all your replay could help me fixing this problem and i would like to give all of you 10 points but in mine browse appear as unassigned but without posibilities to assign point.


Againg many thanks.

Augusto