make net recovery error

[Carl Zabel_2]

I am trying to run net recovery on a new B2600 running 11i. It fails every time when it checks the system_cfg file. It looks like it doesn't understand the virtbus entry "es" for the 2600. I have never run into this problem before. Any ideas???

[garel]

Hi,

try the following:

This problem comes from insufficient access rights.
Check the umask on the client by typing:
umask

Make a long listing of the system_cfg file which you can find in:
/var/opt/ignite/clients/(MAC-address)/recovery/(date),(time)/

If you have a restricted umask, e.g. 026, change it like:
umask 022.
The system_cfg file will then have "rw-r--r--".

Try make_net_recovery again, it should proceed now.


regards

[Carl Zabel_2]

Didn't fix it. Still says instl_adm cannot parse the system_cfg file.

[Uday_S_Ankolekar]

Hi,
Use the -d option with the make_recovery command to specify a no rewind
tape device. The syntax to run make_recovery in preview mode is
make_recovery ???pv ???d [no_rewind_tape_device], then to resume the
make_recovery, use the syntax make_recovery ???rvC ???d [no_rewind_tape_device]


Please see the man page for make_recovery(1m) for more details

-USA..

[Carl Zabel_2]

I am not running make recovery, I am running make net recovery from the gui.

[Uday_S_Ankolekar]

Hi,

Sorry for the previous post,

This problem may be comes from insufficient access rights.


Check the umask on the client by typing:
umask

Make a long listing of the system_cfg file which you can find in:
/var/opt/ignite/clients/(MAC-address)/recovery/(date),(time)/


If you have a restricted umask, e.g. 026, change it like:
umask 022.
The system_cfg file will then have "rw-r--r--".

Try make_net_recovery again, it should proceed now.


-USA..

[Sanjay_6]

Hi Carl,

Take a look at these threads,

http://us-support.external.hp.com/cki/bin/doc.pl/sid=2c89fe810d4c2a51c4/screen=ckiDisplayDocument?docId=200000011495949

http://us-support.external.hp.com/cki/bin/doc.pl/sid=2c89fe810d4c2a51c4/screen=ckiDisplayDocument?docId=200000012180487

Hope this helps.

Regds

[Michael Roberts_3]

This problem is fixed in Ignite-UX release B.3.5 available on the web at
www.software.hp.com/products/IUX.

From the release notes:
This section describes the recent Ignite-UX releases. Major changes
and defect fixes for each release are described here.

2.1 Versions A.3.5/B.3.5 (10/2001)
==================================
[snip..]
save_config now sets the above driver parameter. A check was also added
that ensures that the hardware path is of the format expected by the
parser for hw_instance_num. This fixes the problem introduced by the
sdm driver which has a hardware path of "es" for the virtbus class.