Sun Oracle Sun Blade 6000 Service manual

Sun Blade 6000 Disk Module
Product Notes
Part No. 820-1709-14
May 2010, Revision A

Please
Recycle
Copyright © 2009, 2010, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by
intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate,
broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us
in writing.
If this is software or related software documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the
following notice is applicable:
U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers
are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific
supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set
forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR
52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any
inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use. Oracle
Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Intel and Intel Xeon are
trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of
SPARC International, Inc. UNIX is a registered trademark licensed through X/Open Company, Ltd.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle
Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and
services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services.
Copyright © 2009, 2010, Oracle et/ou ses affiliés. Tous droits réservés.
Ce logiciel et la documentation qui l’accompagne sont protégés par les lois sur la propriété intellectuelle. Ils sont concédés sous licence et soumis à des
restrictions d’utilisation et de divulgation. Sauf disposition de votre contrat de licence ou de la loi, vous ne pouvez pas copier, reproduire, traduire,
diffuser, modifier, breveter, transmettre, distribuer, exposer, exécuter, publier ou afficher le logiciel, même partiellement, sous quelque forme et par
quelque procédé que ce soit. Par ailleurs, il est interdit de procéder à toute ingénierie inverse du logiciel, de le désassembler ou de le décompiler, excepté à
des fins d’interopérabilité avec des logiciels tiers ou tel que prescrit par la loi.
Les informations fournies dans ce document sont susceptibles de modification sans préavis. Par ailleurs, Oracle Corporation ne garantit pas qu’elles
soient exemptes d’erreurs et vous invite, le cas échéant, à lui en faire part par écrit.
Si ce logiciel, ou la documentation qui l’accompagne, est concédé sous licence au Gouvernement des Etats-Unis, ou à toute entité qui délivre la licencede
ce logiciel ou l’utilise pour le compte du Gouvernement des Etats-Unis, la notice suivante s’applique :
U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers
are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific
supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set
forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR
52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
Ce logiciel ou matériel a été développé pour un usage général dans le cadre d’applications de gestion des informations. Ce logiciel ou matériel n’est pas
conçu ni n’est destiné à être utilisé dans des applications à risque, notamment dans des applications pouvant causer des dommages corporels. Si vous
utilisez ce logiciel ou matériel dans le cadre d’applications dangereuses, il est de votre responsabilité de prendre toutes les mesures de secours, de
sauvegarde, de redondance et autres mesures nécessaires à son utilisation dans des conditions optimales de sécurité. Oracle Corporation et ses affiliés
déclinent toute responsabilité quant aux dommages causés par l’utilisation de ce logiciel ou matériel pour ce type d’applications.
Oracle et Java sont des marques déposées d’Oracle Corporation et/ou de ses affiliés.Tout autre nom mentionné peut correspondre à des marques
appartenant à d’autres propriétaires qu’Oracle.
AMD, Opteron, le logo AMD et le logo AMD Opteron sont des marques ou des marques déposées d’Advanced Micro Devices. Intel et Intel Xeon sont des
marques ou des marques déposées d’Intel Corporation. Toutes les marques SPARC sont utilisées sous licence et sont des marques ou des marques
déposées de SPARC International, Inc. UNIX est une marque déposée concédée sous licence par X/Open Company, Ltd.

iii
Contents
Preface vii
1. Sun Blade 6000 Disk Module Product Notes 1
Firmware Revision History 2
Obtaining the Latest Firmware Updates 2
2. Hardware Issues 5
Disk Drive’s Green LED Does not Stop Blinking After Resync Completes
(6717566) 6
Amber Locate LED Does not Show X6220 Server Blade HDDs (6711327) 6
Repeated Warning Messages When Inserting or Powering on a Disk Blade, SAS-
NEM, or Disk (6694909) 7
Yellow Service LED for one Disk Comes on After RAID 1E Volume is Created
(6706908) 8
Multiple HDD Resynch LEDs May Blink Simultaneously (6663520) 8
Expander Status Change Event Sent When Disk Blade is Hot-Plugged (6625472)
9
During Array Initialization with Build and Verify, HDDs Did Not Show the Green
LED (6805033) 9
On the SP Console, Scrolling Characters Cause Difficulty in Cursor Navigation
(6812100) 10
Power State of Blades From CMM Show Incorrect Environment (OFF) (6823893)
11

