About make_recovery

[Michael Tully]

Unfortunately it looks like make_tape_recovery does not like volume groups to be unavailable. If you not using the volume group (vg11) you can activate just for this purpose and try running the make_tape_recovery again.

Activate the group

# vgchange -a y /dev/vg11

# make_tape_recovery ......

Please post the results.

Regards
Michael
"When I have trouble spelling, it's called fat finger syndrome"

[WERWERS]

but i have powered off DS2100 that including VG11.

# vgchange -a y /dev/vg11
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c0t9d0":
The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c0t11d0":
The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c0t13d0":
The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c0t15d0":
The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: Warning: couldn't query physical volume "/dev/dsk/c0t9d0":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c0t11d0":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c0t13d0":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query physical volume "/dev/dsk/c0t15d0":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query all of the physical volumes.
vgchange: Couldn't activate volume group "/dev/vg11":
Quorum not present, or some physical volume(s) are missing.

[Michael Tully]

Do you intend to use 'vg11' at all?

If not remove it, by exporting the VG

# vgexport /dev/vg11

If you do, can you turn on the external disk array, run an 'ioscan -fn' and then activate the volume group?

Regards
Michael
"When I have trouble spelling, it's called fat finger syndrome"

[T G Manikandan]

The problem is that the vgdisplay -v is giving out errors during the make_tape_recovery operation.

It could not find the disks for the VG11

/dev/dsk/c0t9d0
/dev/dsk/c0t11d0
/dev/dsk/c0t13d0
/dev/dsk/c0t15d0

Please do check whether these disks are available using ioscan -fnC disk

Also do check the contents of
strings /etc/lvmtab

If you are not using the VG11 group you can clean the entries by performing a vgexport of the VG.

Post the results of ioscan -fnC disk and strings /etc/lvmtab


Thanks

[WERWERS]

# ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
======================================================================
disk 5 0/0/1/0.8.0 sdisk CLAIMED DEVICE HP 18.2GST318406LC
/dev/dsk/c0t8d0 /dev/rdsk/c0t8d0
disk 6 0/0/1/0.10.0 sdisk CLAIMED DEVICE HP 18.2GST318406LC
/dev/dsk/c0t10d0 /dev/rdsk/c0t10d0
disk 7 0/0/1/0.12.0 sdisk CLAIMED DEVICE HP 18.2GST318406LC
/dev/dsk/c0t12d0 /dev/rdsk/c0t12d0
disk 8 0/0/1/0.14.0 sdisk CLAIMED DEVICE HP 18.2GST318406LC
/dev/dsk/c0t14d0 /dev/rdsk/c0t14d0
disk 3 0/0/1/1.0.0 sdisk CLAIMED DEVICE FUJITSU MAJ3182MC
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0
disk 0 0/0/1/1.2.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 4 0/0/2/0.0.0 sdisk CLAIMED DEVICE SEAGATE ST318404LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 1 0/0/2/0.2.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
disk 2 0/0/2/1.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 6x/32x
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0
# strings /etc/lvmtab
/dev/vg11
/dev/dsk/c0t9d0
/dev/dsk/c0t11d0
/dev/dsk/c0t13d0
/dev/dsk/c0t15d0
/dev/vg100
/dev/dsk/c0t10d0
/dev/dsk/c0t12d0
/dev/dsk/c0t14d0
/dev/vg00
/dev/dsk/c1t2d0
/dev/dsk/c2t2d0
/dev/dsk/c0t8d0
/dev/vg01
/dev/dsk/c1t0d0
/dev/dsk/c2t0d0
#

[Steven E. Protter]

If I were you, I'd do this:

vgreduce /dev/vg11 /dev/dsk/c0t15d0
vgreduce /dev/vg11 /dev/dsk/c0t11d0
vgreduce /dev/vg11 /dev/dsk/c0t13d0

vgremove /dev/vg11

Then try make_tape_recovery again.

I don't have access to a server that I can test my theory on, but thats how I got rid of my last volume group. Of course I did that prior to turning off the disk array.

I'd also throw Mr. Tully a few points for the long efforts he's made to help you.

Good Luck.

I know this will eventually work for you through perserverence.

SEP

[T G Manikandan]

Just do a
#vgexport -m vg11.map /dev/vg11

This should remove the VG from the system as well as properly update the /etc/lvmtab file.

Then things should be OK.

The disks were removed without properly updating changes on the VG.That created this problem


Revert

[T G Manikandan]

Can you post the file /var/opt/ignite/recovery/2003-06-17,17:58/system_cfg

[Kevin.Wang]

Any one can help me?

[Kevin.Wang]

Hello,why did not I run make_tape_recovery?