Recovery Ignite Error: Back space of mt tape failed

[Fernando Boza]

I have rp3440 and a DAT40 C5687C.
The rp3440 has HP-UX 11.11 and Ignite-UX-11-11_C.6.9.150
I make ignite with make_tape_recovery -A -I -a /dev/rmt/0mn
But when recovering, I obtain the following error:

* Beginning installation from source: /dev/rmt/0m
======= 08/22/07 14:43:42 EDT Starting system configuration...
* Configure_Disks: Begin
* Will install B.11.11 onto this system.
ERROR: Back space of mt tape failed: Permission denied (errno = 13).
ERROR: search_file failed.
ERROR: Could not find SYSCMDS for B.11.11. The fileset
Ignite-UX.FILE-SRV-11-11 is probably missing or corrupt. Target disks
have not been disturbed.

The configuration process has incurred an error, would you like
to push a shell for debugging purposes? (y/[n]):

[Patrick Wallek]

It sounds like the tape was not created entirely successfully. 2 things I would try:

1) Try creating a new make_tape_recovery tape and try recovering again, if possible.

2) If it still fails, try upgrading Ignite/UX to the latest version and do step 1 again.

[Steven E. Protter]

Shalom,

Hopefully this is not an actual recovery because this tape is incomplete.

Could be bad tape media, could be a bad archive, which there should be a record of in the Ignite log.

Those logs are pretty darned useful and they should be checked at least periodically.

SEP

[Fernando Boza]

I have already created several ignite and the result is the same one.
Also I installed the last version of Ignite but the problem is the same one.
Where I can review ignite log to know that it is failing?

[skt_skt]

/var/opt/ignite/recovery/latest or /var/opt/ignite/recovery/date,time (not exactly recollecting)

[Fernando Boza]

I attach the last log.
Pls, your help.

[whiteknight · Accepted solution]

Hi Fernando

I will recommend for the following :-
There are several ways to verify the tape.

The tape has 2 parts: LIF and archive of the OS and other files.

1. Using lifls and dd

Use mt and dd with lifls to verify the boot information
on the tape, and use mt with tar to verify the data
information on the tape.

# dd if=/dev/rmt/0mn of=bootimage bs=2k
# lifls -l bootimage
# mt -f /dev/rmt/0mn rew
# mt -f /dev/rmt/0mn fsf 1
# tar tvf /dev/rmt/0mn

2. Using tar to check contents of the image:

- Skip over the first image with mt command

# mt -f /dev/rmt/0mn rew
# mt -f /dev/rmt/0mn fsf 1

- Verify the contents of the tar image:

# tar tvf /dev/rmt/0m

3. Using tar to extract a file:

To extract a file from an existing make_tape_recovery

- Rewind the tape:

# mt -t /dev/rmt/0m rew

- Forward past the lif area

# mt -t /dev/rmt/0mn fsf 1

- Extract the file from archive

# tar xvf /dev/rmt/0mn etc/hosts

Note: this will create etc/hosts in the present working directory.

4. Using copy_boot_tape

# mkdir /tmp/ignitetest
(/ignitetest must enough space in the file system to hold the lif image,
50Mb should be plenty)

# copy_boot_tape -u /dev/rmt/0mn -b -d /tmp/ignitetest

This will create /tmp/ignitetest/bootimage.

5. verify the bundle
Verify this bundle.
# swverify -x mount_all_filesystems=false -x autoselect_dependencies=false
Ignite-UX

6. gzcat /opt/ignite/data/Rel_B.11.11/SYSCMDS|tar -tvf -

WK
Please assign points

[Fernando Boza]

In this step, obtain this:

# mkdir /tmp/ignitetest
# copy_boot_tape -u /dev/rmt/0mn -b -d /tmp/ignitetest
Rewinding tape /dev/rmt/0mn.
Extracting the boot area to /tmp/ignitetest/bootimage.
dd read error: Permission denied
0+0 records in
0+0 records out
Tape may be write protected.

but, the tape is not protected

[whiteknight]

Fernado,

Likely the tape is faulty ;-)

Wk

[whiteknight]

Fernando,

Likely the tape is faulty ;-)

Wk