rx6600 recovery using Ignite tape - sas driver error

[kavanagh_1]

Anyone help with this problem?

I created Ignite tapes (make_tape_recovery -a /dev/rmt/0mn -x inc_entire=vg00) on an rx4640 using Ignite version C.7.2.94 and also on a rx2620. OS=11iv2

These tapes were then used to clone to two rx6600 servers. One recovery worked fine and the other failed. The rx4640 one failed.

The error message "SAS driver No match for pun = 3" occured when the server rebooted after the ignite archive was loaded. See below for the full message.

There is a difference in the OE release, the failing one was 6 months older than the good one.

I think the problem is due to the SAS driver, the rx4640 has Serial SCSI-00 version B.11.23.01.04 while the rx2620 has B.11.23.03. The latest is B.11.23.0706. I have not yet proved this by updating the rx4640 OE and making a new tape followed by recovery to the rx6600, but I am hopeful it will work.

Question 1. Am I on the correct track here ?

In a DR situation it is very likely newer servers will be supplied by the hosting company. Newer cards mean newer drivers which may not be on the Ignite tape.

Question 2. Has anyone got a solution to this problem other than making sure the drivers are always kept up to date on the source server?

Regards

David


Error message

Memory Class Setup
-------------------------------------------------------------------------
Class Physmem Lockmem Swapmem
-------------------------------------------------------------------------
System : 32738 MB 32738 MB 32738 MB
Kernel : 32738 MB 32738 MB 32738 MB
User : 30984 MB 27003 MB 27109 MB
-------------------------------------------------------------------------


Loaded ACPI revision 2.0 tables.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 8.
NOTICE: USB device attached. Identification String:
Devices/Device/USB/hp/Unknown/0_a1
<2.1.3.1008.294.161>
NOTICE: USB device attached. Identification String:
Devices/BulkScsiProtocol/USB/hp/Unknown/0_a1
<2.310.3.1008.294.161>
SAS driver No match for pun = 3
gio: Error configuring root device using EFI hw paths
SAS driver No match for pun = 3

System Console is on the Built-In Serial Interface
iether0: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/4/2/0
iether2: INITIALIZING HP AB290-60001 PCI/PCI-X 1000Base-T 2-port U320 SCSI/2-port 1000B-T Combo Adapter at hardware path 0/7/1/0/6/0
iether3: INITIALIZING HP AB290-60001 PCI/PCI-X 1000Base-T 2-port U320 SCSI/2-port 1000B-T Combo Adapter at hardware path 0/7/1/0/6/1
iether1: INITIALIZING HP AB352-60003 PCI/PCI-X 1000Base-T Dual-port Core at hardware path 0/4/2/1
WARNING: Open failed on device 0x1f010002 (error 0x6).
WARNING: Can not read LVM BOOT information (lvmrec).
WARNING: Open failed on device 0x1f010002 (error 0x6).

[Torsten.]

OS support for the rx6600 came in 06/2006 (or 09/2006? - not sure at this moment).

Any older release may have a problem unless you install all hardware enablement patches.

[Steven E. Protter]

Shalom,

The earliest OS that can be installed by any means on an rx6600 system is 11iv2 September 2006.

Anything earlier than that will fail to install.

HP showed me a document on that when I was testing this in their Israel lab back in February. I forgot to find a link.

So you may be on track with your sas driver problem, or you may not.

IF the image is before September 2006, its not certified, supported and you need to get an image from a system that is at least updated by semi-annual patch set that is later than that date.

The rx3660 and rx6600 system are similar and probably an Ignite image from one can go to the other. Going from rx4640 to other systems is possible but complications are possible. I don't know HP's stance on this.

SEP

[kavanagh_1]

Thanks for your replies.

Am I correct in assuming that once this restore problem has occurred there is no option other than to ensure that the hardware enablement patches are installed on the rx4640 and a new tape made ?

Just for the record, the same rx4640 tape was used to clone to a rx8640 with no problems.

David

[Torsten.]

I'm lost now in how many tapes you have and what tape is backuped from which machine and used to boot ...


In fact (as mentioned before) the new hardware of the rx6600 needs a current OS release and the rx4640 may need it to if you have new Itanium CPUs installed.

BTW, it is always a good idea to keep the patch level current.

[kavanagh_1]

Sorry to the message was not clear Torsten. I'll try again!

Having got the sas driver error while attempting to use the rx4640 ignite tape cloning onto a rx6600, as far I understand there is no way out of this other than go back to the rx4640, apply the HWE patches, make a new tape and try again. Is this correct?

David

[Torsten. · Accepted solution]

Correct.
You need the serial scsi driver:

http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=SerialSCSI-00

[Steven E. Protter]

Shalom,

Once again, I was not clear.

The OS on the rx4640 was released before September 2006. It will never work on an rx6600. The rx6600 must have September 2006 or later OS.

This clone as originally defined will not work.

SEP

[Torsten.]

According to this thread it is enough to install the current patch bundles and the driver:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1134054

But I would recommend to use a current OS release anyway.

[kavanagh_1]

Thanks for the advice. Now for an update

I was not able to try out installing serial-scsi on the rx4640, creating a new ignite tape and cloning to the rx6600 as the rx6600 had gone into production. However I tried it between an rx4640 and an rx2660 (with inbuilt hw raid to two SAS disks).

1st pass
The rx4640 (11iv2) was updated with June 2007 HWE + QPK + latest version of Ignite. Ran make_tape_recovery and used it to ignite the rx2660 (Dual boot method DVD OE then select the Ignite tape). This failed with the sas driver problem as before.

2nd pass
CommonIO + latest serialscsi + patches installed as advised. Another Ignite tape made and used to ignite the rx2660. Much better but still problems. ioscan showed both c2 and c3 hw paths for the same disk device!. Also no DVD drive! vgdisplay vg00 gave disk path errors. strings lvmtab showed it should be c2. Removed /etc/ioconfig + /stand/ioconfig and rebooted. Did the usual ioinit -c when requested to sort out devices. vgdisplay now ok. (as was lvlnboot -v)

I discovered that the DVD was a USB device on the rx2660 so I then did a swinstall of the latest USB-00 driver over the network. This fixed the DVD drive. I then did an update-ux to the June FOE from the DVD drive. Took ages but did manage it. Now all working.

The bit that has come as a suprise to me was that I needed to install the latest serialscsi + USB drivers. I thought the HWE bundle would have given me the necessary update to the rx4640 to enable the clone to the rx2660.Not so, I needed those drivers.

Can anyone explain why HWE was not enough ?

David