Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1012018.1
Update Date:2017-02-02
Keywords:

Solution Type  Technical Instruction Sure

Solution  1012018.1 :   How To replace an Internal disk on a Sun Fire[TM] V1280/E2900 & Netra[TM] 1280/1290  


Related Items
  • Sun Netra 1290 Server
  •  
  • Sun Fire V1280 Server
  •  
  • Sun Fire E2900 Server
  •  
  • Sun Netra 1280 Server
  •  
Related Categories
  • PLA-Support>Sun Systems>SPARC>Enterprise>SN-SPARC: SF-x8x0/Ex900
  •  
  • _Old GCS Categories>Sun Microsystems>Servers>Entry-Level Servers
  •  
  • _Old GCS Categories>Sun Microsystems>Servers>Midrange Servers
  •  
  • _Old GCS Categories>Sun Microsystems>Servers>Midrange V and Netra Servers
  •  

PreviouslyPublishedAs
216470


Applies to:

Sun Netra 1280 Server - Version Not Applicable and later
Sun Fire V1280 Server - Version Not Applicable and later
Sun Fire E2900 Server - Version Not Applicable and later
Sun Netra 1290 Server - Version Not Applicable and later
All Platforms

Goal

The following is the procedure to remove internal disks in the Sun Fire[TM] V1280/E2900 & Netra[TM] 1280/1290. It is not recommended to remove a disk if the power LED is on and the ok_to_remove LED is not ON.

Fix


When identifying a disk for replacement in a V1280/E2900 & Netra[TM] 1280/1290, the disk target to physical slot locations are as follows:

 

target 0 (cXt0dY) = the disk in the lower physical slot
target 1 (cXt1dY) = the disk in the upper physical slot

X = controller number
Y = disk number

 

Once disk is identified, you need to detach/unmount/unconfigure your disk/filesystems through the software you are using (for example, Solstice DiskSuite[TM]), otherwise you risk damaging them. The ok_to_remove LED should be lit, when the disk is unconfigured using cfgadm. Also, keep in mind that the power/active LED goes on when the disk is mounted, but only goes off if the power is removed in the IB_SSC. There are no individual switches in the power feeds to either of the disks.

The following is an example of how it should appear:
In this case we will remove disk1 (target 1),

 

