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)
Removal of Devices Breaks mpathadm in Solaris (6908971, 6919439)
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 Sun Blade X6270 M2 with a Sun Storage 6Gb SAS REM HBA (SGX-SAS6-REM-Z), the Solaris cfgadm -c unconfigure command fails if the path specified is to an MPXIO enabled device.
Select the disk that you want to unplug.
In this example we want to unplug the drive c0t5000C5000F0FE227d0.
# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t5000C5000F0E5AFFd0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /scsi_vhci/disk@g5000c5000f0e5aff 1. c0t5000C5000F0FE227d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /scsi_vhci/disk@g5000c5000f0fe227
Run mount(1M) to identify whether the device is mounted or if it is a boot drive.
The following is an example on how to identify if the drive is mounted:
# mount | grep c0t5000C5000F0E5AFFd0 /mnt on /dev/dsk/c0t5000C5000F0E5AFFd0s6 read/write/setuid/devices/intr/largefiles /logging/xattr/onerror=panic/dev=600016 on Fri Jun 4 10:37:08 2010
To identify if the drive is a boot drive, see the following example:
bash-3.00# mount | grep c0t5000C5000F0FE227d0 / on /dev/dsk/c0t5000C5000F0FE227d0s0 read/write/setuid/devices/intr/largefiles /logging/xattr/onerror=panic/dev=800010 on Wed Jun 9 09:58:24 2010 /export/home on /dev/dsk/c0t5000C5000F0FE227d0s7 read/write/setuid/devices/intr /largefiles/logging/xattr/onerror=panic/dev=800017 on Wed Jun 9 09:59:13 2010 Note: "/" root directory
Run fuser(1M) command to identify the process(es) accessing the disk.
Example of no processes accessing the disk:
# fuser -d /dev/dsk/c0t5000C5000F0E5AFFd0s2 /dev/dsk /c0t5000C5000F0E5AFFd0s2:
Example when a process is accessing the disk (fuser identifies the process):
bash-3.00# fuser -d /dev/dsk/c0t5000C5000F0FE227d0s2 /dev/dsk /c0t5000C5000F0FE227d0s2: 1036o bash-3.00# ps -ef | grep 1036 root 1036 982 0 11:56:34 pts/2 0:02 dd if=/dev/dsk/c0t5000C5000F0E5AFFd0s2 of=/dev/dsk/c0t5000C5000F0FE227d0s7
Kill all of the processes identified in Step 3. For example:
kill —p PID
or
kill —P PID
Do one of the following to remove the disk:
If the disk is not a boot drive, umount the mount points and then run sync(1M) to flush the disk:
# umount /mnt # mount |grep c0t5000C5000F0E5AFFd0 # sync Remove the disk safely.
If the disk is a boot drive, run sync(1M) to flush the disk and shutdown the system:
bash-3.00# sync bash-3.00# init 0 Remove the disk safely.