iv Sun Blade 6000 Disk Module Product Notes • May 2010
When Multiple Reset Commands are Performed the Sun Blade 6000 Will Fail to
Power On (6824045) 11
Controller Kernel Stops Running After Reset (6793466) 11
▼To reset the controller: 14
▼To reboot the system after reset: 14
Server with a SAS-2 REM Might Hang When Inserted into a Chassis with SAS-1
Devices 14
3. Software Issues 17
VMWare 17
Oracle Solaris Issues 17
Linux Issues 18
Windows Issues 18
VMWare ESX does not recognize SCSI IDs (6790706) 18
Solaris OS Will not Install on 1 TByte RAID 19
Delete All Partitions Error With SUSE Linux Installer (6729550) 19
raidctl Operations Can Take More Than One Minute (6723851) 20
format Command Shows “Drive Not Available”(6725695) 20
Solaris Patch Required for Miniroot of Network Installers (6634536) 21
Solaris 0 5/08 Cannot be Installed From DVD on Server Blades in Filled Chassis
(6735573) 22
mpxio-Capable SAS Disks Cannot be Managed by Solaris raidctl (6523832) 22
raidctl -l Truncates Solaris Volume Names (6729161) 23
Cannot Reactivate RAID Volumes on Servers Running the Solaris OS Using
raidctl (6695619) 23
raidctl Cannot set Hot-Spare (6692827) 24
raidctl -d Operation Can Delete a Mounted RAID Volume (6750744) 24
mpt Driver Warning Messages During Solaris System Boot up (6634061) 25
Sun Blade T6300 and T63200 Server Modules Might Hang at Boot (6662335) 26
scsi_vhci.conf Setting for MPxIO Needs to be Reset (6742736) 26

Contents v
Solaris mpxio-upgrade Incompatible with ZFS (6707555) 27
Failure to Complete Partition Request With SAS Disks and Windows Server
2003 27
Removing One NEM Causes Windows Server 2003 to Reboot (6715806) 28
Cannot Create Partition on Both Instances of a Dual-Pathed Disk With Windows
Server 2003 (6715806) 28

vi Sun Blade 6000 Disk Module Product Notes • May 2010

vii
Preface
This document intended to bring you late breaking information about the system, as
well as workarounds for problems you might encounter when installing, configuring,
or operating Oracle’s Sun Blade 6000 Disk Module. This information is designed for
system administrators who are experienced with the installation and configuration of
the basic system components and its software.
Issues include information that you should know about, such as prerequisites, tips,
troubleshooting hints, and change requests. Change requests have tracking numbers
shown in parentheses.
Related Documentation
For a description of the document set for the Sun Blade 6000 Disk Module, see the
Where To Find Sun Blade 6000 Disk Module Documentation sheet that is packed with
your system and also posted at the product's documentation site at this URL:
http://docs.sun.com/app/docs/coll/blade6000dskmod
Translated versions of some of these documents are available at the web site
described above in French, Simplified Chinese, Traditional Chinese, Korean, and
Japanese. English documentation is revised more frequently and might be more up-
to-date than the translated documentation.

viii Sun Blade 6000 Disk Module Product Notes • May 2010
Typographic Conventions
Documentation Comments
Your comments on improving our documentation are welcome. Send feedback to:
http://www.sun.com/hwdocs/feedback
Please include the title and part number of your document with your feedback:
Sun Blade 6000 Disk Module Product Notes, part number 820-1709-14.
Typeface Meaning Examples
AaBbCc123 The names of commands, files,
and directories; onscreen
computer output
Edit your.login file.
Use ls -a to list all files.
% You have mail.
AaBbCc123 What you type, when contrasted
with onscreen computer output
%su
Password:
AaBbCc123 Book titles, new words or terms,
words to be emphasized.
Replace command-line variables
with real names or values.
Read Chapter 6 in the User’s Guide.
These are called class options.
You must be superuser to do this.
To delete a file, type rm filename.

1
CHAPTER 1
Sun Blade 6000 Disk Module
Product Notes
This document contains late-breaking information and issues for the Sun Blade 6000
Disk Module. Sections included in this document:
■“Firmware Revision History” on page 2
■“Obtaining the Latest Firmware Updates” on page 2
■“Hardware Issues” on page 5
■“Software Issues” on page 17

