topic Re: SAS driver problem HPUX in Integrity Servers

SAS driver problem HPUX

David Islas González_1 — Wed, 10 Jan 2007 22:32:21 GMT

Hi everybody, now I´m starting a deployment of an HP Integrity server rx3600. And I have some doubts and problems with the sas controller.

1. Can the the SAS controller create RAID 5 LUNs, or I just can create RAID 1 LUNs???? If I can create RAID 5 LUNs how can I create them, cause I´m applying something like this:

# ./sasmgr add -D /dev/sasd0 -q raid -q level=5 -q enc_bay=1:1,1:2,1:3,1:4,1:5,1:6
and getting the next error:

Driver specific and common library version mismatch. Exiting..

2. I got the last error after I updated the SerialSCSI-00 depot, because when I was booting my system the first time I saw the next message:

sasd: [ALERT] Driver detected a software downgrade.
sasd: The current driver version is unsupported
sasd: for the Serial SCSI HBA at hw path 0/4/1/0.
sasd: Please install the latest SerialSCSI-00 depot ASAP.
Boot device's HP-UX HW path is: 0/4/1/0.0.0.6.0

OH, and I'm getting this error too, after the installation of the SerialSCSI-00 depot,
sending me alerts like this:

From root@sacmux Wed Jan 10 16:28:05 CST 2007
Received: (from root@localhost)
by sacmux (8.11.1/8.11.1) id l0AMS5402334;
Wed, 10 Jan 2007 16:28:05 -0600 (CST)
Date: Wed, 10 Jan 2007 16:28:05 -0600 (CST)
Message-Id: <200701102228.l0AMS5402334@sacmux>
To: root@sacmux
From: root@sacmux
Subject: sacmux: Event Monitor Notification
Status: R

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Wed Jan 10 16:28:05 2007

sacmux sent Event Monitor notification information:

/storage/events/disks/default/0_4_1_0.0.0.6.0
is >= 3.
Its current value is SERIOUS(4).

Event data from monitor:

Event Time..........: Wed Jan 10 16:28:05 2007
Severity............: SERIOUS
Monitor.............: disk_em
Event #.............: 100776
System..............: sacmux

Summary:
Disk at hardware path 0/4/1/0.0.0.6.0 : Software configuration error

Description of Error:

The device was unsuccessful in processing the current request message
because the message contained an invalid field in the command data block.
The request was not processed.

Probable Cause / Recommended Action:

The error most likely indicates that the device is not fully supported by
the current driver. This may or may not cause a problem in the operation
of the device.

Additional Event Data:
System IP Address...: 10.1.1.85
Event Id............: 0x45a5687500000000
Monitor Version.....: B.01.01
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_disk_em.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: ia64 hp server rx3600
OS Version......................: B.11.23
STM Version.....................: C.54.00
EMS Version.....................: A.04.20
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100776

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v

Component Data:
Physical Device Path...: 0/4/1/0.0.0.6.0
Device Class...........: Disk
Inquiry Vendor ID......: HP
Inquiry Product ID.....: IR Volume
Firmware Version.......: HP01
Serial Number..........: unavailable

Product/Device Identification Information:

Logger ID.........: disc30; sdisk
Product Identifier: Disk
Product Qualifier.: HP IR Volume
SCSI Target ID....: 0x06
SCSI LUN..........: 0x00

SCSI Command Data Block:

Command Data Block Contents:
0x0000: 1A 00 1C 00 FF 00

Command Data Block Fields (6-byte fmt):
Command Operation Code...(0x1A)..: MODE SENSE
Logical Unit Number..............: 0
DBD Bit..........................: 0
Page Control Bits................: 0
Page Code Bits...................: 28
Allocation Length................: 255 (0xFF)

Hardware Status: (not present in log record).

SCSI Sense Data:

Undecoded Sense Data:
0x0000: 70 00 05 80 C0 46 04 3E 00 00 00 00 24 00 FF 21

SCSI Sense Data Fields:
Error Code : 0x70
Segment Number : 0x00
Bit Fields:
Filemark : 0
End-of-Medium : 0
Incorrect Length Indicator : 0
Sense Key : 0x05
Information Field Valid : FALSE
Information Field : 0x80C04604
Additional Sense Length : 62
Command Specific : 0x00000000
Additional Sense Code : 0x24
Additional Sense Qualifier : 0x00
Field Replaceable Unit : 0xFF
Sense Key Specific Data Valid : (not applicable)
Sense Key Specific Data : (not applicable)

Sense Key 0x05, ILLEGAL REQUEST, indicates that there was an illegal
parameter in the command data block or in the additional parameters
supplied as data for some commands (FORMAT UNIT, SEARCH DATA, etc.).
This sense key may also indicate that an invalid IDENTIFY message was
received.

The combination of Additional Sense Code and Sense Qualifier (0x2400)
indicates: Invalid field in cdb.

