make_recovery(390)

[Sarah Mokwana]

My customer is trying to do make_recovery with -A option and get the error message "make_recovery(390) call to /opt/ignite/bin/save_config failed"

I told customer to mv /etc/mnttab /etc/mnttab.old and mount -a, but they still experience this problem

[Cheryl Griffin]

The reason you would have moved /etc/mnttab and recreated it is only if bdf shows that your standard filesystems are not mounted, for instance /dev/root vs /dev/vg00, etc.

The 390 message indicates a problem with the volume group. Use vgdisplay to check that the Curr and Open LV's equal.
#vgdisplay /dev/vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 8 <---
Open LV 8 <---

More than likely you will find the problem here.

[jherring]

to add on to Cheryl. your issue most likely has something to do with the volume groups not being completely correct. Check a few of your files like /etc/fstab /etc/mnttab and the output of bdf and see if you can see where the issue is. you should see something that does not match up properly. vgdisplay -v and lvdisplay -v can help also. The issue should be rather evident when you find it.

Jon

[Sarah Mokwana]

I'll like to thank you for all the input I've received.What I discovered is that the ioscan and vgdispaly shows that the customer had 6 disk and the /etc/fstab shows that there is 4 disk.
Customer has removed 2 disk.During the make_recovery, vg00 was trying to query those disk that are not available.Customer didn't do the vgreduce after removing the disk.