2Sun Blade 6000 Disk Module Product Notes • May 2010
Firmware Revision History
The firmware release history for the Sun Blade 6000 Disk Module and supported
SAS NEMs is listed in the following table.
Note – Both the disk module and the SAS NEM firmware need to be at the same
revision level.
Obtaining the Latest Firmware Updates
The latest firmware for the Sun Blade 6000 Disk Module is available as follows:
TABLE 1-1 Sun Blade 6000 Disk Module and SAS NEM Firmware
Firmware
Revision
Base Firmware
Delivery Platform
Supported Hardware Description
5.02.10
(502A)
Sun Common
Array Manager
6.1.2
• Sun Blade 6000 Disk Module
• Sun Blade 6000 Multi-Fabric Network
Express Module
• Sun Blade 6000 10GbE Multi-Fabric
Network Express Module
• Sun Blade 6000 Virtualized Multi-Fabric
10GbE Network Express Module
Initial release.
5.02.14
(502E)
Sun Common
Array Manager
6.4.1
• Sun Blade 6000 Disk Module
• Sun Blade 6000 Multi-Fabric Network
Express Module
• Sun Blade 6000 10GbE Multi-Fabric
Network Express Module
• Sun Blade 6000 Virtualized Multi-Fabric
10GbE Network Express Module
Support was
added for second
source to
monitor disk
module
temperature and
voltage.
5.04.03 Oracle
Hardware
Management
Pack 2.0
(fwupdate
utility)
• Sun Blade 6000 Disk Module
• Sun Blade 6000 Multi-Fabric Network
Express Module
• Sun Blade 6000 10GbE Multi-Fabric
Network Express Module
• Sun Blade 6000 Virtualized Multi-Fabric
10GbE Network Express Module
Support added
for SAS-1/SAS-2
device
coexistence in a
Sun Blade 6000
Modular System
chassis.

Chapter 1 Sun Blade 6000 Disk Module Product Notes 3
■Using the Sun Common Array Manager (CAM), available on the Sun download
web site, at:
http://www.sun.com/storagetek/management_software/resource_man
agement/cam/get_it.html
■Using the fwupdate utility of Oracle Management Pack 2.0, you will need to
download:
■Oracle Hardware Management Pack 2.0 available on the Oracle download site:
http://www.sun.com/systemmanagement/managementtools.jsp
■The latest Sun Blade 6000 Disk Module software release available on the Oracle
download site:
http://www.sun.com/servers/blades/downloads.jsp

4Sun Blade 6000 Disk Module Product Notes • May 2010

5
CHAPTER 2
Hardware Issues
This chapter describes hardware issues related to the Sun Blade6000 disk module.
The following issues are described:
■“Disk Drive’s Green LED Does not Stop Blinking After Resync Completes
(6717566)” on page 6
■“Amber Locate LED Does not Show X6220 Server Blade HDDs (6711327)” on
page 6
■“Repeated Warning Messages When Inserting or Powering on a Disk Blade, SAS-
NEM, or Disk (6694909)” on page 7
■“Yellow Service LED for one Disk Comes on After RAID 1E Volume is Created
(6706908)” on page 8
■“Multiple HDD Resynch LEDs May Blink Simultaneously (6663520)” on page 8
■“Expander Status Change Event Sent When Disk Blade is Hot-Plugged (6625472)”
on page 9
■“During Array Initialization with Build and Verify, HDDs Did Not Show the
Green LED (6805033)” on page 9
■“On the SP Console, Scrolling Characters Cause Difficulty in Cursor Navigation
(6812100)” on page 10
■“Power State of Blades From CMM Show Incorrect Environment (OFF) (6823893)”
on page 11
■“When Multiple Reset Commands are Performed the Sun Blade 6000 Will Fail to
Power On (6824045)” on page 11
■“Controller Kernel Stops Running After Reset (6793466)” on page 11
■“Server with a SAS-2 REM Might Hang When Inserted into a Chassis with SAS-1
Devices” on page 14

6Sun Blade 6000 Disk Module Product Notes • May 2010
Disk Drive’s Green LED Does not Stop
Blinking After Resync Completes
(6717566)
When a RAID resync is in progress, the disk drive’s green LED blinks in a regular
pattern. It should stop blinking and stay lit after the resync completes. However,
when a faulty disk in a RAID 1 mirror is replaced (in the same slot) the LED
continues to blink in some cases, indicating the resynch is still in progress.
Workaround
The resync status of a RAID volume can be observed using the MegaRAID Storage
Manager (MSM) software in Windows and Linux, raidctl in Solaris, or the LSI
BIOS Configuration Utility. These are all documented in the Sun LSI 106x RAID
User’s Guide (820-4933).
The green LED can be reset to the normal condition (solid green) by power cycling
the Sun Blade 6000 Modular System Chassis and then removing and re-inserting the
Sun Blade 6000 Disk Module.
Amber Locate LED Does not Show X6220
Server Blade HDDs (6711327)
In the SAS Topology screen of the LSI BIOS Configuration Utility, there is a
mechanism to turn on the disk amber LED of the disks in a RAID volume to locate
them. This locate feature is not functional for directly attached disks in host server
blade disk bays.
Workaround
In the SAS Topology screen, you can select Direct Attach Devices to view direct
attached disks on host server blades.

