make_net_recovey strange error

[likid0]

Hy people,

When i lauch a recovry image, it has allways worked, sudenly:

make_net_recovery -s epzilot -x inc_entire=vg00
* Creating NFS mount directories for configuration files.

======= 07/06/06 17:12:04 METDST Started make_net_recovery. (Thu Jul 06
17:12:04 METDST 2006)
@(#) Ignite-UX Revision C.6.1.44
@(#) net_recovery (opt) $Revision: 10.672 $

* Testing for necessary pax patch.
* Passed pax tests.
NOTE: Detected entries in the defaults file at
/var/opt/ignite/recovery/client_mnt/0x00306E0E520D/recovery/defaults.

NOTE: The -m option is used. So the pax option is tar
* Checking Versions of Recovery Tools
* Creating System Configuration.
* /opt/ignite/bin/save_config -f /var/opt/ignite/recovery/client_mnt/0x0
0306E0E520D/recovery/2006-07-06,17:12/system_cfg vg00


I get this error:

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

======= 07/06/06 17:15:19 METDST make_net_recovery completed unsuccessfully


All my boot disks are ok:

setboot
Primary bootpath : 0/0/1/0/0.8.0
Alternate bootpath : 0/0/8/0/0.8.0

Autoboot is ON (enabled)
Autosearch is ON (enabled)

Note: The interpretation of Autoboot and Autosearch has changed for
systems that support hardware partitions. Please refer to the manpage.
1:/# lssf 0/0/1/0/0.8.0
lssf: 0/0/1/0/0.8.0: No such file or directory
1:/# ioscan -fnkH 0/0/1/0/0.8.0
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
disk 0 0/0/1/0/0.8.0 sdisk CLAIMED DEVICE HP 18.2GATLAS10K3_18_SCA
/dev/dsk/c0t8d0 /dev/rdsk/c0t8d0
1:/# lssf /dev/dsk/c0t8d0
sdisk card instance 0 SCSI target 8 SCSI LUN 0 section 0 at address 0/0/1/0/0.8.0 /dev/dsk/c0t8d0
1:/# lvlnboot -v vg00
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t8d0 (0/0/1/0/0.8.0) -- Boot Disk
/dev/dsk/c0t10d0 (0/0/1/0/0.10.0)
/dev/dsk/c1t8d0 (0/0/8/0/0.8.0) -- Boot Disk
/dev/dsk/c1t10d0 (0/0/8/0/0.10.0)
Boot: lvol1 on: /dev/dsk/c0t8d0
/dev/dsk/c1t8d0
Root: lvol3 on: /dev/dsk/c0t8d0
/dev/dsk/c1t8d0
Swap: lvol2 on: /dev/dsk/c0t8d0
/dev/dsk/c1t8d0
Dump: lvol2 on: /dev/dsk/c0t8d0, 0

Any idea???

[Bill Hassell]

Ignite does a great job at checking for some sanity in the /dev directory. Try this:

find /dev -type f

If you see anything, a mistake was made. /dev never has anything except device files and directories. "root droppings" occur when you use the cd command and /dev is not a place to cd into. The lssf command is run to identify proper device files and to look at proper relationships so that the resulting backup will actually work when restored.

[Torsten.]

What gives

save_config -f -

(writes to stdout "-")

[likid0]

I only have /dev/null2 as a file

o1:/dev# find /dev -type f
/dev/null2

doesnt look like there is a problem there nope?


1:/dev# save_config -f -
cfg "HP-UX System Recovery"=TRUE
_hp_saved_detail_level="vfph"
#
# Variable assignments
#
lssf: Must specify a special_file
usage: lssf special_file ...
save_config: Error - unknown disk type for , not SCSI or HPFL
init _hp_root_disk=""
save_config: Error - cannot determine root disk


any idea?

[Bill Hassell]

You wrote:

> # find /dev -type f
> /dev/null2

> doesnt look like there is a problem there nope?

Yes, that is a problem. There is no such devicefile called /dev/null2. Someone mispelled the name and dumped something into /dev/null2 and created a normal file. Remove this file and you'll also get back all the space used by this file.

The error message:

> unknown disk type for , not SCSI or HPFL

seems to indicate an invisible filename between "for ," so it's possible there is a bad devicefile name in either /dev/dsk or /dev/rdsk. See if the error message is duplicated by running this command:

lssf /dev/rdsk/* /dev/dsk/*

If so, use ll -v to list all the files and look for a bad name. There may be a filename containing backspaces.

[Peter Marais]

If using lvm as boot disk check for errors when running lvlnboot -v and correct them.