# cfgadm -a
Ap_Id Type Receptacle Occupant Condition
N0.IB6 PCI_I/O_Boa connected configured ok
N0.IB6::pci0 io connected configured ok
N0.IB6::pci io connected configured ok
N0.IB6::pci2 io connected configured ok
N0.IB6::pci3 io connected configured ok
N0.SB0 CPU_Board_( connected configured ok
N0.SB0::cpu0 cpu connected configured ok
N0.SB0::cpu1 cpu connected configured ok
N0.SB0::cpu2 cpu connected configured ok
N0.SB0::cpu3 cpu connected configured ok
N0.SB0::memory memory connected configured ok
N0.SB2 CPU_Board_( connected configured ok
N0.SB2::cpu0 cpu connected configured ok
N0.SB2::cpu1 cpu connected configured ok
N0.SB2::cpu2 cpu connected configured ok
N0.SB2::cpu3 cpu connected configured ok
N0.SB2::memory memory connected configured ok
N0.SB4 unknown empty unconfigured unknown
c1 scsi-bus connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::dsk/c1t1d0 disk connected configured unknown
c2 scsi-bus connected unconfigured unknown

 

Note above that c1t1d0 is connected and configured.
Now check to see what is mounted on that drive.
Unmount anything mounted on that drive next.

 

 

# mount
/ on /dev/dsk/c1t0d0s0 read/write/setuid/intr/largefiles/xattr/onerror=panic/dev=800000 on Thu Aug 14 14:11:59 2003
/proc on /proc read/write/setuid/dev=41c0000 on Thu Aug 14 14:11:58 2003
/etc/mnttab on mnttab read/write/setuid/dev=4280000 on Thu Aug 14 14:11:58 2003
/dev/fd on fd read/write/setuid/dev=42c0000 on Thu Aug 14 14:11:59 2003
/var/run on swap read/write/setuid/xattr/dev=1 on Thu Aug 14 14:12:00 2003
/tmp on swap read/write/setuid/xattr/dev=2 on Thu Aug 14 14:12:02 2003
/export/home on /dev/dsk/c1t0d0s7 read/write/setuid/intr/largefiles/xattr/onerror=panic/dev=800007 on Thu Aug 14 14:12:02 2003
 

If the disk does not show up as connected or configured in the `cfgadm -a` above, it may have been removed already, or failed in a way that it is not present in the OS.   The cfgadm -c unconfigure in the next step will fail. Proceeding with replacement may work, and trying to add the device path to the OS with devsadm -C may bring the device into SOlaris and create the device path, so the cfgadm -c unconfgure will work.

 

# cfgadm -c unconfigure c1::dsk/c1t1d0
Aug 14 15:39:46 Lightweight genunix: /ssm@0,0/pci@18,600000/scsi@2/sd@1,0(sd1) offline
# cfgadm -a
Ap_Id Type Receptacle Occupant Condition
N0.IB6 PCI_I/O_Boa connected configured ok
N0.IB6::pci0 io connected configured ok
N0.IB6::pci1 io connected configured ok
N0.IB6::pci2 io connected configured ok
N0.IB6::pci3 io connected configured ok
N0.SB0 CPU_Board_( connected configured ok
N0.SB0::cpu0 cpu connected configured ok
N0.SB0::cpu1 cpu connected configured ok
N0.SB0::cpu2 cpu connected configured ok
N0.SB0::cpu3 cpu connected configured ok
N0.SB0::memory memory connected configured ok
N0.SB2 CPU_Board_( connected configured ok
N0.SB2::cpu0 cpu connected configured ok
N0.SB2::cpu1 cpu connected configured ok
N0.SB2::cpu2 cpu connected configured ok
N0.SB2::cpu3 cpu connected configured ok
N0.SB2::memory memory connected configured ok
N0.SB4 unknown empty unconfigured unknown
c1 scsi-bus connected configured unknown
c1::dsk/c1t0d0 disk connected configured unknown
c1::dsk/c1t1d0 disk connected unconfigured unknown
c2 scsi-bus connected unconfigured unknown
#
 

Note above that c1t1d0 is now unconfigured. At this point the yellow light is on the 'ok-to-remove` LED. Now you can remove the disk.
Put the new drive in, the yellow LED will still be lit beside the drive.


Next, configure the new disk.

 

# cfgadm -c configure c1::dsk/c1t1d0

Check to see that it is configured.

 

# cfgadm -a
Ap_Id                   Type         Receptacle   Occupant    Condition
N0.IB6                  PCI_I/O_Boa  connected    configured   ok
N0.IB6::pci0            io           connected    configured   ok
N0.IB6::pci1            io           connected    configured   ok
N0.IB6::pci2            io           connected    configured   ok
N0.IB6::pci3            io           connected    configured   ok
N0.SB0                  CPU_Board_(  connected    configured   ok
N0.SB0::cpu0            cpu          connected    configured   ok
N0.SB0::cpu1            cpu          connected    configured   ok
N0.SB0::cpu2            cpu          connected    configured   ok
N0.SB0::cpu3            cpu          connected    configured   ok
N0.SB0::memory          memory       connected    configured   ok
N0.SB2                  CPU_Board_(  connected    configured   ok
N0.SB2::cpu0            cpu          connected    configured   ok
N0.SB2::cpu1            cpu          connected    configured   ok
N0.SB2::cpu2            cpu          connected    configured   ok
N0.SB2::cpu3            cpu          connected    configured   ok
N0.SB2::memory          memory       connected    configured   ok
N0.SB4                  unknown      empty        unconfigured unknown
c1                      scsi-bus     connected    configured   unknown
c1::dsk/c1t0d0          disk         connected    configured   unknown
c1::dsk/c1t1d0          disk         connected    configured   unknown
c2                      scsi-bus     connected    unconfigured unknown

# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
      0. c1t0d0 
         /ssm@0,0/pci@18,600000/scsi@2/sd@0,0
      1. c1t1d0 
         /ssm@0,0/pci@18,600000/scsi@2/sd@1,0

 

The disk is now available for use and can be configured as needed using disk management software (for example, Solstice DiskSuite[TM]).



 

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in an appropriate
My Oracle Support Community - Oracle Sun Technologies Community.





Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback