Can be add new kernel driver modules in Ignite Tape Image

[Joshy PJ]

                        Currently we are in the migration phase of IA to IA @NSB Jeddah & we had completed their Development server IA to IA migration via DRD clone method as per the attached procedure.

And in the  case of Production server customer insisting us to do the Ignite Tape recovery as the DRD version on the Production server is old &  update will require a  reboot.

So we had taken the Ignite image from the all the Source server & restored to the target server, out of the 10 server 6 went fine & 4 server  crashed because of the driver module issue.

Source System -OS: B.11.31 (EOE)  Model: ia64 hp superdome server SD64B  Ignite Version-C.7.9.254 ,npar

Target System – SD2 Npar

Steps which we are followed for doing ignite tape backup

1.Updated the Ignite version @Source

2.Taken the Ignite Tape backup via make_tape_recovery -I -x inc_entire=vg00 -a /dev/rmt/??mn

3.Restored the same to Target Machine

In 4 systems we got following errors & it continuously rebooting

  gio: Error configuring root device using EFI hw paths

iether4: INITIALIZING HP AD222-60001 PCIe 1000Base-T 2-port 4Gb FC/2-port 1000B-T Combo Adapter at hardware path 42/0/1/0/0/0/0/2/0/0/0

iether5: INITIALIZING HP AD222-60001 PCIe 1000Base-T 2-port 4Gb FC/2-port 1000B-T Combo Adapter at hardware path 42/0/1/0/0/0/0/2/0/0/1

    System Console is on the Built-In Serial Interface

AF_INET socket/streams output daemon running, pid 47

afinet_prelink: module installed

Starting the STREAMS daemons-phase 1

    Swap device table:  (start & size given in 512-byte blocks)

        entry 0 - auto-configured on root device; 4/0/2/3/0/0/4.1 usbcomposite

4/0/2/3/0/0/4.1.0 hid

4/0/2/3/0/0/4.1.1 hid

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

VFS_MOUNTROOT error information:

0:(hfs) 6

1:(nfs) 223

9:(vxfs) 6

10:(nfs3) 223

11:(nfs4) 223

12:(autofs) 251

15:(cifs) 223

17:(dnlc_neg_fs) 251

Message buffer contents after system crash:

panic: VFS_MOUNTROOT: READ_ONLY: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????

Stack Trace:

  IP                  Function Name

  0xe000000001f45d20  vfs_mountroot+0x700

  0xe00000000160c9a0  im_mountroot+0x40

  0xe000000001f37900  DoCalllist+0x390

End of Stack Trace

As per our understanding the Ignite image doesn’t contain the required kernel modules for the target System (SD2 npar) . In the case of DRD , we are building a new kernel for the Target machine in the DRD clone using attached procedure & it went fine.

In the case of Ignite Tape backup, one solution we had given to customer was create a new kernel at Source machine wef to the new kernel modules prior to the Ignite backup ,run the Ignite tape backup , install it on the Target machine & boot from the newly create kernel @Target machine. But customer is not ready to follow this at their production server.   

So my question is can we modify /inject the Required driver modules to the Ignite Image via Recovery Shell using script (kernel parameters can be modify via recovery shell) or any other method via EFI shell

We have the list of drivers required for the target machine .If any alternate solution please let us know. I had attached all the log file which got for the crashed system