Ignite-UX ver. A.2.5.136

[Patrick Wallek]

I have a T500 running HP-UX 10.20 with Ignite-UX version A.2.5.136 installed.

I tried booting the system from the ignite tape this weekend. It did successfully boot from the tape, and got to the point where it asks whether or not I want to enable networking. I said NO. It then looks like it tried to load a mini-kernel (or mini-shell -- I don't remember the exact message). When it did this it got dropped down to the # prompt and told me that I would need to use the 'loadfile' command to load other commands and that I would need to use 'reboot' when done.

I am confused about the behavior of the Ignite tape here. Normally it goes to the menu and you can interact with the install.

The tape was created with the following command: /opt/ignite/bin/make_recovery -A -C -i -t "Make recovery of UPR system `uname -n` on `date`" -d /dev/rmt/0mn

Any ideas as to what's going on here?

[Tom Crawford]

Hi Patrick,

I seem to remember this sort of thing happening to me because I failed to watch the installation messages after initially booting from the make_recovery tape. It's sort of silly, but the install will occur non-interactively if you don't respond in a ten-second window. I'm not sure what your situation is, but I learned from this to first test the make_recovery on a disk other than the one you have designated as the primary boot.

[Patrick Wallek]

I tested the tape this morning in a test system I have (I gave up on it this weekend). It booted as it's supposed to. The '-i' option to make_recovery tells it to ALWAYS be an interactive installation. A handy option.

What the tape was doing on Saturday -- It would boot, the title would be displayed (the -t option does this) and would say press any key to continue. Somehow it would continue automatically. Then it would get to the menu (Install HP-UX, Run a recovery shell, etc.) and would automatically run the recovery shell.

On the test machine this morning it behaved as it should have and paused and waited for keyboard input in all the right places.

I am wondering if the fact the the console on this machine is connected to a KVM switch, with a DEC VT100 terminal acting as the main console would have anything to do with this. I think next time I try this I will attach a console directly to the machine rather than relying on the switch.