9.4.2 Dynamically Releasing the HDD/SSD From a Logical Domain
9.4.2 Dynamically Releasing the HDD/SSD From a Logical Domain
This section describes the procedure for enabling the removal of an HDD/SSD from the SPARC M12 by using the PCI Hot Plug function.
To remove an HDD/SSD composing the RAID volumes using the hardware RAID function of the SPARC M12, this procedure is not required.
Note - When the target HDD/SSD has a RAID volume configuration generated by software, you need to enable the release of the HDD/SSD from the Oracle Solaris device configuration. Before releasing the HDD/SSD from the Oracle Solaris device configuration, be sure to see the manual for the software or application being used. |
Table 9-10 lists the procedure for dynamically releasing an HDD/SSD.
Step | Operation Description | Execution Location | Command Used |
---|---|---|---|
1 (*1) |
Checking the device path of the target HDD/SSD | primary domain Root domain |
Oracle Solaris 11 # diskinfo Oracle Solaris 10 (*2) # diskinfo -ap |
2 (*1) |
Checking the BB-ID of the SPARC M12-2S that houses the target HDD/SSD | XSCF shell | Oracle Solaris 11 XSCF> showhardconf Oracle Solaris 10 XSCF> showboards -a |
3 | Checking the mounting location of the target HDD/SSD (Ap_Id) | primary domain Root domain |
# cfgadm -al |
4 | Releasing the target HDD/SSD from the Oracle Solaris device configuration | primary domain Root domain |
# cfgadm -c unconfigure <Ap_Id> |
5 | Confirming that you can remove the target HDD/SSD | primary domain Root domain |
# cfgadm -al |
6 | Having the CHECK LED (amber) of the HDD/SSD released from the Oracle Solaris device configuration blink (*3) (*4) | primary domain Root domain |
# cfgadm -x led=fault,mode=blink <Ap_Id> |
7 (*5) |
Turning off the CHECK LED | primary domain Root domain |
# cfgadm -x led=fault,mode=off <Ap_Id> |
*1 When using only one SPARC M12-2 or SPARC M12-2S, skip this operation. *2 Check the device path of the target HDD/SSD and the LSB number of the SPARC M12-2S that houses the HDD/SSD, according to "Appendix A Lists of SPARC M12/M10 System Device Paths" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide. *3 Before removing the HDD/SSD, confirm that the CHECK LED (amber) is blinking. *4 When removing a hard disk, pull it out slightly from its slot, wait for 10 seconds, and then remove it from the slot. *5 When replacing the HDD/SSD, incorporate it into the Oracle Solaris device configuration and then turn off the CHECK LED. For details, see Table 2-22. |
The following example executes the commands for enabling the removal of an HDD/SSD by using the PCI Hot Plug function.
Confirming the HDD/SSD to be released
[Oracle Solaris 11 with SRU 11.4.27.82.1 or later applied]
- Use the diskinfo command to check the device pathname and BB-ID.
# diskinfo D:devchassis-path c:occupant-compdev ------------------------------ --------------------- /dev/chassis/SYS/BB0/HDD0 - /dev/chassis/SYS/BB0/HDD1 - /dev/chassis/SYS/BB0/HDD2 - /dev/chassis/SYS/BB0/HDD3 - /dev/chassis/SYS/BB0/HDD4/disk c5t50000393D82954D6d0 /dev/chassis/SYS/BB0/HDD5 - /dev/chassis/SYS/BB0/HDD6 - /dev/chassis/SYS/BB0/HDD7/disk c5t50000393B81B2446d0 |
[Oracle Solaris 11 without SRU 11.4.27.82.1 or later applied]
- Check the device path of the target HDD/SSD. (Take this step only for a building block configuration connecting two or more SPARC M12-2S units.)
The following example assumes that the user logs in to Oracle Solaris on the control domain and identifies the device path from the logical device name of the HDD/SSD. Write down the character string (three or four characters) in the "****" part of ".../****_HDDxx/..." contained in the identified device path.
primary# diskinfo D:devchassis-path c:occupant-compdev ----------------------------------------------------------- ------------------ /dev/chassis/SYS/BB0/CMUL/HDD0 - /dev/chassis/SYS/BB0/CMUL/HDD1 - (Omitted) /dev/chassis/FUJITSU-BBEXP.500000e0e06d31bf/04GG_HDD00/disk c4t50000394281B5312d0 /dev/chassis/FUJITSU-BBEXP.500000e0e06d31bf/04GG_HDD01/disk c4t50000394281B59D6d0 (Omitted) |
- Check the BB-ID of the SPARC M12-2S that houses the target HDD/SSD. (Take this step only for a building block configuration connecting two or more SPARC M12-2S units.)
The following example assumes that the user logs in to the XSCF shell and checks for a SPARC M12-2S BB-ID where the character string written down in step 1 matches the last four digits of the CMUL serial number. If the character string written down in step 1 consists of three characters, add "0" at the beginning of the character string to make it four characters long for matching purposes.
XSCF> showhardconf (Omitted) BB#00 Status:Normal; Role:Master; Ver:3015h; Serial:PZ51649002; + FRU-Part-Number:CA20369-B17X 005AC/7341758 ; + Power_Supply_System: ; + Memory_Size:256 GB; CMUL Status:Normal; Ver:2101h; Serial:PP164804GG ; (Omitted) BB#01 Status:Normal; Role:Standby; Ver:2290h; Serial:2081236002; + FRU-Part-Number:CA07361-D202 A0 /NOT-FIXD-P2 ; + Power_Supply_System: ; + Memory_Size:128 GB; CMUL Status:Normal; Ver:0101h; Serial:PP1231043X ; (Omitted) |
[Oracle Solaris 10]
- Check the LSB number of the SPARC M12-2S that houses the target HDD/SSD. (Take this step only for a building block configuration connecting two or more SPARC M12-2S units.)
The following example assumes that the user logs in to Oracle Solaris on the control domain and checks the LSB number of the SPARC M12-2S that houses the HDD/SSD based on the device path identified from the logical device name of the HDD/SSD. For details on device paths, see "Appendix A Lists of SPARC M12/M10 System Device Paths" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide.
primary# diskinfo -ap (Omitted) Label Disk name Vendor Product Vers -------- ---------------------- -------- -------------- ---- HDD_0 c0t50000393D8289180d0 TOSHIBA MBF2600RC 3706 Physical path -------------------------------- 0: /pci@8000/pci@4/pci@0/pci@0/scsi@0/iport@f/disk@w50000393D8289180,0 (Omitted) |
- Check the BB-ID of the SPARC M12-2S that houses the target HDD/SSD. (Take this step only for a building block configuration connecting two or more SPARC M12-2S units.)
The following example assumes that the user logs in to the XSCF shell and checks the BB-ID of the SPARC M12-2S from the LSB number identified in step 1.
XSCF> showboards -a PSB PPAR-ID(LSB) Assignment Pwr Conn Conf Test Fault ---- ------------ ----------- ---- ---- ---- ------- -------- 00-0 00(00) Assigned y y y Passed Normal 01-0 00(01) Assigned y y y Passed Normal |
Releasing the HDD/SSD from the Oracle Solaris device configuration
- Check the mounting location of the target HDD/SSD (Ap_Id).
The following example checks the Ap_Id, including the logical device name of the target HDD/SSD, from Oracle Solaris on the control domain.
primary# cfgadm -al Ap_Id Type Receptacle Occupant Condition (Omitted) c2 scsi-sas connected configured unknown c2::dsk/c2t50000394281B59D6d0 disk connected configured unknown c2::es/ses0 ESI connected configured unknown c2::smp/expd0 smp connected configured unknown c3 scsi-sas connected unconfigured unknown c4 scsi-sas connected unconfigured unknown c5 fc connected unconfigured unknown c6 fc connected unconfigured unknown c7 scsi-sas connected unconfigured unknown (Omitted) |
- Release the HDD/SSD from the Oracle Solaris device configuration.
The following example assumes that the user logs in to Oracle Solaris on the control domain and releases the HDD/SSD from the Oracle Solaris device configuration by using the Ap_Id checked in step 3.
primary# cfgadm -c unconfigure c2::dsk/c2t50000394281B59D6d0 |
- Confirm that you can remove the HDD/SSD.
The following example assumes that the user logs in to Oracle Solaris on the control domain and confirms that the HDD/SSD has been released from the Oracle Solaris device configuration.
primary# cfgadm -al Ap_Id Type Receptacle Occupant Condition (Omitted) c2 scsi-sas connected configured unknown c2::dsk/c2t50000394281B59D6d0 disk connected unconfigured unknown c2::es/ses0 ESI connected configured unknown c2::smp/expd0 smp connected configured unknown c3 scsi-sas connected unconfigured unknown c4 scsi-sas connected unconfigured unknown c5 fc connected unconfigured unknown c6 fc connected unconfigured unknown c7 scsi-sas connected unconfigured unknown (Omitted) |
- Have the CHECK LED (amber) of the HDD/SSD to be removed blink.
The following example assumes that the user logs in to Oracle Solaris on the control domain, causing the CHECK LED (amber) of the HDD/SSD to blink. Check the LEDs on the HDD/SSD, and then remove it. When removing a hard disk, pull it out slightly from its slot, wait for 10 seconds, and then remove it.
primary# cfgadm -x led=fault,mode=blink c2::dsk/c2t50000394281B59D6d0 |
< Previous Page | Next Page >