| Skip Navigation Links | |
| Exit Print View | |
|
Sun Blade Storage Module M2 Product Documentation |
About This Documentation (PDF and HTML)
Overview of the Sun Blade Storage Module M2
Installing the Storage Module Into the Chassis
Assigning and Managing Storage
Overview of the Sun Blade Storage Module M2 Product Notes
Supported Firmware, Hardware and Software
Solaris Operating System Issues
Solaris Operating System Current Issues
Disk Fault and Ready-to-Remove LEDs Do Not Work in Oracle Solaris 10 (6926642)
stmsboot Fails to Map Root Device After a Fresh OS Install (6931924)
Using stmsboot -d to Disable MPxIO Can Cause the System to Not Reboot Successfully (6923599)
Changes in Drive Physical Configuration Causes the Solaris format Utility to Hang (6890270, 6930996)
cfgadm -c unconfigure Fails if Path Specified is to an MPXIO Enabled Device (6948701)
Command for Creating RAID 10 Volume Not Named Correctly (6943131)
Storage Module Disk Ready-to-Remove LED Does Not Work Using cfgadm (6946124)
Performing Maintenance and Hot Plug Actions
Importing Existing Virtual Drives to a Replacement REM
Storage Module Sensors and Indicators
Introduction to the Sun Blade Storage Module M2
Maintaining the Sun Blade Storage Module M2
On a server running Solaris 10 OS 10/09 using a Sun Storage 6Gb SAS REM HBA (SGX-SAS6-REM-Z), the following hot plug actions will cause mpathadm to stop working:
Hotplug or hot removal of a physical drive.
Hotplug or hot removal of a Sun Blade Storage Module M2.
Hotplug or hot removal of a SAS NEM.
If you encounter this issue, reboot the host. To fix this problem, install Solaris patch 141871-03 (x86 systems) or patch 141870–03 (SPARC), available from http://sunsolve.sun.com.
|