Document fins/I0612-1
FIN #: I0612-1
SYNOPSIS: RM6 may detect a non-existent 2MB dacstore on factory formatted hard
disk drives
DATE: Sep/08/00
KEYWORDS: RM6 may detect a non-existent 2MB dacstore on factory formatted hard
disk drives
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
SYNOPSIS: RM6 may detect a non-existent 2MB dacstore on factory
formatted hard disk drives.
TOP FIN/FCO REPORT: No
PRODUCT_REFERENCE: StorEdge Array Configuration
PRODUCT CATEGORY: Storage / Disk
PRODUCTS AFFECTED: A1000, A3x00, A3x00FC
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
Systems Affected
----------------
- ANYSYS - System Platform Independent -
X-Options Affected
------------------
- A3000 ALL StorEdge A3000 -
- A1000 All StorEdge A1000 -
- A3500 ALL StorEdge A3500 -
SG-XARY122A-16G - - 16GB STOREDGE A1000 -
SG-XARY122A-50G - - 50GB STOREDGE A1000 -
SG-XARY124A-109G - - 109GB STOREDGE A1000 -
SG-XARY124A-36G - - 36GB STOREDGE A1000 -
SG-XARY126A-144G - - 144GB STOREDGE A1000 -
SG-XARY126A-72G - - 72GB STOREDGE A1000 -
SG-XARY131A-16G - - 16GB STOREDGE A1000 FOR RACK -
SG-XARY133A-36G - - 36GB STOREDGE A1000 FOR RACK -
SG-XARY135A-72G - - 72GB STOREDGE A1000 FOR RACK -
SG-XARY351A-180G - - A3500 1 CONT MOD/5 TRAYS/18GB -
SG-XARY353A-1008G - - A3500 2 CONT/7 TRAYS/18GB -
SG-XARY353A-360G - - A3500 2 CONT/7 TRAYS/18GB -
SG-XARY355A-2160G - - A3500 3 CONT/15 TRAYS/18GB -
SG-XARY360A-545G - - 545-GB A3500 (1X5X9-GB) -
SG-XARY360A-90G - - A3500 1 CONT/5 TRAYS/9GB(10K) -
SG-XARY362A-180G - - A3500 2 CONT/7 TRAYS/9GB(10K) -
SG-XARY362A-763G - - A3500 2 CONT/7 TRAYS/9GB(10K) -
SG-XARY364A-1635G - - A3500 3 CONT/15 TRAYS/9GB(10K) -
SG-XARY366A-72G - - A3500 1 CONT/2 TRAYS/9GB(10K) -
SG-XARY380A-1092G - - 1092-GB A3500 (1x5x18-GB) -
SG-XARY360B-90G - - ASSY,TOP OPT,1X5X9,MIN,9GB,10K -
SG-XARY360B-545G - - ASSY,TOP OPT,1X5X9,MAX,9GB,10K -
SG-XARY362B-180G - - X-OPT,2X7X9,MIN,FCAL,9G10K -
SG-XARY374B-273G - - ASSY,TOP OPT,3X15X9,MIN,9GB,10K -
SG-XARY380B-182G - - X-OPT,FC-SN,1X5X18MIN,18GB10K -
SG-XARY380B-1092G - - ASSY,FC-SNL,1X5X18MAX,18G10K -
SG-XARY382B-364G - - ASSY,FC-SN,2X7X18,MIN,18GB,10K -
SG-XARY384B-546G - - ASSY,FC,3X15X18,MIN,18GB -
SG-XARY381B-364G - - ASSY,FC-SN,1X5X36MIN,36G10K -
SG-XARY381B-1456G - - ASSY,FC-SN,1X5X36MAX,36B10K -
SG-XARY383B-728G - - ASSY,FC-SN,2X7X36MIN,36B10K -
SG-XARY385B-1092G - - ASSY,FC-SN,3X15X36MIN,36B10K -
UG-A3500-FC-545G - - ASSY,TOP OPT,1X5X9,MAX,9GB,10K -
CU-A3500-FC-545G - - ASSY,TOP OPT,1X5X9,MAX,9GB,10K -
UG-A3500FC-182-10K - - FCTY,A3500FC/SCSI,1X5X18MIN,18/10K -
CU-A3500FC-182-10K - - FCTY,A3500FC/SCSI,1X5X18MIN,18/10K -
UG-A3500FC-364-10K - - FCTY,A3500FC/SCSI,2X7X18MIN,18/10K -
CU-A3500FC-364-10K - - FCTY,A3500FC/SCSI,2X7X18MIN,18/10K -
UG-A3500FC-546-10K - - FCTY,A3500FC/SCSI,3X15X18MIN 18G10K -
CU-A3500FC-546-10K - - FCTY,A3500FC/SCSI,3X15X18MIN 18G10K -
UG-A3K-A3500FC - - ASSY,UPGRADE,A3500FC/TABASCO -
UG-A3500-A3500FC - - ASSY,UPGRADE,A3500FC/DILBERT -
X6538A - - X-OPT,A3500FC CONTROLLER -
6538A - - FCTY, CONTROLLER, A3500FC -
PART NUMBERS AFFECTED:
Part Number Description Model
----------- ----------- -----
798-0522-01 RAID Manager 6.1.1 -
798-0522-02 RAID Manager6.1.1 Update 1 -
798-0522-03 RAID Manager6.1.1 Update 2 -
704-6708-10 CD, SUN STOREDGE RAID Manager6.22 -
REFERENCES:
BugId: 4334761 : Failed to create luns when new drives added.
PatchId: 
108553 : Solaris 8
108834 : Solaris 2.6 & 7
ESC: 525788
PROBLEM DESCRIPTION:
Any customer adding new drives to the A1000, A3x00, or A3x00FC may be
unable to create LUNs or replace failed drives within existing LUNs
using RM6.1.1 or RM6.22.
The following error will occur when LUN creation is attempted or when
replacing a drive within an existing LUN:
Failed:** Check Condition **
SENSE Data:
7000050000000098 0000000091030000
0000000000000000 0000000000000000
0000000000000000 0000000000000000
0000000000000000 0000000000000000
0000000000000000 0000000000000000
Sense Key: 05
ASC: 91
ASCQ: 03
This ASC/ASCQ combination can be further translated using the file
/usr/lib/osa/raidcode.txt:
ASC ASCQ Sense Key
91 03 5
Illegal Operation For Current Drive State - A drive operation was
requested through a Mode Select that cannot be executed due to the
state of the drive.
On each newly inserted drive, controller A would examine the drive and
check for a certain bit which indicates whether the dacstore is 2MB or
40MB. The bit pattern on some factory formatted drives will
mistakingly indicate to RM6 a 2MB dacstore where in actuality none
exists. When controller B receives a request from controller A to
refresh the dacstore in memory from the dacstore stored on the drive,
controller B tries to read the magic number which doesn't exist because
a dacstore was never created on the drive.
It has been determined that the root cause is a compatibility issue
between some factory formatted disk drives and the array firmware. The
fix can be applied to either the disk drives or the firmware. For the
sake of convenience LSI will implement the fix in a new firmware
revision which will be included in patches 108553 (Solaris 8), and
108834 (Solaris 2.6 & 7).
LSI has provided a controller firmware fix that is scheduled to be
released in the form of a patch in early December. They have provided a
work-around procedure in the mean-time.
Approximately 10,538 A3x00 and A3x00FC units in 1x5, 2x7, and 3x15
configurations have been shipped since January of 1998. And
approximately 31,600 A1000 units have been shipped since January of
1998. This is the total amount of units that are at risk of
encountering this problem.
IMPLEMENTATION:
---
| | MANDATORY (Fully Pro-Active)
---
---
| | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---
CORRECTIVE ACTION:
The patches are the permanent solution to this problem but the patches
are not scheduled to release until early December, 2000. Therefore, until
the patches are released, the following work-around procedure should be
implemented when adding new drives to the storage systems.
1. Obtain a current module profile first and save it so that if any
problems are encountered, the system can be brought up again.
In the RAID Manager GUI,
1) Choose Configuration
2) Select the RAID module
3) From the Top Menu, choose File->Save Module Profile
4) Make sure "All" is selected
5) Click "OK" and then provide a file to hold the profile
2. Insert a drive into a tray while the module is powered up.
3. Allow time for the drive to spin up (~30 seconds).
4. Run a health check to ensure that the drive is not defective.
In the RAID Manager GUI,
1) Choose Status
2) Select the RAID Module
3) Click Health Check
4) If the health results are not Optimal, click on Show Details
5. Fail the drive then revive the drive to update the dacstore.
In the RAID Manager GUI,
1) Choose Recovery
2) Select the RAID Module
3) Click Options->Manual Recovery->Drives
4) Highlight the drive you just installed
5) Click Fail, then OK
6) Click Options->Manual Recovery->Drives
7) Highlight the drive just installed
8) Click Revive, then OK
6. Perform step 2, 3, 4, and 5 until all drives have been added.
COMMENTS:
----------------------------------------------------------------------------
Implementation Footnote:
i) In case of MANDATORY FINs, Enterprise Services will attempt to
contact all affected customers to recommend implementation of
the FIN.
ii) For CONTROLLED PROACTIVE FINs, Enterprise Services mission critical
support teams will recommend implementation of the FIN (to their
respective accounts), at the convenience of the customer.
iii) For REACTIVE FINs, Enterprise Services will implement the FIN as the
need arises.
----------------------------------------------------------------------------
All released FINs and FCOs can be accessed using your favorite network
browser as follows:
SunWeb Access:
--------------
* Access the top level URL of http://sdpsweb.ebay/FIN_FCO/
* From there, select the appropriate link to query or browse the FIN and
FCO Homepage collections.
SunSolve Online Access:
-----------------------
* Access the SunSolve Online URL at http://sunsolve.Corp/
* From there, select the appropriate link to browse the FIN or FCO index.
Supporting Documents:
---------------------
* Supporting documents for FIN/FCOs can be found on Edist. Edist can be
accessed internally at the following URL: http://edist.corp/.
* From there, follow the hyperlink path of "Enterprise Services Documenta-
tion" and click on "FIN & FCO attachments", then choose the
appropriate
folder, FIN or FCO. This will display supporting directories/files for
FINs or FCOs.
Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to finfco-manager@Sun.COM
---------------------------------------------------------------------------
Copyright (c) 1997-2003 Sun Microsystems, Inc.