Document fins/I0685-1
FIN #: I0685-1
SYNOPSIS: Certain precautions need to be observed when upgrading the Solaris OS
on systems with RM6 software installed
DATE: Jun/21/01
KEYWORDS: Certain precautions need to be observed when upgrading the Solaris OS
on systems with RM6 software installed
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
SYNOPSIS: Certain precautions need to be observed when upgrading the
Solaris OS on systems with RM6 software installed.
SunAlert: No
TOP FIN/FCO REPORT: No
PRODUCT_REFERENCE: Raid Manager 6 Software
PRODUCT CATEGORY: Storage / Service
PRODUCTS AFFECTED:
Systems Affected
----------------
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
- ANYSYS - System Platform Independent -
X-Options Affected
------------------
Mkt_ID Platform Model Description Serial
Number
------ -------- ----- -----------
-------------
- A1000 ALL A1000 Storage Array -
- A3000 ALL A3000 Storage Array -
- A3500 ALL A3500 Storage Array -
- A3500FC ALL A3500FC Storage Array -
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 9GB10K -
SG-XARY360B-545G - - ASSY TOP OPT 1X5X9 MAX 9GB10K -
SG-XARY362B-180G - - X-OPT 2X7X9 MIN FCAL 9G10K -
SG-XARY374B-273G - - ASSY TOP OPT 3X15X9 MIN 9GB10K -
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 18GB10K -
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 -
X2611A - - OPT INT I/O BD FOR EXX00 -
X2612A - - OPT INT I/O BD EXX00 W/FC-AL -
X2622A - - OPT INT GRAPHICS I/O BD EXX00 -
PART NUMBERS AFFECTED:
Part Number Description Model
----------- ----------- -----
825-3869-02 MNL Set SUN RSM ARRAY 2000 -
798-0188-01 SS CD ASSY RAID Manager 6.1 -
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 -
704-7937-05 CD, SUN STOREDGE RAID Manager6.22.1 -
REFERENCES:
BugId: 4408321 - s8U4_b4/later and S9 failed to show RM6 LUNs under
format using jumpstart.
4479887 - RDAC open log messages when RDBMS (Oracle, Sybase)
accesses raw lun partitions.
FIN: I0589-01
I0619-01
MANUAL: 805-7758-12 - Sun StorEdge RAID Manager 6.22.1 Release Notes.
806-6419-12 - Sun StorEdge A3x00/A3500FC Best Practices Guide.
806-7792-14 - Sun StorEdge RAID Manager 6.22 and 6.22.1 Upgrade
Guide.
PROBLEM DESCRIPTION:
This FIN highlights the precautions that should be followed if
performing Solaris Operating Environment upgrades on the system with
Sun StorEdge RAID Manager software installed. Absence of these
precautions could result in data loss or possibly data corruption.
The A1000, A3000, A3500 and A3500FC arrays are supported on Solaris 9,
but the RM6 patch is not yet available. Upgrading to Solaris 9 if you
have any of these arrays attached and you do not have the latest 112126
patch applied, exposes problems like those described in bug 4479887,
non-root access to raw partitions.
When upgrading from Solaris 2.6 to any higher Solaris version, a copy
of the file /kernel/drv/sd.conf needs to be backed up and then restored
after the upgrade. If this action is not taken then an upgrade will
result in repeated error messages upon boot up and an inability to scan
the array module. The first reboot following an upgrade from Solaris
2.6 to a higher level OS will look like this:
Hostname: tazbert
Configuring /dev and /devices
Configuring the /dev directory (compatibility devices)
Re-generating rdriver.conf file ...
ps: psread() error on read, rbs=5092, bs=6096, Error 0
Configuring the RAID devices
The system is coming up. Please wait.
Configuring network interface addresses: hme0 hme1SUNW,hme1:
Link Down - cable problem?
SUNW,hme1: Link Down - cable problem?
SUNW,hme1: Link Down - cable problem?
.
NIS domainname is etc.eng.sun.com
starting rpc services: rpcbind keyserv ypbind done.
Setting netmask of hme0 to 255.255.255.0
Setting default interface for multicast: add net 224.0.0.0:
gateway tazbert
syslog service starting.
Print services started.
May 3 14:05:17 tazbert /usr/lib/osa/bin/nvutil:
An internal processing error occurred on controller 1T93401256.
May 3 14:05:17 tazbert /usr/lib/osa/bin/nvutil:
An internal processing error occurred on controller 1T93401256.
The NVSRAM settings of controller c1t5d0(1T93600684) are correct.
May 3 14:05:17 tazbert
May 3 14:05:17 tazbert
nvutil command failed.
Array Monitor initiated
RDAC daemons initiated
May 3 14:05:17 tazbert unix: ID[RAIDarray.rdaemon.1001] RDAC
Resolution Daemon locked in memory volume management
starting.
The system is ready.
tazbert console login:
In addition to the error message "ps: psread() error on read, rbs=5092,
bs=6096, Error 0" the nvutil command will report "An internal
processing error occurred on controller..." and fail to complete.
The last upgrade issue mentioned is caused by the Solaris upgrade
copying a new version of the file /kernel/drv/sd.conf over the original
sd.conf file. The installation of RM6 results in the sd.conf file
getting updated with entries for every possible RM6 LUN the system can
support. The default is 8. When 16 or 32 LUN support is enabled the
file is updated again with entries for all 16 or 32 LUNs.
When the solaris upgrade overwrites the sd.conf file then these entries
are not preserved and this is the reason for the repeated error
messages upon boot up and the system's inability to scan the array
modules. Until the original sd.conf file is restored and the host
system is rebooted the system will remain in this failed state.
Since the RM6 patch is not yet available for Solaris 9, the bugs fixed
by that patch will appear on systems where RM 6.22.1 is installed on
Solaris 9. Note that a system running Solaris 8 with a fully patched RM
6.22.1, can be upgraded to Solaris 9 with no RM 6.22.1 patch issues.
Of the bugs fixed in the RM 6.22.1 patch, that would not be fixed on a
new Solaris 9 installation until patch 112126 is ready to install on
Solaris 9, bug 4479887 impacts LUNs on these arrays which are used as
raw partitions.
IMPLEMENTATION:
---
| | MANDATORY (Fully Pro-Active)
---
---
| | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---
CORRECTIVE ACTION:
An Authorized Enterprise Field Service Representative may avoid the
above mentioned problems by following the recommendations as shown
below.
The following precautions need to be observed when upgrading the
Solaris Operating Environment on systems with RM6 software installed.
* The only supported version of RM6 is RM6.22.1. Any customer who
wishes to upgrade to Solaris 8 or 9 must first upgrade to RM6.22.1.
* If the glm driver is used and a customer wishes to upgrade from
Solaris 2.6 or Solaris 7 to any higher OS level then they need to
be aware of necessary changes to the file /kernel/drv/glm.conf.
Refer to FIN I0589-1 to determine differences in the glm.conf file
between Solaris 2.6 and 7 and higher OS levels.
* If a customer is upgrading to Solaris 8 Update 4 or higher then
they need to be aware of bug 4408321. This bug prevents the user
from being able to jumpstart their RM6.22 installation.
* Users must ensure that their device tree is stable, ie lad and
format output are synchronized, their array is in an optimal state
and no hardware changes are being done. Any device tree
inconsistencies or array component failures need to be fixed prior
to the OS upgrade.
* If a Sun StorEdge A1000, A3000, or A3500 is used as the boot device
then the customer will *not* be able to upgrade their OS. A complete
backup of customer data is necessary so that the OS and RM6 software
can be re-installed from scratch. For more information on booting
from any of these hardware RAID arrays refer to FIN I0619-1.
* Prior to upgrades from Solaris 2.6 to any higher OS level, a copy of
the file /kernel/drv/sd.conf needs to be backed up and then restored
after the upgrade. If this action is not taken then an upgrade will
result in repeated error messages upon boot up and an inability to
scan the array module.
* When upgrading to Solaris 9, one should install the RM 6 patch 112126
on the Solaris 8 host first, then upgrade to Solaris 9. This only
applies until 
112126 is released. The target release date is
August 20, 2002. If the host is running a pre-Solaris 8 OS, then
upgrade to Solaris 8 first, install the latest 112126 patch, then
upgrade to Solaris 9.
Each of these upgrade issues have been addressed in the various RM6
documents. The RM6.22.1 Release Notes instruct users to back up and
restore their sd.conf file. The Sun StorEdge A3x00/A3500FC Best
Practices Guide points to information regarding device tree
stabilization, FRU component troubleshooting and replacement as well as
relevant FINs.
COMMENTS:
None
------------------------------------------------------------------------------
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.
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.