make_net_recovery problem

[Tim Hempstead_1]

One of my workmates is atempting to reover a new vPar on our Superdome from a make_net recovery image taken of one of the other vPars.

On the console he gets messages as follows:
-----------------------------------------------
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: nfs3_link(): File system was registered at index 4.
NOTICE: autofs_link(): File system was registered at index 6.
NOTICE: cachefs_link(): File system was registered at index 7.
WARNING:5/0/6/0/0/4/0: PCI Device BAR 28 not Configured!
init of hardware not successful. id=10000030 and my_isc=0
WARNING:5/0/6/0/0/4/1: PCI Device BAR 28 not Configured!
init of hardware not successful. id=10000030 and my_isc=1
WARNING:5/0/6/0/0/6/0: PCI Device BAR 24 not Configured!
WARNING:5/0/6/0/0/6/1: PCI Device BAR 24 not Configured!
WARNING:5/0/12/0/0/4/0: PCI Device BAR 28 not Configured!
init of hardware not successful. id=10000030 and my_isc=2
WARNING:5/0/12/0/0/4/1: PCI Device BAR 28 not Configured!
init of hardware not successful. id=10000030 and my_isc=2
WARNING:5/0/12/0/0/6/0: PCI Device BAR 24 not Configured!
WARNING:5/0/12/0/0/6/1: PCI Device BAR 24 not Configured!
iether_ilan_map_memspace: Base addr invalid
iether_preinit: iether0 failing in iether_ilan_map_memspace call.
iether_ilan_map_memspace: Base addr invalid
iether_preinit: iether1 failing in iether_ilan_map_memspace call.
iether_ilan_map_memspace: Base addr invalid
iether_preinit: iether2 failing in iether_ilan_map_memspace call.
iether_ilan_map_memspace: Base addr invalid
iether_preinit: iether3 failing in iether_ilan_map_memspace call.

Host is virtual System Console slave
Swap device table: (start & size given in 512-byte blocks)
entry 0 - auto-configured on root device; ignored - no room
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
read_ss_nvm: Cannot validate NVM - -2
Starting the STREAMS daemons-phase 1
Create STCP device files
Starting the STREAMS daemons-phase 2
$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 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 8323072 Kbytes, lockable: 6410548 Kbytes, available: 7372772 Kbytes

======= 04/11/06 04:26:53 EDT HP-UX Installation Initialization. (Tue Apr 11
04:26:53 EDT 2006)
@(#) Ignite-UX Revision B.5.4.50
@(#) install/init (opt) $Revision: 10.285 $
* Scanning system for IO devices...

System Console is virtual
WARNING:5/0/6/0/0/4/0: PCI De BAR 28 not Configured!
init of hardware not successful. id=10000030 and my_isc=0
WARNING:5/0/6/0/0/4/1: PCI Device BAR 28 not Configured!
init of hardware not successful. id=10000030 and my_isc=1
WARNING:5/0/6/0/0/6/0: PCI Device BAR 24 not Configured!
iether_ilan_map_memspace: Base addr invalid
iether_preinit: iether0 failing in iether_ilan_map_memspace call.
wsio_claim init failed isc=0x4385e400 name=iether
WARNING:5/0/6/0/0/6/1: PCI Device BAR 24 not Configured!
iether_ilan_map_memspace: Base addr invalid
iether_preinit: iether1 failing in iether_ilan_map_memspace call.
wsio_claim init failed isc=0x4385e400 name=iether
WARNING:5/0/12/0/0/4/0: PCI Device BAR 28 not Configured!
init of hardware not successful. id=10000030 and my_isc=0
WARNING:5/0/12/0/0/4/1: PCI Device BAR 28 not Configured!
init of hardware not successful. id=10000030 and my_isc=1
WARNING:5/0/12/0/0/6/0: PCI Device BAR 24 not Configured!
iether_ilan_map_memspace: Base addr invalid
iether_preinit: iether2 failing in iether_ilan_map_memspace call.
wsio_claim init failed isc=0x4385e400 name=iether
WARNING:5/0/12/0/0/6/1: PCI Device BAR 24 not Configured!
iether_ilan_map_memspace: Base addr invalid
iether_preinit: iether3 failing in iether_ilan_map_memspace call.
wsio_claim init failed isc=0x4385e400 name=iether
NOTE: There were no disk devices found during the scan. Make sure that the
destination disks are connected and powered on. You may choose to
scan for more disk drives from next menu on the console.
ERROR: Cannot open /dev/dlpi: No such file or directory (errno = 2)
WARNING: Could not write LAN information file: "/tmp/hw.info"
ERROR: could not find source device "4/0" in ioscan output. You must select
from the list of devices below to use for the source device:
index HW-path Class description
0) 3/10 processor Processor
1) 4/10 processor Processor
2) 7/12 processor Processor
3) 7/13 processor Processor

Enter the index corresponding to the device to use
as the installation source, or 'q' to reboot:
-----------------------------------------------

Where the disk which will be booted from is connected one of the SCSI ports on 5/0/6.

What is also a bit odd is sometimes it goes to this stage and its not possible to get any further as the only devices listed are processors but sometimes it gets a bit further and gives the initial portion of the Ignite setup failing at the nfs mount for recovery ...

Any ideas ....

Tim

[JASH_2]

Tim,

I do not know much about vpars etc yet, but did your collegue just try and install as if restoring to original par, or did he tell it to go into the advanced settings and therefore which disks etc to use.

Sorry if yes, just a thought.

Regards,

JASH

[Tim Hempstead_1]

He is booting the vpar off of the Ignite server to run the recovery. (i.e. vparboot -p name -I ip,path/WINSTALL ). The messages are comming up at the begining of the boot off of the Ignite server prior to the Ignite interface being shown to choose the install type/recovery console etc etc etc ...

Tim

[Tim Hempstead_1]

We found out what was causing these errors. The multifunction cards HP had provided us with were not compatible with our hardware and OS levels hence they were not working correctly. Also by updating Ignite we were able to loose most of these errors as the Ignite boot kernel could now recognise what the cards were. The cards have now been replaced with others which are compatible.

For reference the cards which caused the problems were AB290A's on a PA8700 based SD32000 running 11.11