Related Manuals for Sun Oracle Sun Blade 6000
Summary of Contents for Sun Oracle Sun Blade 6000
- Page 1 Sun Blade 6000 Disk Module Product Notes Part No. 820-1709-14 May 2010, Revision A...
- Page 2 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.
-
Page 3: Table Of Contents
Contents Preface vii Sun Blade 6000 Disk Module Product Notes 1 Firmware Revision History 2 Obtaining the Latest Firmware Updates 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... - Page 4 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...
- Page 5 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 Contents...
- Page 6 Sun Blade 6000 Disk Module Product Notes • May 2010...
-
Page 7: Preface
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... - Page 8 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. viii Sun Blade 6000 Disk Module Product Notes • May 2010...
-
Page 9: Sun Blade 6000 Disk Module Product Notes
C H A P T E R 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 ■... -
Page 10: Firmware Revision History
• Sun Blade 6000 Virtualized Multi-Fabric chassis. 10GbE Network Express Module Obtaining the Latest Firmware Updates The latest firmware for the Sun Blade 6000 Disk Module is available as follows: Sun Blade 6000 Disk Module Product Notes • May 2010... - Page 11 ■ 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 Chapter 1 Sun Blade 6000 Disk Module Product Notes...
- Page 12 Sun Blade 6000 Disk Module Product Notes • May 2010...
-
Page 13: Hardware Issues
“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 ■... -
Page 14: Disk Drive's Green Led Does Not Stop Blinking After Resync Completes (6717566)
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... -
Page 15: Nem, Or Disk (6694909)
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):... -
Page 16: Yellow Service Led For One Disk Comes On After Raid 1E Volume Is Created (6706908)
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). Sun Blade 6000 Disk Module Product Notes • May 2010... -
Page 17: Expander Status Change Event Sent When Disk Blade Is Hot-Plugged (6625472)
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. -
Page 18: On The Sp Console, Scrolling Characters Cause Difficulty In Cursor Navigation (6812100)
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. -
Page 19: Power State Of Blades From Cmm Show Incorrect Environment (Off) (6823893)
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... - Page 20 Reboot Hang FIGURE 2-2 Controller Error FIGURE 2-3 The HBA crashes in the Adaptec BIOS RAID manager. Sun Blade 6000 Disk Module Product Notes • May 2010...
- Page 21 Chapter 2 Hardware Issues...
-
Page 22: To Reset The Controller
When Inserted into a Chassis with SAS-1 Devices If a server module with a SAS-2 REM is inserted into a Sun Blade 6000 Modular System chassis that has SAS-1 NEMs, or SAS-1 NEMs and Sun Blade 6000 Disk Module, the server’s SAS-2 REM might hang. To prevent this, you need to upgrade the firmware of your SAS-1 NEMs and Sun Blade 6000 Disk Modules to a firmware version that supports SAS-1/SAS-2 coexistence. - Page 23 Refer to your product documentation to find out if your server blade includes a SAS- 2 REM. For detailed instructions on performing the upgrade, refer to the SAS-1/SAS-2 Compatibility Upgrade Guide for the Sun Blade 6000 Modular System (821-1800) which can be found in: http://docs.sun.com/coll/blade6000dskmod...
- Page 24 Sun Blade 6000 Disk Module Product Notes • May 2010...
-
Page 25: Software Issues
C H A P T E R Software Issues This chapter describes software issues related to the Sun Blade 6000 disks module. The following issues are described: VMWare “VMWare ESX does not recognize SCSI IDs (6790706)” on page 18 Oracle Solaris Issues “Solaris OS Will not Install on 1 TByte RAID”... -
Page 26: Linux Issues
You may occasionally see the error, but there will be no interruption in service. This problem will be fixed in a future release. Workaround Limit the number of disk blades to four per Sun Blade 6000 chassis. Sun Blade 6000 Disk Module Product Notes • May 2010... -
Page 27: Solaris Os Will Not Install On 1 Tbyte Raid
Solaris OS Will not Install on 1 TByte RAID The Oracle Solaris OS cannot be installed on a RAID array larger than one terabyte. The Solaris installer OS doesn’t support it. Workaround There is no workaround for this issue. Delete All Partitions Error With SUSE Linux Installer (6729550) If you choose to delete all partitions during SUSE Linux installation and you are using a disk blade with two SAS-NEMs and no hardware RAID, you will see a... -
Page 28: Raidctl Operations Can Take More Than One Minute (6723851)
2. When the format command results in a driver not available message, use the cfgadm -c command to unconfigure the corresponding disk access point, regardless of whether a volume is created or deleted. Sun Blade 6000 Disk Module Product Notes • May 2010... -
Page 29: Solaris Patch Required For Miniroot Of Network Installers (6634536)
Solaris Patch Required for Miniroot of Network Installers (6634536) Solaris 10 5/08 cannot be installed on server blades whose paired disk blade contains above a certain number of hard drives. A patch must be added to the miniroot of network install servers for users who maintain network install servers. Workaround This is the procedure for adding patch 138076-02 to the x86 miniroot. -
Page 30: Solaris 0 5/08 Cannot Be Installed From Dvd On Server Blades In Filled Chassis (6735573)
DVD on Server Blades in Filled Chassis (6735573) Solaris 10 5/08 cannot be installed on X6220 blades in a Sun Blade 6000 chassis that contains above a certain number of hard drives in disk blades. An installation from DVD will fail if the chassis is populated with server/disk pairs. -
Page 31: Raidctl -L Truncates Solaris Volume Names (6729161)
raidctl -l Truncates Solaris Volume Names (6729161) When using raidctl -l with a volume name, the output will truncate the volume name to seven characters if the volume target ID is larger than 100. For example, # raidctl -l c0t102d0 Volume Size Stripe... -
Page 32: Raidctl Cannot Set Hot-Spare (6692827)
There is no workaround. Before deleting a volume using the raidctl -d option, please use the mount command to check to see if there are any mounted partitions on the volume. For example: raidctl -l | egrep -i volume Controller: 0 Volume:c0t20d0 Sun Blade 6000 Disk Module Product Notes • May 2010... -
Page 33: Mpt Driver Warning Messages During Solaris System Boot Up (6634061)
To see if any partitions on volume are mounted, execute this command: c0t20d0 # mount | egrep c0t20d0 / on /dev/dsk/c0t20d0s0 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror= panic/dev=800008 on Fri Oct 3 16:16:17 2008 /export/home on /dev/dsk/c0t20d0s7 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror= panic/dev=80000f on Fri Oct 3 16:16:28 2008 This output indicates that the volume does have mounted partitions, one of which is the root (boot) partition, so deleting the volume will lose that data and render the system unbootable. -
Page 34: Sun Blade T6300 And T63200 Server Modules Might Hang At Boot (6662335)
Sun Blade T6300 and T63200 Server Modules Might Hang at Boot (6662335) Sun Blade T6300 and T6320 Server Modules can hang at boot when Sun Blade 6000 10GbE Multi-Fabric NEM is used. This occurs infrequently. Workaround Reboot or reset from Open boot until fix for is available. Contact Sun Service Center if three successive reboot cycles does not resolve the issue. -
Page 35: Solaris Mpxio-Upgrade Incompatible With Zfs (6707555)
Solaris mpxio-upgrade Incompatible with ZFS (6707555) When enabling or disabling MPxIO in conjunction with ZFS root, the system will not reboot cleanly because the mpxio-upgrade does not know how to handle ZFS root. Workaround 1. Disable the mpxio-upgrade service. 2. Run /lib/mpxio/stsmboot_util -u 3. - Page 36 Create a partition on only one of the “two” disks. ■ Create a hardware RAID volume using the SAS host bus adapter’s RAID ■ configuration utility (entered through the server’s BIOS on initial boot-up). Sun Blade 6000 Disk Module Product Notes • May 2010...
Need help?
Do you have a question about the Sun Blade 6000 and is the answer not in the manual?
Questions and answers