Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1007367.1
Update Date:2011-05-11
Keywords:

Solution Type  Technical Instruction Sure

Solution  1007367.1 :   Removing and Replacing the Sun Fire[TM] 280R , Sun Fire[TM] V480 ,Sun Fire[TM] V490 ,Sun Fire[TM] V880 ,Sun Fire[TM] V880z or Sun Fire[TM] V890 Hot-Pluggable Internal Disk Drives.  


Related Items
  • Sun Fire V480 Server
  •  
  • Sun Fire 280R Server
  •  
  • Sun Fire V880z Visualization Server
  •  
  • Sun Fire V890 Server
  •  
  • Sun Fire V880 Server
  •  
  • Sun Fire V490 Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>Entry-Level Servers
  •  

PreviouslyPublishedAs
210174


Description
Documented below is the proper procedure for removing and replacing failed Sun Fire hot-pluggable internal disk drives (FC-AL).

The system's disk hot-plug feature allows you to remove a disk drive without shutting down the operating system or powering the system off.



Steps to Follow
When you remove a hot-pluggable drive, you need to stop the drive and take it off-line to remove the logical software links to the drive. Use the luxadm and the devfsadm command tools to remove the internal disk(s). The following procedure describes the general steps involved, (your specific device names may be different).

First, if the disk was under control of  a volume management software (e.g. Solaris[TM] Volume Manager, Veritas Volume Manager), make sure to take the necessary steps for the disk replacement in the software before and after issuing the following disk replacement procedure.

In case of Veritas Volume Manager (VxVM), please refer to <Document: 1003122.1> , <Document: 1011782.1>  , and <Document: 1002285.1> for additional information.

In case of Solaris Volume Manager (SVM), please refer to <Document: 1010753.1>  for additional information.

Removing the failed disk:

As superuser, enter the following command,

# /usr/sbin/luxadm remove_device /dev/rdsk/<c1t1d0s2>

WARNING!!! Please ensure that no file systems are mounted on these device(s).

All data on these devices should have been backed up.

The list of devices which will be removed is:
1: Device name: /dev/rdsk/c1t1d0s2
Node WWN: 20000020371b1f31
Device Type: Disk device
Device Paths: /dev/rdsk/c1t1d0s2
Please verify the above list of devices and then enter c or <CR> to Continue or q to Quit. [Default: c]:c
stopping: /dev/rdsk/c1t1d0s2.... Done
offlining: /dev/rdsk/c1t1d0s2.... Done
The drives are now off-line and spun down.
Physically remove the disk and press the Return key.

Hit <Return> after removing the device(s).

<date> <systemname> picld[87]: Device DISK1 removed
Device: /dev/rdsk/c1t1d0s2
No FC devices found. - /dev/rdsk/c1t1d0s2

Note: If 'luxadm remove_device' fails, please follow the below procedure.

  • physically pull the bad disk

  • luxadm -e offline /dev/rdsk/c1t1d0s2

  • if the disk is multipathed, run 'luxadm -e offline' on the second path as well.

Note: The 
picld
 daemon notifies the system that the disk has been removed.

Initiate devfsadm cleanup subroutines by entering the following command:

# /usr/sbin/devfsadm -C

The default devfsadm operation is to attempt to load every driver in the system and attach these drivers to all possible device instances. devfsadm then creates device special files in /devices and logical links in /dev.

The -C option cleans up the /dev directory and removes any lingering logical links to the device link names.

Installing a new disk:

As superuser, list the system's current logical device links.

# ls /dev/rdsk/c1t1d*

You should have no match.

Insert the drive in its disk bay and enter the following command:

# /usr/sbin/devfsadm

or

# /usr/sbin/luxadm insert_device <enclosure_name>,sx

where x is the slot number. (Use luxadm display <enclosure_name> to find the slot number. To find the <enclosure_name> do a luxadm probe .)

List the system's current c1t1d* logical device links.

# ls /dev/rdsk/c1t1d*

you should see,

/dev/rdsk/c1t1d0s0 /dev/rdsk/c1t1d0s1 /dev/rdsk/c1t1d0s2
/dev/rdsk/c1t1d0s3 /dev/rdsk/c1t1d0s4 /dev/rdsk/c1t1d0s5
/dev/rdsk/c1t1d0s6 /dev/rdsk/c1t1d0s7

NOTE:

If you have not configured the system with two boot disks, you cannot hot-plug a single boot disk. You can only hot-plug the boot disk if you have configured a two-disk mirror of the boot disk for hot-plugging. If the system is configured with a boot disk and a data disk, you may hot-plug the data disk, not the boot disk.



Product
Sun Fire V480 Server
Sun Fire V880 Server
Sun Fire 280R Server
Sun Fire V880z Visualization Server
Sun Fire V890 Server
Sun Fire V490 Server

Internal Comments
Audited/updated 11/19/09 - Ian.Macdonald@Sun.COM, Entry Level SPARC Content Team Member




v890, v880, v490, v480, 280R, 280, 480, 490, 880, 880z, 890, replace disk, failed drive, disk, drive
Previously Published As
40517

Change History
Date: 2011-05-11
User name: Dencho Kojucharov
Action: Currency check
Comments: audited by Entry-Level SPARC Content Lead
Date: 2009-11-13
User Name: 79977
Action: Updated
Comment: Currency update, audited by Dencho Kojucharov, Entry-Level SPARC Content Lead
Verified Keywords - ok
Date: 2006-10-30
User Name: 31620
Action: Approved
Comment: Verified Metadata - ok
Verified Keywords - ok

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback