CREATING NEW SERVER WITH IGNITE

[Chris Chaoman]

I am trying to ignite a L1000 (HP-UX11.0)from a L2000 server. I have replaced the 4x18gb discs with 4x73gb discs. When I try to boot from the alternative path (LTO1 tape drive) it access the device then fails.
Boot failed: Running non-OS code. Followed by a lot of other errors.

[Pete Randall]

Was the archive created successfully? I would try re-running the make_tape_recovery and double checking it's success.


Pete

[Pete Randall]

Oh - and is the tape rewound to BOT?


Pete

[generic_1]

Just some ideas.
I would make sure that tape drive is supported. Make sure its working properly, tar command perhaps with a blank tape, make sure your ignite is up to date. Always make sure at the end of making an ignite tape that it says it was a success. Try booting the tape on your old disks or another system perhaps without actually initiating the build.

[Alex Glennie]

hows the lto attached ... via a fibre channel card ?

if yes solution here is to use dual media recovery because HP systems cannot
boot from FC connected tape drives.

Procedure to use dual media recovery:

1) Create the make_recovery as per normal. This tape would have the lif and
archive files.

2) Boot the system using the "core os" install cd. In the Ignite manual, it is
referred as "ignite media".
- at the main screen " Welcome to the HP-UX installation/recovery process"
* select "Install HP-UX"
- at the "User Interface and Meida Options"
* select "Meida only installation"
* select "Advanced installation"
- at the "Media Installation Selection"
* select "Boot from CD/DVD, Recover from Tape"

- select the correct hardware path for the tape drive containing the
make_recovery tape.

NOTE: The above info on how to do the recovery can also be obtained
from the Ignite manual in www.docs.hp.com . Refer to section titled 'System
Recovery - Tape recovery with no tape boot support'.

[Steven E. Protter]

Shalom Chris,

Your server supports booting from fiber san.

If the source server did not, the imaged server may not be able to do this.

You should be able to interupt the restore and reconfigure Ignite to this new situation.

How easy this is depends on what version of Ignite you use.

SEP