Ignite-UX

make_recovery(486): Call to system failed

 
Kong Kian Chay
Regular Advisor

make_recovery(486): Call to system failed

Encountered above at end when issuing command :
#make_recovery -v -A -C -d /dev/rmt/1m

** Also attached the full log of the error **

System : HP-UX 10.20
7 REPLIES 7
Satish Y
Trusted Contributor

Re: make_recovery(486): Call to system failed

Are u running this make recovery on remote server?.

And also u should use /dev/rmt/0mn (suffix 'n') as ur device.

Cheers...
Satish.
Difference between good and the best is only a little effort
Satish Y
Trusted Contributor

Re: make_recovery(486): Call to system failed

Are u running this make recovery on remote server?.

And also u should use non-rewind tape device /dev/rmt/0mn (suffix 'n')

Cheers...
Satish.
Difference between good and the best is only a little effort
Marcin Wicinski
Trusted Contributor

Re: make_recovery(486): Call to system failed

Hi,

try to find out which vg contains /dev/dsk/c6t1d0 (#strings/etc/lvmtab).

Then execute

# vgdisplay -v /dev/vg

and if you get the same warning it means you probably have a gost disk in your system.
Typical event that might create a ghost disk is a replacement of a defect hot swap hard disk just physically without removing it from LVM.

Then you can follow these steps:

1. Unmirrored Logical Volumes:

Determine the affected logical volumes with:

# vgdisplay -v vgXY | grep stale
and
# lvdisplay -v /dev/vgXY/lvolZ

Remove the logical volumes with:

# lvremove /dev/vgXY/lvolZ

The next steps are the same for both kinds - unmirrored resp. mirrored -, see step 3.



2. Mirrored Logical Volumes:

Determine the affected logical volumes with:

# vgdisplay -v vgXY | grep stale
and
# lvdisplay -v -k /dev/vgXY/lvolZ

Now, the disk key instead of the device file is shown in column PV:

--- Logical extents ---
LE PV1 PE1 Status 1 PV2 PE2
Status 2
0000 0 0000 current 1 0000
stale
0001 0 0001 current 1 0001
stale
To remove the mirror, do the following:

# lvreduce -m 0 -k /dev/vgXY/lvolZ [disk-key]



3. Further steps

Rename /etc/lvmtab

# mv /etc/lvmtab /etc/lvmtab.old

Create a new /etc/lvmtab

# vgscan ?v

NOTE: Alternate links have to be reconfigured after the vgscan.

Reactivate the volume group

# vgchange -a y vgXY

Now, the ghost disk can be removed from the volume group configuration by

# vgreduce -f vgXY


Good luck,
Marcin Wicinski
Kong Kian Chay
Regular Advisor

Re: make_recovery(486): Call to system failed

Satish
* have tried "/dev/rmt/0mn" & "../1mn".
Both failed with exact same error as posted.

NOTE :
* command issued LOCALLY.
* I have been issuing the stated command for the past 1 year. Last month was also successful.
* We have tape drives /dev/rmt/0m & /dev/rmt/1m.

Satish Y
Trusted Contributor

Re: make_recovery(486): Call to system failed

Hi Kong,

Marcin's suggestion is also good. But before going through all series of commands first check whether ur VG is active and also any stale physical extents r there...

Cheers...
Satish.
Difference between good and the best is only a little effort
Kong Kian Chay
Regular Advisor

Re: make_recovery(486): Call to system failed

Satish & Marcin

* Have removed the ghost LV as suggested by Marcin.
* However, the make_recovery problem remains.
Kong Kian Chay
Regular Advisor

Re: make_recovery(486): Call to system failed

To ALL

The problem was resolved after a REBOOT.

Would like to CLOSE this thread.

Thanks everybody.