>---------- End Event Monitoring Service Event Notification ----------<

3. Now I don't know what to do, because I got two troubles, first the "driver specific and library common mismatch", and I can not create a RAID 5 LUN.

4. I tried to solve the "driver" problem updating the SAS controller firmware as in this page: http://docs.hp.com/en/AB463-9001A/ch09s02.html?btnNext=next%A0%BB

but I couldn't know if this happened because I only got the message:
Applying...

So I rebooted my system, now the firmware of my sas controller is:

Controller information
------------------------------------------------------------------------
Controller type : SAS1068
EFI BSD version : 2.00.14.00
Firmware version : 1.16.00.00
Channel description : 1 Serial Attached SCSI
Initiator ID : 112
Maximum physical devices : 62
Concurrent commands supported : 511

After telling everybody my sad story... does anybody knows a solution for this???

I appreciate any suggestion.

Regards

Re: SAS driver problem HPUX

Sameer_Nirmal — Wed, 10 Jan 2007 23:38:15 GMT

First of all, RAID 5 is not supported on HPUX and OpenVMS. Hence you are getting mismatch error and the EMS events notification ( for the invalid task you tried with the driver ). On HPUX/OpenVMS, you can only have RAID 1 and a hot spare.

RAID 1,5,6 are only supported with Smart Array SAS Controller on Windows and Linux. Refer the server specifications at
http://h18000.www1.hp.com/products/quickspecs/12595_div/12595_div.HTML

Secondly,the sasd ALERT you got which is a known issue. Refer this and its workaround.
http://docs.hp.com/en/5991-7528/ch01s04.html

Re: SAS driver problem HPUX

David Islas González_1 — Thu, 11 Jan 2007 11:16:22 GMT

Thanks Sameer,

Your suggestions were very helpful, but about the second one of the error.

That's correct, at the begining I got the error:

sasd: [ALERT] Driver detected a software downgrade.sasd: The current driver version is unsupportedsasd: for the Serial SCSI HBA at hw path 0/4/1/0.sasd: Please install the latest SerialSCSI-00 depot ASAP

So I downloaded the last SerialSCSI-00 depot from:

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

And after that I'm getting the alarm I mentioned before:

From root@sacmux Wed Jan 10 16:28:05 CST 2007
Received: (from root@localhost)
by sacmux (8.11.1/8.11.1) id l0AMS5402334;
Wed, 10 Jan 2007 16:28:05 -0600 (CST)
Date: Wed, 10 Jan 2007 16:28:05 -0600 (CST)
Message-Id: <200701102228.l0AMS5402334@sacmux>
To: root@sacmux
From: root@sacmux
Subject: sacmux: Event Monitor Notification
Status: R

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Wed Jan 10 16:28:05 2007

sacmux sent Event Monitor notification information:

/storage/events/disks/default/0_4_1_0.0.0.6.0
is >= 3.
Its current value is SERIOUS(4).

Event data from monitor:

Event Time..........: Wed Jan 10 16:28:05 2007
Severity............: SERIOUS
Monitor.............: disk_em
Event #.............: 100776
System..............: sacmux

Summary:
Disk at hardware path 0/4/1/0.0.0.6.0 : Software configuration error

Description of Error:

The device was unsuccessful in processing the current request message
because the message contained an invalid field in the command data block.
The request was not processed.

Probable Cause / Recommended Action:

The error most likely indicates that the device is not fully supported by
the current driver. This may or may not cause a problem in the operation
of the device.

Additional Event Data:
System IP Address...: 10.1.1.85
Event Id............: 0x45a5687500000000
Monitor Version.....: B.01.01
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_disk_em.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: ia64 hp server rx3600
OS Version......................: B.11.23
STM Version.....................: C.54.00
EMS Version.....................: A.04.20
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100776

Is this depot that I downloaded different from the one you told me before??

Regards

Re: SAS driver problem HPUX

Sameer_Nirmal — Thu, 11 Jan 2007 13:48:49 GMT

As per the workaround mentioned in the link posted before sasd alert is to install the driver SASD B.11.23.03 . However the version you might have installed is SASD B.11.23.03.01 which is the latest one.

It seems that you are getting the alert inspite of having latest bundle. Did you follow the installation instructions for the SASD driver given at

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

Re: SAS driver problem HPUX

David Islas González_1 — Thu, 11 Jan 2007 19:37:49 GMT

Sorry I didn't read the full procedure for the SerialSCSI-00 depot, I had to install previously the COMMON patch.

THANKS A LOT FOR YOUR HELP!!!

Re: SAS driver problem HPUX

Andrew Merritt_2 — Fri, 19 Jan 2007 04:11:21 GMT

Hi David,
See my response in http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1091575 which explains why the EMS event 100776 is being delivered and how to suppress it.

Andrew