save_config fails

[Warren griggs]

Hi All,

I am running a make_net_recovery but it is failing with the below message....

* Creating NFS mount directories for configuration files.

======= 11/18/03 13:36:38 GMT Started /opt/ignite/bin/make_net_recovery. (Tue
Nov 18 13:36:38 GMT 2003)
@(#) Ignite-UX Revision B.4.1.61
@(#) net_recovery (opt) $Revision: 10.597 $

* Testing pax for needed patch
* Passed pax tests.
* Checking Versions of Recovery Tools
* Creating System Configuration.
* /opt/ignite/bin/save_config -f /var/opt/ignite/recovery/client_mnt/0x0
0306E035955/recovery/2003-11-18,13:36/system_cfg
lssf: Must specify a special_file
usage: lssf special_file ...
save_config: error - unknown disk type for , not SCSI or HPFL
save_config: error - cannot determine root disk
ERROR: /opt/ignite/bin/save_config failed

======= 11/18/03 13:37:10 GMT make_net_recovery completed unsuccessfully

My root file system is mounted on /dev/root so I am unsure whether this is having any impact? I have tried looking through the save_config script but I thought I'd try you guys in case you have seen this before.

Thanks,
Colin.

[Stefan Farrelly]

I think ive seen it before - an ioscan -fnk showed a strange device file, cant recall if was a disk which in addition to /dev/dsk/cxxx and /dev/rdsk/cxxx had a /dev/lan entry! on removing it ignite worked, or a non disk which for some strange reason had a /dev/dsk/cxxxx entry for it. Try looking for strange device files from ioscan which should not be there.

[Robert-Jan Goossens]

Hi Colin,

http://www5.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062910622

Document description: Ignite: make_tape_recover returns error "save_config failed"
Document id: KBRC00010161

Regards,
Robert-Jan

[Bernhard Mueller]

Colin,

try to correct the /dev/root mount by
rm /etc/mnttab
mountall

run
file /usr/sbin/lssf and check if the output is reasonable
then re-run make_tape_recovery

Regards,
Bernhard

[Warren griggs]

Hi,

Thanks for your speedy replies...

I cannot see anything strange in the ioscan output, I have also tried to copy the binaries from a working system to see if they work (as per Robert-Jan's suggestion) but this still does not work. I also have removed the /etc/mnttab and recreated it, whilst this has got rid of the /dev/root I am still getting the error.

I think there must be something wrong with the script as it is not picking anything up to run the lssf against. If you look above in the make_net_recovery output the lssf is giving the error "Must specify a special_file" and the first save_config error does not show any disk path?

Any more ideas?

Thanks,
Colin.

[Robert-Jan Goossens]

Hi Colin,

Check if there are some logical volumes, which not have been removed properly but do still have files in the /dev/vg??/

something like,
# ls /dev/*/lvol* | while read LINE
do
lvdisplay $LINE
done

Hope this helps,
Robert-Jan

[Warren griggs]

Hi Robert-Jan,

Even worse than that, I cannot run a vgdisplay on vg00??

This is the output....

vgdisplay -v vg00
vgdisplay: Volume group "/dev/vg00" does not exist in the "/etc/lvmtab" file.
vgdisplay: Cannot display volume group "vg00".


Here is a strings on my /etc/lvmtab....

strings /etc/lvmtab
/dev/vg01
/dev/dsk/c7t0d0
/dev/vg02
/dev/dsk/c7t0d1
/dev/vg03
/dev/dsk/c7t0d2
/dev/vg04
/dev/dsk/c7t0d3
/dev/vg05
/dev/dsk/c7t0d4
/dev/vg06
/dev/dsk/c7t0d5
/dev/vg07
/dev/dsk/c7t0d6
/dev/vg08
/dev/dsk/c7t0d7
/dev/vg09
/dev/dsk/c7t1d0

Why is my vg00 not in here???

Thanks,
Colin.

[Robert-Jan Goossens]

Hi Colin,

# ll /dev/*/group
and check if you have a conflict in the minor numbers.

Robert-Jan

[Warren griggs]

Robert-Jan,

There are no conflicts in minor numbers...

crw-r----- 1 root sys 64 0x000000 Feb 22 2003 ./vg00/group
crw-r----- 1 root sys 64 0x010000 Sep 18 20:46 ./vg01/group
crw-r----- 1 root sys 64 0x020000 Sep 18 20:46 ./vg02/group
crw-r----- 1 root sys 64 0x030000 Sep 18 20:46 ./vg03/group
crw-r----- 1 root sys 64 0x040000 Sep 18 20:47 ./vg04/group
crw-r----- 1 root sys 64 0x050000 Sep 18 20:47 ./vg05/group
crw-r----- 1 root sys 64 0x060000 Sep 18 20:47 ./vg06/group
crw-r----- 1 root sys 64 0x070000 Sep 18 20:47 ./vg07/group
crw-r----- 1 root sys 64 0x080000 Sep 18 20:47 ./vg08/group
crw-r----- 1 root sys 64 0x090000 Sep 18 20:47 ./vg09/group


A pvdisplay also cannot find which volume group the disk belongs to....

/dev > pvdisplay -v /dev/dsk/c1t6d0
pvdisplay: Couldn't find the volume group to which
physical volume "/dev/dsk/c1t6d0" belongs.
pvdisplay: Cannot display physical volume "/dev/dsk/c1t6d0".


Thanks,
Colin.

[Robert-Jan Goossens · Accepted solution]

Colin,

# mv /etc/lvmtab /etc/lvmtab.save

# vgscan -v

# vgchange -a y vg00

# vgdisplay vg00

Robert-Jan

[Pippo_9]

Hi Colin,

Robert-Jan is right.
Recreating /etc/lvmtab could solve the problem.

Otherwise, you should execute

# lvlnboot -v

If no output or error messages return then you should recreate boot definitions on VG00. Below how to do:

# lvlnboot -R /dev/vg00

If problem persists, you could try to configure boot definitions manually:

# lvlnboot -r /dev/vg00/lvol3
# lvlnboot -s /dev/vg00/lvol2
# lvlnboot -d /dev/vg00/lvol2
# lvlnboot -b /dev/vg00/lvol1
# lvlnboot -v /dev/vg00

and then launching save_config:

# /opt/ignite/bin/save_config -f /tmp/saveconf.out vg00

If the last command works fine, then make_net_recovery will work fine.

I hope this helps you.

Bets regards,
Ettore