WARNING:Articles moved into the Archived collection were accurate at the "Last Update" date, but are not maintained from that date forward.
As such, Sun disclaims all implied or express warranties with respect to the information contained in such articles.
Document Audience:INTERNAL Archive
Document ID:I0509-1
Title:Raid Manager large rdriver.conf files need a patch to prevent panic.
Copyright Notice:Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved
Last Updated Date:2004-01-07

---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------  
                        FIELD INFORMATION NOTICE
                  (For Authorized Distribution by SunService)
FIN #: I0509-1
Synopsis: Raid Manager large rdriver.conf files need a patch to prevent panic.
Create Date: Jun/29/99
Keywords: 

Raid Manager large rdriver.conf files need a patch to prevent panic.

Top FIN/FCO Report: Yes
Products Reference: RM 6 and Solaris kernel corruption
Product Category: Storage / Software / Solaris / SWAdmin
Product Affected: 
Mkt_ID   Platform   Model   Description              Serial Number
------   --------   -----   -----------              -------------
Systems Affected
----------------
  -       A14        ALL    Ultra 2                         -
  -       SS1000(E)  ALL    SPARCserver 1000(E)             -
  -       SC2000(E)  ALL    SPARCcenter 2000(E)             -
  -       E3000      ALL    Ultra Enterprise 3000           -
  -       E3500      ALL    Ultra Enterprise 3500           -
  -       E4000      ALL    Ultra Enterprise 4000           -
  -       E4500      ALL    Ultra Enterprise 4500           -
  -       E5000      ALL    Ultra Enterprise 5000           -
  -       E5500      ALL    Ultra Enterprise 5500           -
  -       E6000      ALL    Ultra Enterprise 6000           -
  -       E6500      ALL    Ultra Enterprise 6500           -
  -       E10000     ALL    Ultra Enterprise 10000          -

X-Options Affected
------------------

SG-ARY131A-16GR5   -  -   16GB STOREDGE A1000 RACK      -       
SG-ARY133A-36GR5   -  -   36GB STOREDGE A1000 RACK      -      
SG-ARY135A-72GR5   -  -   72GB STOREDGE A1000 RACK      -  
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-XARY144A-109G   -  -   109GB STOREDGE A1000(10K RPM) -
SG-XARY144A-36G    -  -   36GB STOREDGE A1000(10K RPM)  -
SG-XARY146A-36G    -  -   36GB A1000 FOR RACK(10K RPM)  -
Parts Affected: 
Part Number   Description                            Model
-----------   -----------                            -----
825-3869-02   RM 6.0 Manual Set, SUN RSM ARRAY 2000    -
798-0188-01   RAID Manager6.1                          -
798-0522-01   RAID Manager6.1.1                        -
798-0522-02   RAID Manager6.1.1 Update 1               - 
798-0522-03   RAID Manager6.1.1 Update 2               -
References: 
BugId:   4230669, 4176940
PatchId: 105181-13,  106541-03
MANUAL:  805-3656-11 Sun StorEdge RAID Manager 6.1.1 Release Notes
Issue Description: 
In order for RM 6 software to configure multiple LUNs, it adds entries
to the sd.conf and rdriver.conf files.  The add16lun.sh script is a
case in point as it enlarges the sd.conf for 16 LUNs for all targets.
However, there is bug in the Solaris kernel that sometimes causes a
panic if a *.conf file is greater than 8k bytes.  

*For sample error messages reference BugId#s 4230669 and 4176940
from SunSolve Online.

The above mentioned problem often occurs during boot -r, (the first boot
-r) after adding hardware, however, it's occurrence has been know to vary, 
thus, the bug is often mistaken for a hardware problem.  Also, because of 
when it occurs, a corefile can be difficult to obtain.

This problem has the potential to cause invisible kernel corruption
during driver loading after the boot -r and it's timing mimics a
hardware problem so seamlessly that even a very experienced support
representative would never suspect that it was a software bug in a timely
manner.
Implementation: 
---
        |   |   MANDATORY (Fully proactive)
         ---    
         
  
         ---
        | X |   CONTROLLED PROACTIVE (per Sun Geo Plan) 
         --- 
         
                                
         ---
        |   |   REACTIVE (As Required)
         ---
Corrective Action: 
Enterprise Customers and Authorized Service Representatives may avoid 
the above mentioned Raid Manager software problem by following the patch 
installation recommendation as shown below:

Apply the patch as listed for your Solaris version and reboot.
Note a reconfiguration boot is not needed or recommended.


FOR SOLARIS 2.6 INSTALL:
------------------------
Patch-ID# 105181-14
Keywords: security kernel ST_FIX_ALIGN FFB2 ECC VOP_REALVP sockfs klmmod
          sigintr
Synopsis: SunOS 5.6: kernel update patch
Date: May/18/99

Solaris Release: 2.6

SunOS Release: 5.6

Unbundled Product: 

Unbundled Release: 

Xref: This patch available for x86 as patch 105182

Topic: SunOS 5.6: kernel update patch

        NOTE:   Refer to Special Install Instructions section for 
                IMPORTANT specific information on this patch.



FOR SOLARIS 2.7 INSTALL:
------------------------
Patch-ID# 106541-05
Keywords: security fcntl EINVAL cpr genunix PPS kernel F_SHARE ufsvfs DR procfs
Synopsis: SunOS 5.7: Kernel update patch
Date: Jun/11/99

Solaris Release: 7

SunOS Release: 5.7

Unbundled Product: 

Unbundled Release: 

Xref: This patch available for x86 as patch 106542

Topic: SunOS 5.7: kernel update patch

        NOTE:  Refer to Special Install Instructions section for 
               IMPORTANT specific information on this patch.
Comments: 
NOTE: A reconfiguration boot (boot -r) is not needed or recommended.
      after the installation of the above mentioned patches.

NOTE: This FIN will also apply to future Raid Manager releases.
               

--------------------------------------------------------------------------
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 [email protected]
---------------------------------------------------------------------------
Statusinactive