trying to make a boot tape with ignite

[Norville Cole]

The following error occurs when I am trying to make a recovery tape. I would appreciate any help.

make_recovery -A -d /dev/rmt/c0t3d0BESTn
/opt/ignite/lbin/list_expander -d
/opt/ignite/lbin/list_expander -d -v
/opt/ignite/lbin/list_expander -d
"/opt/ignite/bin/save_config" -f "/var/opt/ignite/recovery/config.recover" "vg00
" >> "/var/opt/ignite/logs/makrec.log1" 2>&1
/opt/ignite/bin/save_config[10]: tee: not found.
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

********
Ended Unsuccessfully - Fri Apr 25 01:37:03 2008

[OldSchool]

"make_recovery"?????

Yikes, that's *way* out of date...I don't even have the "man" pages available any more.

What OS are you running? If newer than 11.0, download a newer version

http://www.docs.hp.com/en/IUX/download.html#d0e192

then take a look at "make_tape_recovery"

[Norville Cole]

we are running test equipment that is stable with 10.20 and we have no plans of updating. If you have any tricks up your sleeve I would appreciate to hear from you. Thanks Norville

[YAQUB_1]

>>> save_config: error - unknown disk type for , not SCSI or HPFL

Can U send us ioscan -fnC tape output

And alos check man page make_recovery....

[OldSchool]

"save_config: error - unknown disk type for , not SCSI or HPFL"

If ioscan lists the disks as "claimed", then I'd be suspicious of something like a garbage filename, something that has control characters perhaps. something that caused the make_recovery script to simply fall apart. Note how the problem starts with list_expander? You might check where its saving configuration files to see if it saved anything for this run that can help you.

Given the age of the system, I assume that Ignite worked in the past and that this is a recent problem.

[OldSchool]

also the output of:

/opt/ignite/lbin/list_expander -d -v

might be of use

[Mridul Shrivastava]

Hi,

One other possibility of this error from save_config is

if the root filesystem "/" is mounted by /dev/root and not with /dev/vg00/lvol3.

"bdf" will show this.

In case it is /dev/root in your systerm currently, then
====================
mv /etc/mnttab /etc/mnttab.bak
mount
======================

check "bdf" to verify it is now /dev/vg00/lvol3.

make_recovery should not report any problem now.

Regards,

Mridul

[Mridul Shrivastava]

There are other possibilities as well, like

1. You should use no-rewind device file "/dev/rmt/0mn" (suffix 'n') instead of "/dev/rmt/0m".

2. save_config errors are often misleading. It makes it look like it's a problem with Ignite, when actually it's an underlying problem with LVM. check the following:
# lvlnboot -v
# strings /etc/lvmtab
# vgdisplay -v /dev/vg00 |more
# bdf

3. ioscan (called by save_config) is showing up something which save_config is not comfortable with. We've seen this before, and I suggest you run :

lvlnboot -v

to show what is in the BDRA. If no information is returned, then there is no info in the BDRA. You will then have to recreate the info with lvlnboot command for the lvols that are in /dev/vg00. (lvol1,lvol2,lvol3 in particular). Once you have completed this, save_config (executed outside of make_recovery) should work ok.

Now you have some options to try, I hope one of them will fix the issue.