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

Asset ID: 1-72-1332311.1
Update Date:2011-07-04
Keywords:

Solution Type  Problem Resolution Sure

Solution  1332311.1 :   V490 HDD Failed  


Related Items
  • Sun Fire V490 Server
  •  
Related Categories
  • PLA-Support>Sun Systems>SPARC>Workgroup Servers>SN-SPARC: SF-Vx90
  •  
  • .Old GCS Categories>Sun Microsystems>Servers>Entry-Level Servers
  •  




In this Document
  Symptoms
  Cause
  Solution


Created from <SR 3-3888764291>

Applies to:

Sun Fire V490 Server - Version: Not Applicable to Not Applicable - Release: N/A to N/A
Information in this document applies to any platform.

Symptoms


=== ODM Issue Clarification ===

Hard drive failed


=== ODM Issue Verification ===

# iostat -en
---- errors ---
s/w h/w trn tot device
0 904 0 904 c1t0d0


d15: Submirror of d5
State: Needs maintenance
Invoke: metareplace d5 c1t0d0s5 <new device>
Size: 16790400 blocks (8.0 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t0d0s5 0 No Maintenance Yes

d14: Submirror of d4
State: Needs maintenance
Invoke: metareplace d4 c1t0d0s4 <new device>
Size: 25175424 blocks (12 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t0d0s4 0 No Maintenance Yes

d13: Submirror of d3
State: Needs maintenance
Invoke: metareplace d3 c1t0d0s0 <new device>
Size: 37752960 blocks (18 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t0d0s0 0 No Maintenance Yes

d11: Submirror of d1
State: Needs maintenance
Invoke: metareplace d1 c1t0d0s1 <new device>
Size: 16790400 blocks (8.0 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t0d0s1 0 No Maintenance Yes

d17: Submirror of d7
State: Needs maintenance
Invoke: metareplace d7 c1t0d0s7 <new device>
Size: 31464192 blocks (15 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t0d0s7 0 No Maintenance Yes

Cause


=== ODM Cause Determination ===

HDD failed


=== ODM Cause Justification ===

Failed disk needs to be replaced.

Solution


=== ODM Solution / Action Plan ===

WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE RESOLUTION ACTIVITY? :

The operating system should be configured by the customer such that the disk drive is free for replacement.
e.g. The disk may be part of Solaris Volume Manager, Veritas Volume Manager, mounted file-system, raw partitions, etc.
A data backup may be required to restore data onto a replaced disk.
If a data backup is not required it is still a wise precaution.

WHAT ACTION DOES THE ENGINEER NEED TO TAKE:

Follow standard ESD procedures to avoid Electrostatic Discharge

1. Open front bezel on the server.

2. Slide the catch to the right, remove the drive

3. Slide the catch to the right, install the new drive.

4. Push the metal level until the HDD clicks in place.

5. Close the front bezel.

OBTAIN CUSTOMER ACCEPTANCE

WHAT ACTION DOES THE CUSTOMER NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:
Reconfigure disk as previously configured. e.g. Part of raid set or mounted file-system or raw partition or other.

PARTS NOTE:
540-6487 [F] 146GB - 15000 RPM FC-AL, Disk Assembly with one of the following disks:

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