Operating System - HP-UX
1753365 Members
6080 Online
108792 Solutions
New Discussion юеВ

missing gui on interactive recovery

 
Reinhard Posmyk
Advisor

missing gui on interactive recovery

I've just tried to make an interactive tape
recovery with Ignite-UX B.5.4.50 on a B1000
workstation. But no gui has been started. The
last messages are:

Would you like to startup networking at this time?[n]
NOTE: Creating the second RAM disc and mounting on /dev ...
* Generating device file for the second ramdisc...
* Loading mkfs to make a file system...
version 4 layout
15625 sectors, 15625 blocks of size 1024, log size 1024 blocks
unlimited inodes, largefiles not supported
15625 data blocks, 14529 free data blocks
1 allocation units of 32768 blocks, 32768 data blocks
last allocation unit has 15625 data blocks
* Loading mount to mount/dev/ram1 file system...
* Mounting /dev/ram1 file system succeeded!
* Copying /dev.old files back to /dev succeeds!
* Loading insf to create disk device files...
* Creating disk device files...
* Loading in a shell...
NOTE: Pushing a shell, you will have to use "reboot" to reboot the system
when done. Use the "loadfile" command to bring in more commands as
you need them.
#


Did I miss something? The tape was created with
make_tape_recovery -I -A
rpos
6 REPLIES 6
Shaikh Imran
Honored Contributor

Re: missing gui on interactive recovery

Hi,
Please refer this:
Create a Recovery Archive from the Ignite-UX Server :
To create a system recovery archive from an Ignite-UX server:
Step 1. On your host system, allow the Ignite-UX server access to your to display
by adding the Ignite-UX server hostname to your xhost list:
xhost + Ignite-UX_server_hostname
Step 2. Set the DISPLAY variable to your local host system, if necessary. For
example:
export DISPLAY=Step 3. On the Ignite-UX server, as root run:
/opt/ignite/bin/ignite
Step 4. Select: Actions ├в > Add New Client for Recovery You will need to respond to
a dialogue to identify the system.
Step 5. Click the client icon when its appears on the Ignite-UX screen.
Step 6. Select: Actions ├в > Create Network Recovery Archive. You may be prompted
for the root password for the targetsystem.
The network recovery tools needed on the client will automatically be
installed.
After some information screens, you will see an Include/Exclude selection screen.

Regar
I'll sleep when i am dead.
Reinhard Posmyk
Advisor

Re: missing gui on interactive recovery

With Ignite/UX 4.4.x I could create tapes on
a standalone hpux box without having an ignite
server. I just used "make_tape_recovery". Was
there a change with 5.x? Can I make the
required steps to create a tape from a shell
script?
rpos
Shaikh Imran
Honored Contributor

Re: missing gui on interactive recovery

Hi,
Don't you get a gui if you run
/opt/ignite/bin/ignite


#make_tape_recovery -I -A

This is command line for taking the ignite backup whatever is the type standalone,network etc..,

Regards,



I'll sleep when i am dead.
Reinhard Posmyk
Advisor

Re: missing gui on interactive recovery

I guess my original question was a little bit
confusing. My problem is that I do not get a
gui within the restore session. When I hit a
key within 10 seconds, I only can change to
networking y/n. I get no gui to change the
disk layout or something else. With 4.4.x it
worked fine.
rpos
Shaikh Imran
Honored Contributor

Re: missing gui on interactive recovery

Hi,
Ok now you are 100% clear.

I suppose you are not getting the menu.
which ideally should be like the attached doc.

Now See the message in your first post viz,
NOTE: Pushing a shell, you will have to use "reboot" to reboot the system
when done. Use the "loadfile" command to bring in more commands as
you need them.
#

What happens when you reboot at this stage ?


Regards,


I'll sleep when i am dead.
Reinhard Posmyk
Advisor

Re: missing gui on interactive recovery

Ok, I may enter commands like "loadfile" or
"reboot". And reboot works as expected, i. e.
it reboots the machine. I guess, some required
script is missing or fails. I can see some
files in /tmp (client_status, install.log, ...),
but to me they all look ok.
rpos