A3x00
Command Line Procedures
INDEX
2 Setting Path
2 Checking the whole Array
3 Checking the Controllers
4 Checking the Disks
5 Checking the Logical Devices
7 Recovering Disk Problems
7 Recovering Controller Problems
8 Recovering Logical Devices
9 Upgrading Firmware
Appendices:
A Decoding rmlog.log
2 A3500 Trouble Shooting from the Command Line
Setting up the path
# ksh
# PATH=$PATH:/usr/lib/osa/bin
# export PATH
This will need to be run every time you log in, unless it is added to the /.profile file.
Looking for errors
- Check /var/adm/messages
- LUNs offline
- SCSI errors
- Check rmlog.log
- # logutil /usr/lib/osa/rmlog.log
- See Attachment A for notes on how to decode the log
- See /etc/raid/raidcode.txt for more on decoding
- Look for patterns of errors in the logs
Here is some examples of useful commands, and some outputs that you might expect to see:-
# healthck -a
**********************************************************************************
Health Check Summary Information
p4u-5500a_002: Multiple Unresponsive Drives at Drive [2,2];[2,3];[2,5];[2,8];[2,9];[2,12];[2,13]
healthck succeeded!
**********************************************************************************
3
To Check Controllers
# rdacutil -i p4u-5500a_002
************************************************************************************
p4u-5500a_002: dual-active
Active controller a (c1t5d0s0) units: 0 2
Active controller b (c2t4d1s0) units: 1
rdacutil succeeded!
************************************************************************************
# lad
************************************************************************************
c1t5d0s0 1T81410687 LUNS: 0 2
c2t4d1s0 1T82623877 LUNS: 1
************************************************************************************
# storutil -c c1t5d0s0 -d
************************************************************************************
p4u-5500a_002:
Controller A: 1T81410687 ( c1t5d0s0 )
Controller B: 1T82623877 ( c2t4d1s0 )
Independent Controller Configuration: OFF
************************************************************************************
4
To Check Disks
# drivutil -i c1t5d0s0
************************************************************************************
Drive Information for p4u-5500a_002
Location Capacity Status Vendor Product Firmware Serial
(MB) ID Version Number
[1,0] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G074
[2,0] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558 LG433750
[3,0] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G072
[4,0] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G086
[5,0] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G053
[1,1] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G083
[2,1] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558 LG461369
[3,1] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G075
[4,1] 17274 Optimal FUJITSU MAA3182S SUN18G 1907 00H22912
[5,1] 17274 Optimal FUJITSU MAA3182S SUN18G 1907 00H22718
[1,2] 17274 Optimal FUJITSU MAA3182S SUN18G 1907 00H24391
[2,2] 0 Unresponsive
[3,2] 17274 Optimal FUJITSU MAA3182S SUN18G 1907 00H24741
[2,3] 0 Unresponsive
[2,4] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558 LG461444
[2,5] 0 Unresponsive
[2,8] 0 Unresponsive
[4,8] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G083
[5,8] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G082
[2,9] 0 Unresponsive
[2,10] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558 LG432787
[2,11] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558 LG461468
[2,12] 0 Unresponsive
[2,13] 0 Unresponsive
drivutil succeeded!
************************************************************************************
5
To Check the Logical Devices (LUNs and Drive Groups)
# drivutil -d c1t5d0s0
************************************************************************************
Drives in Group for p4u-5500a_002
Group Drive List [Channel,Id]
Unassigned [3,2]; [4,8]; [5,8];
Group 1: [1,0]; [3,0]; [4,0]; [5,0];
Group 2: [2,0]; [2,1]; [2,2]; [2,3]; [2,4]; [2,5]; [2,8]; [2,9]; [2,10]; [2,11]; [2,12]; [2,13];
Group 3: [1,1]; [3,1]; [4,1]; [5,1]; [1,2];
drivutil succeeded!
************************************************************************************
# drivutil -I p4u-5500a_002
************************************************************************************
Group Information for p4u-5500a_002
Group No. of RAID No. of Total Remaining
LUNs Level Drives Space(MB) Space(MB)
Unassigned 0 - 3 51704 51704
1 1 0 4 68938 68937
2 1 1 12 24325 0
3 1 5 5 68938 0
drivutil succeeded!
************************************************************************************
6
# drivutil -p 0 c1t5d0s0
************************************************************************************
p4u-5500a_002 unit 0: optimal
drivutil succeeded!
************************************************************************************
# drivutil -l p4u-5500a_002
***********************************************************************************
Logical Unit Information for p4u-5500a_002
LUN Group Device RAID Capacity Status
Name Level (MB)
0 1 c1t5d0s0 0 1 Optimal
1 2 c2t4d1s0 1 24325 Optimal
2 3 c1t5d2s0 5 68938 Optimal
drivutil succeeded!
************************************************************************************
7 Recovery
Disks
To try and ’unfail’ a disk in the state Replaced
Failed
Unresponsive, do
# drivutil -u <drive number> <controller id>
Where <drive number> is the tray number, followed by the disk number, with no separator, and the
<controller id> is the name of the array, or the ID of the specific controller
e.g. # drivutil -u 210 c2t4d0s0
(This will ’unfail’ disk 10 on tray 2, on the controller c2t4d0s0)
If this does not work, try and manually fail the drive, and then try and ’unfail’ it again afterwards. To
fail the drive, do:
# drivutil -f <drive number> <controller id>
e.g. # drivutil -f 210 c2t4d0s0
Controllers
To ’unfail’ a controller. Normally this would succeed if the controller was held in reset (all lights on
the controller on).
# rdacutil -u <raid module specifier> or
# rdacutil -U <raid module specifier>
e.g. # rdacutil -u p4u-5500a_002
This will bring the controller back online, and should move the LUNs so that they are balanced in the
same way as before the failure. If you use the lower case ’u’ as the argument then normal checks will
be made before the controller is put back on line, and if you use the the uppercase ’U’ then the controller
will come back on line without any checks being made.
8
If required you can manually fail one of the controllers. This will automatically move the LUNs on the
controller that we are trying to fail on to the controller that will remain ’optimal’.
# rdacutil -f <id of the controller you want to fail>
# rdacutil -F <id of alternate controller to the one you want to fail>
Logical Devices
To revive a LUN from a dead state:
# drivutil -r <LUN number> <raid module specifier>
e.g. # drivutil -r 2 p4u-5500a_002
You must now run fsck on the file systems on the LUN, and then mount it, and check the data. The sanity
of this data is not guaranteed. (In fact it may be complete insane!)
9
Upgrading Firmware
To check the current version of the firmware that is installed:
# raidutil -i <controller id>
e.g. # raidutil -i c1t4d0s0
***********************************************************************************
LUNs found on c1t4d0s0
LUN 0 RAID 0 1 MB
LUN 2 RAID 5 68938 MB
Vendor ID Symbios
ProductID StorEDGE A3000
Product Revision 0205
Boot Level 02.05.01.00
Boot Level Date 12/02/97
Firmware Level 02.05.02.15
Firmware Date 09/08/98
raidutil succeeded
***********************************************************************************
To quisce the one of the controllers, so that it can be upgraded.
If the controllers are currently active/active, then run the following command
# raidutil -m 1 <raid module specifier>
e.g. # raidutil -m 1 p4u-5500a_002
This will make controller A active, and controller B passive. You can now upgrade controller B.
Run the command again, and the currently active controller will become passive, and vice versa. This
will allow you to upgrade controller A
10
Then run the following command to put the controllers back into an active/active state.
# rdacutil -m 2 -b <raid module specifier>
e.g. # rdacutil -m 2 -b c1t4d0s0
(The -b will rebalance the LUNs to a ’nominal’ configuration)
To actually do the upgrade, you will need to load the relevant patch (currently 106513), which will put
the firmware files in the usr/lib/osa/fw/ directory.
The files will be proceeded with the firmware level, and end with a suffix, such as .apd or .fcd.
e.g. /usr/lib/osa/fw/02050211.apd
All the files with the relevant firmware number prefix should be installed.
To install the firmware run the command:
# fwutil <file> <raid controller specifier>
e.g. fwutil /usr/lib/osa/fw/02050211.apd p4u-5500a_002
After the upgrades, check the firmware levels, with the command:
# raidutil -i <controller id>
e.g. # raidutil -i c1t4d0s0
Attachment A
Decoding rmlog.log
First run the command:
# logutil /usr/lib/osa/rmlog.log
Record # 409:
Host: bart
Date: 09/28/97
Time: 16:22:18
Device: c2t5d6s0
Controller: 1T1234567JT
Error Type: 06
LUN: 03
LUN Status: 01
Drive: 2E
Error Number: 3F80
Sense Data:
7000 0600 0000 0098 0000 0000 3F80 2E00
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0008 0500 0000 0000 0000 0000
0000 0000 0F05 3154 3731 3332 3230 3736
2020 2020 2020 0204 1D00 0003 0100 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0050 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 000
The first line tells you the event number, followed by the
name of the host. Next is the date, time of the event. The drive
invloved, the controller serial number of the A3000 controller invloved.
Next would be the type of error, the LUN number, the location of the
actual drive, the error number and then the sense data.
LUN Status Definition:
00 => Optimal condition
20 => Optimal with parity scan in progress
01 => Degraded LUN- waiting for repair action
41 => Degraded LUN - replaced drive being formatted.
02 => Degraded LUN - replaced drive being reconstructed
04 => Dead LUN
44 => Dead LUN - format in progress
54 => Dead LUN - creation in progress
74 => Dead LUN - wrong drive removed/replaced
Error Number Definition:
This information is in the raidcode.txt on the sonoma page or
in RM6 6.1
Error Type:
This will always be byte 2 in the sense data, they are defined as
follows:
00 => No Sense
01 => Recovered Error
02 => Not Ready
03 => Medium Error
04 => Hardware Error
05 => Illegal Request
06 => Unit Attention
07 => Data Protect
0B => Aborted Command
0E => Miscompare
In the example above, you can see that it is telling you that the error
has to do with "Unit Attention:.
Drive Location:
The 362x controller reports drive location start with byte offset 0, and
going from bottom to top, it would be 0,1,2,3 and 4. This would correspond
with drive channels 1,2,3,4 and 5 that RM6 uses. The drives are targeted
from 8 thru E in the firmware. In our example above of drive location
2E, that would be the third tray from the bottom and the last drive in the
tray. RM6 would see this drive 3,14.
Sense Data Decoding:
Byte 2 is the sense key inforamtion
byte 7 is Additional Sense Length, this value will indicate the number
of additional sense bytes to follow.
Bytes 8-11 will always be zero unless the has been unsuccessful Reassign
blocks.
Bytes 12-13, this information is in the raidcode.txt file or on the sonoma
web page.
Byte 14, Field Replaceable Unit Code, this is also in the raidcode.txt file.
Bytes 37-40, Error Detection Point, will indicate were in the software
the error was detected.
Bytes 52-53, Host Descriptor:
LSB:
bit 0 => data is being transfered 16-bit wide
bit 1 => Reserved
bit 2 => wide negotiation completed successfully
bit 3-7 => Reserved
MSB:
0 => Message using host
1 => Reselectable host
2 => data is being transferred synchronously(bit off means
asynchronously data transfer)
3 => synchronous negotiation successful
4 => Reserved
5 => AEN supported
6 => Polled AEN supported
7 => Reserved
Bytes 54-69, Controller serial number
Bytes 70-73, Array software Revision
Byte 75, LUN Number
Byte 76, LUN status
Byte 101, Raid Level, a value off 255 indicates that the LUN Raid
level is undefined
To break down on sense data a little:
byte 2 7 1213 14
7000 0600 0000 0098 0000 0000 3F80 2E00 sense data
0000 0000 0000 0000 0000 0000 0000 0000 sense data
byte 37 38
0000 0000 0008 0500 0000 0000 0000 0000 sense data
byte 5253 5455 5657 5859 6061 6263
0000 0000 0F05 3154 3731 3332 3230 3736 sense data
byte6465 6667 6869 7071 7273 75 76
2020 2020 2020 0204 1D00 0003 0100 0000 sense data
0000 0000 0000 0000 0000 0000 0000 0000 sense data
byte 101
0000 0000 0050 0000 0000 0000 0000 0000 sense data
0000 0000 0000 0000 0000 0000 0000 000 sense data
Command Line Procedures
INDEX
2 Setting Path
2 Checking the whole Array
3 Checking the Controllers
4 Checking the Disks
5 Checking the Logical Devices
7 Recovering Disk Problems
7 Recovering Controller Problems
8 Recovering Logical Devices
9 Upgrading Firmware
Appendices:
A Decoding rmlog.log
2 A3500 Trouble Shooting from the Command Line
Setting up the path
# ksh
# PATH=$PATH:/usr/lib/osa/bin
# export PATH
This will need to be run every time you log in, unless it is added to the /.profile file.
Looking for errors
- Check /var/adm/messages
- LUNs offline
- SCSI errors
- Check rmlog.log
- # logutil /usr/lib/osa/rmlog.log
- See Attachment A for notes on how to decode the log
- See /etc/raid/raidcode.txt for more on decoding
- Look for patterns of errors in the logs
Here is some examples of useful commands, and some outputs that you might expect to see:-
# healthck -a
**********************************************************************************
Health Check Summary Information
p4u-5500a_002: Multiple Unresponsive Drives at Drive [2,2];[2,3];[2,5];[2,8];[2,9];[2,12];[2,13]
healthck succeeded!
**********************************************************************************
3
To Check Controllers
# rdacutil -i p4u-5500a_002
************************************************************************************
p4u-5500a_002: dual-active
Active controller a (c1t5d0s0) units: 0 2
Active controller b (c2t4d1s0) units: 1
rdacutil succeeded!
************************************************************************************
# lad
************************************************************************************
c1t5d0s0 1T81410687 LUNS: 0 2
c2t4d1s0 1T82623877 LUNS: 1
************************************************************************************
# storutil -c c1t5d0s0 -d
************************************************************************************
p4u-5500a_002:
Controller A: 1T81410687 ( c1t5d0s0 )
Controller B: 1T82623877 ( c2t4d1s0 )
Independent Controller Configuration: OFF
************************************************************************************
4
To Check Disks
# drivutil -i c1t5d0s0
************************************************************************************
Drive Information for p4u-5500a_002
Location Capacity Status Vendor Product Firmware Serial
(MB) ID Version Number
[1,0] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G074
[2,0] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558 LG433750
[3,0] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G072
[4,0] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G086
[5,0] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G053
[1,1] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G083
[2,1] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558 LG461369
[3,1] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G075
[4,1] 17274 Optimal FUJITSU MAA3182S SUN18G 1907 00H22912
[5,1] 17274 Optimal FUJITSU MAA3182S SUN18G 1907 00H22718
[1,2] 17274 Optimal FUJITSU MAA3182S SUN18G 1907 00H24391
[2,2] 0 Unresponsive
[3,2] 17274 Optimal FUJITSU MAA3182S SUN18G 1907 00H24741
[2,3] 0 Unresponsive
[2,4] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558 LG461444
[2,5] 0 Unresponsive
[2,8] 0 Unresponsive
[4,8] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G083
[5,8] 17274 Optimal FUJITSU MAA3182S SUN18G 1705 00G082
[2,9] 0 Unresponsive
[2,10] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558 LG432787
[2,11] 4094 Optimal SEAGATE ST34501WCSUN4.2G 0558 LG461468
[2,12] 0 Unresponsive
[2,13] 0 Unresponsive
drivutil succeeded!
************************************************************************************
5
To Check the Logical Devices (LUNs and Drive Groups)
# drivutil -d c1t5d0s0
************************************************************************************
Drives in Group for p4u-5500a_002
Group Drive List [Channel,Id]
Unassigned [3,2]; [4,8]; [5,8];
Group 1: [1,0]; [3,0]; [4,0]; [5,0];
Group 2: [2,0]; [2,1]; [2,2]; [2,3]; [2,4]; [2,5]; [2,8]; [2,9]; [2,10]; [2,11]; [2,12]; [2,13];
Group 3: [1,1]; [3,1]; [4,1]; [5,1]; [1,2];
drivutil succeeded!
************************************************************************************
# drivutil -I p4u-5500a_002
************************************************************************************
Group Information for p4u-5500a_002
Group No. of RAID No. of Total Remaining
LUNs Level Drives Space(MB) Space(MB)
Unassigned 0 - 3 51704 51704
1 1 0 4 68938 68937
2 1 1 12 24325 0
3 1 5 5 68938 0
drivutil succeeded!
************************************************************************************
6
# drivutil -p 0 c1t5d0s0
************************************************************************************
p4u-5500a_002 unit 0: optimal
drivutil succeeded!
************************************************************************************
# drivutil -l p4u-5500a_002
***********************************************************************************
Logical Unit Information for p4u-5500a_002
LUN Group Device RAID Capacity Status
Name Level (MB)
0 1 c1t5d0s0 0 1 Optimal
1 2 c2t4d1s0 1 24325 Optimal
2 3 c1t5d2s0 5 68938 Optimal
drivutil succeeded!
************************************************************************************
7 Recovery
Disks
To try and ’unfail’ a disk in the state Replaced
Failed
Unresponsive, do
# drivutil -u <drive number> <controller id>
Where <drive number> is the tray number, followed by the disk number, with no separator, and the
<controller id> is the name of the array, or the ID of the specific controller
e.g. # drivutil -u 210 c2t4d0s0
(This will ’unfail’ disk 10 on tray 2, on the controller c2t4d0s0)
If this does not work, try and manually fail the drive, and then try and ’unfail’ it again afterwards. To
fail the drive, do:
# drivutil -f <drive number> <controller id>
e.g. # drivutil -f 210 c2t4d0s0
Controllers
To ’unfail’ a controller. Normally this would succeed if the controller was held in reset (all lights on
the controller on).
# rdacutil -u <raid module specifier> or
# rdacutil -U <raid module specifier>
e.g. # rdacutil -u p4u-5500a_002
This will bring the controller back online, and should move the LUNs so that they are balanced in the
same way as before the failure. If you use the lower case ’u’ as the argument then normal checks will
be made before the controller is put back on line, and if you use the the uppercase ’U’ then the controller
will come back on line without any checks being made.
8
If required you can manually fail one of the controllers. This will automatically move the LUNs on the
controller that we are trying to fail on to the controller that will remain ’optimal’.
# rdacutil -f <id of the controller you want to fail>
# rdacutil -F <id of alternate controller to the one you want to fail>
Logical Devices
To revive a LUN from a dead state:
# drivutil -r <LUN number> <raid module specifier>
e.g. # drivutil -r 2 p4u-5500a_002
You must now run fsck on the file systems on the LUN, and then mount it, and check the data. The sanity
of this data is not guaranteed. (In fact it may be complete insane!)
9
Upgrading Firmware
To check the current version of the firmware that is installed:
# raidutil -i <controller id>
e.g. # raidutil -i c1t4d0s0
***********************************************************************************
LUNs found on c1t4d0s0
LUN 0 RAID 0 1 MB
LUN 2 RAID 5 68938 MB
Vendor ID Symbios
ProductID StorEDGE A3000
Product Revision 0205
Boot Level 02.05.01.00
Boot Level Date 12/02/97
Firmware Level 02.05.02.15
Firmware Date 09/08/98
raidutil succeeded
***********************************************************************************
To quisce the one of the controllers, so that it can be upgraded.
If the controllers are currently active/active, then run the following command
# raidutil -m 1 <raid module specifier>
e.g. # raidutil -m 1 p4u-5500a_002
This will make controller A active, and controller B passive. You can now upgrade controller B.
Run the command again, and the currently active controller will become passive, and vice versa. This
will allow you to upgrade controller A
10
Then run the following command to put the controllers back into an active/active state.
# rdacutil -m 2 -b <raid module specifier>
e.g. # rdacutil -m 2 -b c1t4d0s0
(The -b will rebalance the LUNs to a ’nominal’ configuration)
To actually do the upgrade, you will need to load the relevant patch (currently 106513), which will put
the firmware files in the usr/lib/osa/fw/ directory.
The files will be proceeded with the firmware level, and end with a suffix, such as .apd or .fcd.
e.g. /usr/lib/osa/fw/02050211.apd
All the files with the relevant firmware number prefix should be installed.
To install the firmware run the command:
# fwutil <file> <raid controller specifier>
e.g. fwutil /usr/lib/osa/fw/02050211.apd p4u-5500a_002
After the upgrades, check the firmware levels, with the command:
# raidutil -i <controller id>
e.g. # raidutil -i c1t4d0s0
Attachment A
Decoding rmlog.log
First run the command:
# logutil /usr/lib/osa/rmlog.log
Record # 409:
Host: bart
Date: 09/28/97
Time: 16:22:18
Device: c2t5d6s0
Controller: 1T1234567JT
Error Type: 06
LUN: 03
LUN Status: 01
Drive: 2E
Error Number: 3F80
Sense Data:
7000 0600 0000 0098 0000 0000 3F80 2E00
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0008 0500 0000 0000 0000 0000
0000 0000 0F05 3154 3731 3332 3230 3736
2020 2020 2020 0204 1D00 0003 0100 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0050 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 000
The first line tells you the event number, followed by the
name of the host. Next is the date, time of the event. The drive
invloved, the controller serial number of the A3000 controller invloved.
Next would be the type of error, the LUN number, the location of the
actual drive, the error number and then the sense data.
LUN Status Definition:
00 => Optimal condition
20 => Optimal with parity scan in progress
01 => Degraded LUN- waiting for repair action
41 => Degraded LUN - replaced drive being formatted.
02 => Degraded LUN - replaced drive being reconstructed
04 => Dead LUN
44 => Dead LUN - format in progress
54 => Dead LUN - creation in progress
74 => Dead LUN - wrong drive removed/replaced
Error Number Definition:
This information is in the raidcode.txt on the sonoma page or
in RM6 6.1
Error Type:
This will always be byte 2 in the sense data, they are defined as
follows:
00 => No Sense
01 => Recovered Error
02 => Not Ready
03 => Medium Error
04 => Hardware Error
05 => Illegal Request
06 => Unit Attention
07 => Data Protect
0B => Aborted Command
0E => Miscompare
In the example above, you can see that it is telling you that the error
has to do with "Unit Attention:.
Drive Location:
The 362x controller reports drive location start with byte offset 0, and
going from bottom to top, it would be 0,1,2,3 and 4. This would correspond
with drive channels 1,2,3,4 and 5 that RM6 uses. The drives are targeted
from 8 thru E in the firmware. In our example above of drive location
2E, that would be the third tray from the bottom and the last drive in the
tray. RM6 would see this drive 3,14.
Sense Data Decoding:
Byte 2 is the sense key inforamtion
byte 7 is Additional Sense Length, this value will indicate the number
of additional sense bytes to follow.
Bytes 8-11 will always be zero unless the has been unsuccessful Reassign
blocks.
Bytes 12-13, this information is in the raidcode.txt file or on the sonoma
web page.
Byte 14, Field Replaceable Unit Code, this is also in the raidcode.txt file.
Bytes 37-40, Error Detection Point, will indicate were in the software
the error was detected.
Bytes 52-53, Host Descriptor:
LSB:
bit 0 => data is being transfered 16-bit wide
bit 1 => Reserved
bit 2 => wide negotiation completed successfully
bit 3-7 => Reserved
MSB:
0 => Message using host
1 => Reselectable host
2 => data is being transferred synchronously(bit off means
asynchronously data transfer)
3 => synchronous negotiation successful
4 => Reserved
5 => AEN supported
6 => Polled AEN supported
7 => Reserved
Bytes 54-69, Controller serial number
Bytes 70-73, Array software Revision
Byte 75, LUN Number
Byte 76, LUN status
Byte 101, Raid Level, a value off 255 indicates that the LUN Raid
level is undefined
To break down on sense data a little:
byte 2 7 1213 14
7000 0600 0000 0098 0000 0000 3F80 2E00 sense data
0000 0000 0000 0000 0000 0000 0000 0000 sense data
byte 37 38
0000 0000 0008 0500 0000 0000 0000 0000 sense data
byte 5253 5455 5657 5859 6061 6263
0000 0000 0F05 3154 3731 3332 3230 3736 sense data
byte6465 6667 6869 7071 7273 75 76
2020 2020 2020 0204 1D00 0003 0100 0000 sense data
0000 0000 0000 0000 0000 0000 0000 0000 sense data
byte 101
0000 0000 0050 0000 0000 0000 0000 0000 sense data
0000 0000 0000 0000 0000 0000 0000 000 sense data