Chapter 2 Hardware Issues 7
The bay number next to the disk shown as a member of the RAID volume
corresponds to the silk-screen number on the host server blade’s bays. In the case
above, the disk that is a member of the RAID volume is in the disk bay with silk-
screen label 1.
Repeated Warning Messages When
Inserting or Powering on a Disk Blade,
SAS-NEM, or Disk (6694909)
The following pair of warning messages may appear repeatedly upon insertion of
HDDs and upon powering on Sun Blade 6000 Disk Module or Sun Blade 6000 Multi-
Fabric Network Expansion Module:
scsi: WARNING: /pci@7c0/pci@0/pci@2/LSILogic,sas@0 (mpt0):
mpt_handle_event_sync: IOCStatus=0x7, IOCLogInfo=0x0
Workaround
These warning messages are benign and can be ignored.

8Sun Blade 6000 Disk Module Product Notes • May 2010
Yellow Service LED for one Disk Comes
on After RAID 1E Volume is Created
(6706908)
After creating a RAID 1E volume, one or more of the member disk drive’s amber
service LEDs may turn on, even though there is no HDD fault.
Workaround
If you create a RAID 1E volume, ignore the amber service LEDs on the disk drives.
Instead, view the disk drive’s status using the MegaRAID Storage Manager (MSM)
software in Windows and Linux, raidctl in Solaris, or the LSI BIOS Configuration
Utility. These are all documented in Sun LSI 106x RAID User’s Guide (820-4933).
Multiple HDD Resynch LEDs May Blink
Simultaneously (6663520)
Only one RAID volume at a time can resynch. When volume B needs to resynch, but
volume A is resynching, volume B must wait to resynch until the volume A resynch
is completed.
If a disk in an LSI RAID volume B fails while another RAID volume (volume A) is
resynching, the resynch light on the hot-spare for volume B starts blinking even
though volume B has not begun to resynch.
Workaround
This is expected behavior. One volume is resynching and the other is in queue to
resynch. You can view the status of each RAID (A is resynching and B is degraded)
using the MegaRAID Storage Manager (MSM) software in Windows and Linux,
raidctl in Solaris, or the LSI BIOS Configuration Utility. These are all documented
in Sun LSI 106x RAID User’s Guide (820-4933).

Chapter 2 Hardware Issues 9
Expander Status Change Event Sent
When Disk Blade is Hot-Plugged
(6625472)
When you change your storage hardware configuration, you may see the following
Solaris message:
mpt0: unknown event 1b received
The message is harmless and may be safely ignored.
Workaround
Ignore the message. Check for the availability of a patch for this defect.
During Array Initialization with Build
and Verify, HDDs Did Not Show the
Green LED (6805033)
When a Sun Blade 6000 Disk Module is connected to a Sun Blade RAID 5 Expansion
Module (X4620A) and you build a RAID volume that includes disks in slot 4 and/or
slot 6, the LEDs on these disk will not blink during RAID initialization, rebuilding or
verification.
Workaround
Use the Sun RAID Manager interface to confirm that disks four and/or six are part
of the RAID volume. Alternatively, use the Sun Blade G2 RAID 0/1 Expansion
Module (X4607A).

10 Sun Blade 6000 Disk Module Product Notes • May 2010
On the SP Console, Scrolling Characters
Cause Difficulty in Cursor Navigation
(6812100)
When a Sun Blade 6000 Disk Module is connected to a Sun Blade RAID 5 Expansion
Module (X4620A) and you attempt to connect to the BIOS through the SP the screen
will be obscured by scrolling "5;00H" characters.
[I5;00H
FIGURE 2-1 Scrolling Characters in Adaptec BIOS Main Menu
Workaround
1. Don’t use the SP. Connect to the host blade directly.
2. Use the Sun Blade G2 RAID 0/1 Expansion Module (X4607A).

Chapter 2 Hardware Issues 11
Power State of Blades From CMM Show
Incorrect Environment (OFF) (6823893)
When power is removed from the Sun Blade 6000 Disk Module, whether by power
cycling the blade itself or the entire chassis, the power state shown by the CMM
command show /CH/ will show the blade as powered off when it is actually
powered on
Workaround
Run the start /CH/ command from the CMM.
When Multiple Reset Commands are
Performed the Sun Blade 6000 Will Fail
to Power On (6824045)
When resetting the Sun Blade 6000 Disk Module though the CMM, the power state
shown by the CMM command show /CH/ will show the blade as powered off when
it is actually powered on.
Workaround
Use the start /CH/ and stop /CH/ command from the CMM instead of the reset
command.
Controller Kernel Stops Running After
Reset (6793466)
The HBA hangs during system reboot or boot up.

12 Sun Blade 6000 Disk Module Product Notes • May 2010
FIGURE 2-2 Reboot Hang
FIGURE 2-3 Controller Error
The HBA crashes in the Adaptec BIOS RAID manager.