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-1338141.1
Update Date:2011-07-22
Keywords:

Solution Type  Problem Resolution Sure

Solution  1338141.1 :   V880/V890 HDD Faulty  


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




In this Document
  Symptoms
  Cause
  Solution


Created from <SR 3-4043443451>

Applies to:

Sun Fire V880 Server - Version: Not Applicable and later   [Release: N/A and later ]
Sun Fire V890 Server - Version: Not Applicable and later    [Release: N/A and later]
Information in this document applies to any platform.

Symptoms


=== ODM Issue Clarification ===
HDD Faulty


=== ODM Issue Verification ===
*** iostat hard errors ***

c1t3d0 Soft Errors: 409 Hard Errors: 118 Transport Errors: 61
Vendor: FUJITSU Product: MAP3735F SUN72G Revision: 1701 Serial No: 0403Q07HJS
Size: 73.40GB <73400057856 bytes>
Media Error: 103 Device Not Ready: 0 No Device: 15 Recoverable: 409
Illegal Request: 0 Predictive Failure Analysis: 2


*** Solaris Volume Manager (SVM / SDS) messages ***

d82: Submirror of d8
State: Needs maintenance
Invoke: metareplace d8 c1t3d0s0
Size: 286688448 blocks
Stripe 0:
Device Start Block Dbase State Hot Spare
c1t3d0s0 0 No Maintenance


*** messages error summary ***

c1t3d0:
Type: Retryable, Quantity: 27 Last message:
Jul 13 16:49:15 vodagpinrt2 scsi: [ID 107833 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010709271,0 (ssd3):
Jul 13 16:49:15 vodagpinrt2 Error for Command: read(10) Error Level: Retryable
Counted for analysis: Yes


suspects
===========
device => suspicion level
c1t3d0 => 11

Cause


=== ODM Cause Determination ===
HDD failure


=== ODM Cause Justification ===
Disk c1t3d0 failed.

Solution


=== ODM Solution / Action Plan ===
1.- Remove the failed disk.
2.- Replace the disk with the new one.
3.- Restore the disk configuration.
4.- Test the system after disk replacement.

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