topic Restoring Ignite --- Problem in Operating System - HP-UX

Restoring Ignite --- Problem

Marvin L. Diaz — Wed, 05 May 2010 23:24:22 GMT

Hi,

I have an old rp5470 and now we are migrating to rp4440.

i created the ignite on rp5470 using the command "make_tape_recovery -Av -a /dev/rmt/0mn"
the ignite has been successfully completed.

however upon restoring it to the new rp4440, before the completion of the restore is prompts me with a warning:

===============================================
NOTE: Unable to determine if system hardware is SCA. Configure "sppnuma"
into kernel if SCA use is desired.
* Executing: "/var/adm/sw/products/OS-Core/CORE-KRN/iux_postload".
* Executing: "/var/adm/sw/products/OS-Core/CORE-SHLIBS/iux_postload".
* Running: /var/adm/sw/products/OS-Core/CORE-SHLIBS/postinstall
NOTE: /usr/bin/libc.2 has been replaced with a version specifically
made for PA2.0 computers. The library can be changed back by
executing libcadmin(1m).
* Executing: "/var/adm/sw/products/PHSS_25983/pfiles/iux_postload".
NOTE: tlinstall is searching filesystem - please be patient
NOTE: Successfully completed
* Loading_software: Complete
* Build_Kernel: Begin
* Tuned kernel for large swap space: "maxswapchunks 6144".
* Building a new kernel using the command: "/usr/sbin/mk_kernel -o
/stand/vmunix".
WARNING: No such device, tunable, or cdio ehci.
Ignoring the following line.
ehci
WARNING: No such device, tunable, or cdio side_ba.
Ignoring the following line.
side_ba
WARNING: No such device, tunable, or cdio ciss.
Ignoring the following line.
ciss
Generating module: krm...
Compiling /stand/build/conf.c...
Loading the kernel...
Generating kernel symbol table...
* Build_Kernel: Complete
* Boot_From_Client_Disk: Begin
* Rebooting machine as expected.

==========================================
Then during boot-up another error has been encountered and the machine wont boot.

==========================================
alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x3f900000.
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: autofs_link(): File system was registered at index 3.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 6.
probe: port 1 overcurrent 0x0
probe: port 1 overcurrent 0x0
td: claimed Tachyon XL2 Fibre Channel Mass Storage card at 0/4/2/0
td: claimed Tachyon XL2 Fibre Channel Mass Storage card at 0/5/1/0

System Console is on the Built-In Serial Interface
igelan0: INITIALIZING HP A6825-60101 PCI 1000Base-T Adapter at hardware path 0/1/2/0
igelan5: INITIALIZING HP A6847-60101 PCI 1000Base-SX Adapter at hardware path 0/6/1/0
Swap device table: (start & size given in 512-byte blocks)
entry 0 - auto-configured on root device; ignored - can't open device
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
mountfs:opend

linkstamp: Mon Oct 27 01:29:35 EDT 2008
_release_version: @(#) $Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????

PC-Offset Stack Trace (read across, top of stack is 1st):
0x00212458 0x0030aa28 0x0035da94
0x0048327c 0x0035dd70 0x0017a4a4
0x00200164
End Of Stack
============================================

Anyones idea and help is very much appreciated.

Re: Restoring Ignite --- Problem

Bill Hassell — Thu, 06 May 2010 00:12:58 GMT

Several things have gone wrong here.

>> make_tape_recovery -Av -a /dev/rmt/0mn

This looks like the options were borrowed from the long-obsolete make_recovery command. A more useful list would be:

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

>> I have an old rp5470 and now we are migrating to rp4440.

>> panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????

It appears that these are quite different. The Ignite backup command make_tape_recovery does not create a universal installation tape. It is a copy of the source system and designed to be restored on the same or very similar system. It would appear that the target machine (rp4440) has completely different types of disks. So your rp5470 does not have the drivers installed suitable for the rp4440. This includes the disks as well as the interface HBAs.

Similarly, you'll have to take an inventory of the LAN cards and make sure you have drivers for the rp4440 LAN cards.

I am also guessing that the version of Ignite on the rp5470 is very old. Download a current version: C.7.10... Find it at:

http://www.hp.com/go/ignite-ux

Once you have added the required drivers and loaded the latest Ignite/UX, run the make_tape_recovery command as above. Then when restoring the image, be sure to select the Advanced button at the bottom right and check the restore to other hardware option.

Re: Restoring Ignite --- Problem

Marvin L. Diaz — Thu, 06 May 2010 00:18:04 GMT

Hi Bill,

Thanks for the response.

The current config of the rp4440 disk is connected to SmartArray and configured with raid 1+0.

Are there any issues in that aspect?

Re: Restoring Ignite --- Problem

Torsten. — Thu, 06 May 2010 05:43:04 GMT

Your image probably does not have the ciss driver for the smart array.

Install the RAID-01 product and patch the source system with current bundles before making the image.

Re: Restoring Ignite --- Problem

Prasanth V Aravind — Thu, 06 May 2010 05:43:55 GMT

yes .. your guss can be rt ....

> Unable to determine if system hardware is SCA. Configure "sppnuma" to kernel if SCA use is desired.

it mean the hard drive connected with rp4440 is Single Connector Attachment type & the ignite image doesn't have the kernel driver for this.

it seems you have to configure sppnuma on rp5470 server, then take one more ignite backup & try for restore.

i also recommend to update your system with latest HWE available.

Check this..
http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1162691&admit=109447626+1273128148107+28353475

goodluck
Prasanth

Re: Restoring Ignite --- Problem

Matti_Kurkela — Thu, 06 May 2010 07:25:34 GMT

When SCA and "sppnuma" are mentioned together, SCA is more likely to mean "Scalable Computing Architecture": a method for connecting up to 4 V-Class systems together to form one big system.

This was HP's biggest HP-UX system configuration before the introduction of Superdomes.

The message about SCA is just a "NOTE": you don't need to do anything unless you're running on a SCA complex of 2 or more V-Class systems.

The problem is as Bill says: the old installation on the rp5470 is missing some drivers required on the rp4440 hardware.

MK