Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Technical Instruction Sure Solution 1017961.1 : How to Identify if a Solaris[TM] Operating Environment is Installed on a Hardware RAID Controller
PreviouslyPublishedAs 229233
Applies to:Sun Fire X4200 M2 ServerSun Fire X4200 Server Sun Fire X4440 Server Sun Fire X4500 Server Sun Fire X4540 Server All Platforms GoalSymptoms:
This document describes how to identify if a Solaris[TM] operating environment is installed under the control of a platforms hardware RAID management device. 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
SolutionDescriptionSummary This document describes how to identify if a Solaris[TM] operating environment is installed under the control of a platforms hardware RAID management device.
Symptoms
Steps to Follow Always perform disk management commands as the root user. IDENTIFY THE ROOT FILESYSTEM DISK DEVICE: Use the Solaris df command to identify the Solaris root filesystem disk device (the system disk that contains the operating system root filesystem): # df / / (/dev/dsk/c1t0d0s0 ):132034832 blocks 8243082 files In this example, the root filesystem resides on /dev/dsk/c1t0d0s0. Dropping the 's0' partition slice information will leave us with the disk device name: /dev/dsk/c1t0d0, which can be further abbreviated to just c1t0d0 . ( For more detailed information on Solaris disk device naming, refer to Logical Disk device Naming in the System Administration Guide: Basic Administration ) The Solaris format / inquiry command can be used to display the properties of the system disk that will help determine whether the disk is under hardware RAID management control. NOT UNDER THE CONTROL OF HARDWARE RAID MANAGEMENT: Run the Solaris format command specifying the disk device name you identified in the previous step (this example uses c1t0d0, however this will be different from system to system): # format c1t0d0 selecting c1t0d0 [disk formatted] FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk fdisk - run the fdisk program repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name ! quit format> inquiry Vendor: SEAGATE Product: ST914602SSUN146G Revision: 0400 format> The Vendor and Product properties reveal the disk drive manufacturer is "SEAGATE" and drive model is "ST914602SSUN146G". This is a physical disk, not a RAID volume. UNDER THE CONTROL OF HARDWARE RAID MANAGEMENT: format> inquiry Vendor: LSILOGIC Product: Logical Volume Revision: 3000 format> Above, the disk properties identify this disk device as being a Logical (RAID) volume on an LSI controller. format> inquiry Vendor: Sun Product: STK RAID INT Revision: V1.0 format> This last example shows the disk is a RAID Volume on a Sun StorageTek INT RAID controller. For information on how to check the status of a hardware RAID volume, please see: How to Identify BIOS and Solaris[TM] Hardware RAID Status (Doc ID 1013107.1) 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: tsc-emea-x64@sun.com x64, normalized, solaris, RAID Previously Published As 91489 Change History Date: 2007-12-13 User Name: 95826 Action: Approved Comment: - verified metadata - review date ok : 2008-12-12 - checked normalized data - checked for TM - 2 added - checked audience : contract Publishing Version: 3 Attachments This solution has no attachment |
||||||||||||
|