Ignite-UX fails to restore - Fails to find source in ioscan

[John Dinwoodie]

I am trying to restore a system to a partition on a brand new Superome from an ignite tape that was created on an old system.

This fails while booting from the ignite tape with the message -

ERROR: could not find source device "3/0/11/0/0" in ioscan output.

Please see the attachment for the full output.

Once it has booted from the tape it seems to then not be able to see it (or infact the local disks).

I guess this may be that the source system is at an old patch level and the ignite image that is built does not support the brand new harware.

Has anybody seen this message before and can confirm my fears or tell me what the problem might actually be.

Cheers, John

[Bernhard Mueller · Accepted solution]

John,

I suspect you are correct, looks like after you have booted the install kernel it is not able to see any of the FC paths.

If this tape is the only thing you have for the restore I would suggest you create a new one by running make_medialif on a current system with an appropriate config by running:
/opt/ignite/bin/make_medialif -f /var/opt/ignite/recovery/latest/archive_cfg \
-f /var/opt/ignite/recovery/latest/control_cfg \
-f /var/opt/ignite/recovery/latest/system_cfg \
-l /var/tmp/special_recovery.lif \
-a

Then extract your image from the tape to disk:
dd if=/dev/rmt/0m of=/bigtempdir/special.image

Then you use a fresh tape and combine the new lif with the old image:

mt -f /dev/rmt/0m rew
dd if=/var/tmp/special_recovery.lif of=/dev/rmt/0mn obs=2k
dd if=/bigtempdir/special_image of=/dev/rmt/0mn obs=10k


Then try to interactively recover from this new tape.
Do not forget to set "cloning to diff HW" to true.

Good luck.

Regards,
Bernhard

[Bernhard Mueller]

Oooooops:

"...
Then extract your image from the tape to disk:
dd if=/dev/rmt/0m of=/bigtempdir/special.image
...."

Of course this should read:
insert your old tape
mt -f /dev/rmt/0m rew
mt -f /dev/rmt/0mn fsf 1
(you need to skip the lif to extract the second tapefile)
dd if=/dev/rmt/0m of=/bigtempdir/special.image

(do not forget to use a no-rewind device with fsf....)

Regards,
Bernhard

[sinhass]

Hi Jhon,
I have doubt that ignite tape taken from old class server will work on new hardwares. I am not very sure but u can search the forum for this issue.

-sinhass

[Bill Hassell]

Regardless of the source machine (which should be a fairly new box), this is the problem:

Ignite-UX Revision B.3.2.45

That version is far too old to support new boxes like the SuperDome. Go back to the old machine (which should be an rp-series or perhaps N or L class, but NOT K-class, D-class, E-class, or any of the old Novas (F/G/H/I-series). Download the latest version of Ignite/UX and run make_tape_recovery. If you used make_recovery in the past, the options are very different. Ignite/UX is by it's nature very hardware dependent, so to avoid all these issues (and delays), always download the latest version quarterly and load it onto all your machines. Note: new hardware not only includes CPU's but most especially I/O cards, LAN card, disks and tapes.

[Sanjay_6]

Hi John

you are having compatibility problem with the version of ignite through which this tape was made and the hardware on which you are trying to install.

Upgrade the ignite on the server from which this tape was made and make a fresh ignite tape.

You can download the latest version of ignite from this location.

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

Hope this helps.

Regds

[John Dinwoodie]

Many thanks to all for the replies.

Bernhards elegant solution worked nicely to get us over the initial problem and the on going solution was to upgrade the ignite version on the donor systems to a later version (5.3.35).

Relating to the hardware comments we were trying to ignite partitions on a brand new superdome from tapes taken on an identical but 2/3 year old Superdome. The hardware was effectively identical but just firmware and interface versions were different.