topic Re: make_recovery failure in Operating System - HP-UX

make_recovery failure

Tom Dawson — Sat, 13 Apr 2002 15:10:48 GMT

Hi,

I'm trying to rebuild ( clone ) a server from a make_recovery tape.
The make_recovery tape was made on a v11.11 D330 with the following
command:

make_recovery -ACv -d /dev/rmt/0mn

The make_recovery process indicated the tape had been created successfully.

When I try to boot from the tape on the new server, I get the following:

-----------------------------------------------------------------------
Booting...
Boot IO Dependent Code (IODC) revision 144

Failed I/O operation with
ENTRY_IO
Status = -3

00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000008 00000000 00000000 454E4841 00000002 00000090 454E48D3
00000000 00000000 00000000 00000000 00000400 00000000 00000000 00000000

Error Reading IPL
-----------------------------------------------------------------------

And at this poing the "clean" light on the tape drive starts flashing.

I've ran cleaning tapes through all the tape drives, both on the server
creating the tape and on the server to be rebuilt. I've used two different
tape drives on the server to be rebuilt and I've used two different tapes.
All drives involved are HP DDS-3 tape drives and the tapes are HP DDS-3
tapes.

Do I have the make_recovery command wrong ( I used the no-rewind device )?
Or have just come across a bunch of bad tape drives? Or possibly two
bad tapes?

Both servers involved are D330's and I've made sure all expansion cards
in the new server are in the same slots as in the server being cloned.
The only differences are:

1. The server being cloned has 512 Mb RAM, the new server only has 416 MB.
2. The server being cloned has 2 FWD SCSI Cards, the new server only has 1.

Any help would be appreciated.

TIA,
Tom

Re: make_recovery failure

harry d brown jr — Sat, 13 Apr 2002 15:34:07 GMT

Tom,

I've seen other people suggest using the norewind device, but I have never had to use it, and I suspect that could be the issue here, by say 10%.

Also, toss in the "Interactive" option, which I think is "-i" but could be the upper case "-I" option.

Use another tape and recreate the make_recovery. Another better option is to upgrade your ignite on your running machine, and perform a make_tape_recovery - as make_recovery is being obsoleted.

Also, do both machines have the same firmware version??

live free or die
harry

Re: make_recovery failure

Tom Dawson — Sat, 13 Apr 2002 16:03:43 GMT

Harry,

Thanks! Actually, I have make_tape_recovery available. I just haven't taken the time to figure out what the comparable parameters are to make_recovery's "ACv".

My understanding was that you had to use the "norewind" device because a boot image was first written to the tape, then a separate job writes the file system data.

I'll try it with the rewind device and "i".

Thanks,
Tom

Re: make_recovery failure

Clemens van Everdingen — Sat, 13 Apr 2002 17:04:33 GMT

Hi,

Use this command:

make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/0mn

This does:

Create a system recovery tape that includes files from all file systems in the vg00 volume group:

See also man make_tape_recovery.

C.

Re: make_recovery failure

Clemens van Everdingen — Sat, 13 Apr 2002 17:06:21 GMT

Hi again,

By the way download the latest version from:

http://www.software.hp.com/products/IUX/

C.