| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||
Solution Type Troubleshooting Sure Solution 1008381.1 : Diagnosing missing devices and device warnings for Sun SPARC Servers
PreviouslyPublishedAs 211463 Description This document will assist the user in diagnosing issues with missing device(s) and device warnings for Sun SPARC(R) Servers. Symptoms:
Steps to Follow Please validate that each troubleshooting step below is true for your environment. The steps will provide instructions or a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step. Diagnosing missing devices 1. Verify that the device is not present. Refer to <Document: 1013117.1> How to verify a missing device(s) on Sun SPARC systems. 2. Verify if multiple devices are missing. Refer to <Document: 1013117.1> How to verify a missing device(s) on the Sun SPARC platforms. 3. Verify that environment change has not adversely affected the cables. Visually inspect all drive cables/connectors in the system for possible contamination or damages and re-seat the cables if necessary. The drive/backplane cable locations can be found in the Sun[TM] System Handbook. or the Service Manuals included in the product documentation for the different servers. You may need to check and reconnect the cables, or try a known good cable, issue a reset-all and retest. 4. Verify the HBA controller is not on-board and that moving the controller card to a different slot (or a different bus) or replacing it, doesn't resolve the problem with the missing device. Refer to <Document: 1005523.1> Verifying the HBA controller path and status on Sun SPARC systems. 5. Verify that after motherboard (MB) replacement, devices still
cannot be seen (this step eliminates problems that could be due to
failed MB, failed I/O bridge). On platforms with hardware raid such as,
Sun Fire[TM] T1000/T2000 Sun Sparc Enterprise T5120/T5140/T5220/T5240/T5440,
when a system board is replaced,certain procedures have to be followed to have
the existing RAID volumes be seen after replacement. Refer to 6. At this point, if the user has validated that each troubleshooting step above is true for the environment, and the issue still exists, further troubleshooting is required. Gather the needed data from the console logs and by running explorer. For further assistance you may contact Sun Support. Product Sun Fire V880 Server Sun Fire V890 Server Sun Fire V480 Server Sun Fire V490 Server Sun Fire 280R Server Sun Fire V210 Server Sun Fire V240 Server Sun Fire V215 Server Sun Fire V245 Server Sun Fire V440 Server Sun Fire V445 Server Sun Fire T1000 Server Sun Fire T2000 Server Internal Comments This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the Document Feedback alias(es) listed below:
<Document: 1003733.1> Sun Fire[TM] V440 server: Not All The
Sun Alert 228513: Certain Sun SCSI and FC-AL Disk Drives May
normalized, missing devices, device warnings Previously Published As 91297 Change History Date: 2009-11-25 User name: Dencho Kojucharov Action: Updated Comments: Currency check, audited by Dencho Kojucharov, Entry-Level SPARC Content Lead Date: 2008-08-12 User Name: 79977 Action: Update Comment: Fixed links to Sun Alerts in Internal comments Date: 2007-12-18 User Name: 71396 Action: Approved Comment: Performed final review of article. No changes required. Publishing Version: 3 Attachments This solution has no attachment |
||||||||||||
|
||||||||||||