Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Technical Instruction Sure Solution 1005530.1 : How to Check for Solaris[TM] x64 Disk Errors and Online/Offline Status
PreviouslyPublishedAs 207660
Applies to:Sun Java Workstation W1100zSun Java Workstation W2100z Sun Ultra 20 M2 Workstation Sun Ultra 20 Workstation Sun Ultra 40 M2 Workstation All Platforms GoalSymptoms
This document describes how to identify if a Solaris[TM] x64 operating environments disk is online/offline or has reported errors. This document does not detail how to recover data or replace storage devices. To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Sun x86 Systems SolutionSteps to FollowAlways perform disk management commands as a root or UID0 user. CHECKING DRIVE STATUS: Execute the command "/usr/sbin/format" while logged in as root. Check for the following "drive type unknown" message: #/usr/sbin/format Line numbers and controller numbers (cXtXdX) may vary depending on failure condition, highlighted in BOLD. This message
appears when a disk was originally available to the operating system
but now does not contain a valid disk label (VTOC) or the operating
system is unable to read the disk label. This is an indication of a
disk being corrupt. FURTHER INVESTIGATION: Investigate further by running the following command: # /usr/sbin/cfgadm The resulting output will be similar to below depending on platform type and configuration: #/usr/sbin/cfgadm The above output which may vary depending on configuration refers to a platform that has 2 controllers installed. The first controller is connected to an 2 disk backplane. The second controller is connected to a CD-ROM or DVD device. Possible failures are highlighted in BOLD.
Confirm that a
disk is not disconnected or unconfigured which may explain why the
disk is unavailable to Solaris[TM]. Finally, you may
wish to confirm error messages have not been logged in the system
messages file for a failed disk. /usr/bin/grep -i SCSI /var/adm/messages* We use the keyword SCSI because all storage devices in Solaris including IDE/PATA, SAS, SATA, SCSI, and USB emulate SCSI to be represented as a storage device. Therefore, most error messages reported in the system messages file are prefixed with the word SCSI. Replace as a precaution any disks that show multiple read or write SCSI ASC/ASQ media errors. 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: [email protected] x64, normalized, solaris, disk, RAID Previously Published As 91499 Change History Date: 2010-02-08 User Name: 88029 Action: Currency check Comment: Modernized and adjusted for Oracle migration Attachments This solution has no attachment |
||||||||||||
|