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

Asset ID: 1-71-1013107.1
Update Date:2011-04-11
Keywords:

Solution Type  Technical Instruction Sure

Solution  1013107.1 :   How to Identify BIOS and Solaris[TM] Hardware RAID Status  


Related Items
  • Sun Blade 6000 System
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>Blade Servers
  •  

PreviouslyPublishedAs
217959


Description:

This document describes how to identify the RAID disk status of a Solaris[TM] operating environment from BIOS and from within Solaris itself.


Steps to Follow:
The section describes how to reveal RAID status of both the LSI and Adaptec controller cards under BIOS and under Solaris.

A platform's BIOS (Basic Input Output System) is executed by default when power is applied to a system. BIOS output is automatic and will appear on console as indicated.
When presented with the syntax <CTRL> this means press the keyboard CONTROL(CTRL) key. When two or more <> <> identifiers are together this means to press two keyboard keys at the same time, for example <CTRL><A>.
Always perform disk management commands as a root or UID 0 user.
Issue the command /usr/bin/cat /etc/release to determine the Solaris release you are have currently installed.

VERIFY LSI CONTROLLER STATUS FROM WITHIN BIOS:

To verify disk failures within a RAID array on an LSI based controller, the user can view the LSI BIOS at boot time. The utility may tell the user that the RAID array is in a degraded state. Output may vary depending on platform type and configuration:

OUTPUT AT BOOT TIME WITH LSI 1020/1030 CONTROLLER:

HBA ID LUN VENDOR   PRODUCT              REV  SYNC  WIDE   CAPACITY
-------------------------------------------------------------------
0   0  0  LSILOGIC 1030 IM       IM     3000        16     73277 MB
0   7  0  LSILogic LSI1030[    402]  1032300 320.0  16
LSI Logic Corp. MPT boot ROM successfully installed!

OUTPUT AT BOOT TIME WITH LSI 1064/1068 CONTROLLER:

LSI Logic Corp. MPT SAS BIOS                                   
MPTBIOS-6.02.00.00 (2005.07.08)                                
Copyright 2000-2005 LSI Logic Corp.                            
SLOT ID  LUN VENDOR   PRODUCT          REVISION   CAPACITY     
---- --- --- -------- ---------------- ---------- ----------   
0    0  0  LSILOGIC Logical Volume   3000         69618 MB   
0          LSILogic SAS1064-IR       1.04.00.00              

OUTPUT AFTER ENTERING THE LSI BIOS UTILITY:

During BIOS boot, watch for LSI messages prompting you to press <CTRL> <C> to enter the configuration utility.

Press <CTRL> <C> to enter the LSI Logic MPT Setup Utility and select "Raid Properties":

LSI Logic MPT Setup Utility  v6.02.00.00 (2005.07.08)
View Array -- LSI
Array                      1 of 1
Identifier                 LSILOGICLogical Volume  3000
Type                       IM
Scan Order                 2
Size(MB)                   69618
Status                     Degraded
Manage Array
Scan Device  Identifier           RAID   Hot    Drive     Pred  Size
ID                                Disk   Spr    Status    Fail  (MB)
0    FUJITSU MAV2073RCSUN72G 0301 Yes    No     Primary   No    69618    
1    FUJITSU MAV2073RCSUN72G 0301 Yes    No     Failed    No

Note that the “Status” of the array is “Degraded” and disk “ID” “1” has a “Drive Status” of “Failed”

VERIFY LSI CONTROLLER STATUS FROM WITHIN SOLARIS:

Platforms using Solaris 10 Update 3 or lower will produce similar to the following output when configured under LSI hardware RAID management:

Good Volume:

# /usr/sbin/raidctl -l

RAID    Volume  RAID            RAID            Disk
Volume  Type    Status          Disk            Status
------------------------------------------------------
c1t0d0  IM      OK              c1t0d0          OK
c1t1d0          OK

Failed Volume:

# /usr/sbin/raidctl -l

RAID    Volume  RAID            RAID            Disk
Volume  Type    Status          Disk            Status
------------------------------------------------------
c1t0d0  IM      DEGRADED        c1t0d0          OK
c1t1d0          FAILED

Note that the “RAID Status” of the volume is “DEGRADED” and the “RAID Disk” “c1t1d0” has a “Disk Status” of “FAILED”.

Platforms using Solaris 10 Update 4 or higher will produce similar to the following output when configured under LSI hardware RAID management:

Good Volume:

# /usr/sbin/raidctl -l

Controller: 0
Volume:c1t0d0
Disk: 0.0.0
Disk: 0.1.0

In addition to this, specifics for the "Volume" can be listed by executing the command as follows:

# /usr/sbin/raidctl -l c1t0d0

Volume      Sub         Size    Stripe  Status   Cache  RAID
Disk                Size                    Level
----------------------------------------------------------------
c1t0d0                  68.3G   N/A     OPTIMAL  N/A    RAID1
0.0.0       68.3G           GOOD
0.1.0       68.3G           GOOD

Failed Volume:

# /usr/sbin/raidctl -l

Controller: 0
Volume:c1t0d0
Disk: 0.0.0
Disk: 0.1.0

In addition to this, specifics for the "Volume" can be listed by executing the command as follows:

# /usr/sbin/raidctl -l c1t0d0

Volume          Sub     Size    Stripe  Status   Cache  RAID
Disk            Size                    Level
----------------------------------------------------------------
c1t0d0                  68.3G   N/A     DEGRADED  N/A   RAID1
0.0.0   68.3G           GOOD
0.1.0   68.3G           FAILED

Note that the “Status” of the “Volume” “c1t0d0” is “DEGRADED” and the “Sub Disk” “0.1.0” has a “Status” of “FAILED”.

In failed situations, the user should try to perform the following before considering a disk replacement:

  1. Reinsert the suspect drive to check the drive is properly seated.

  2. Check any internal flex cables to the disk backplane for loose connectivity or damage.

  3. Recheck the LSI MPT BIOS Utility status.

VERIFY ADAPTEC CONTROLLER STATUS FROM WITHIN BIOS:

To verify disk failures within a RAID array on an Adaptec / Sun STK based controller, the user can view the Adaptec RAID BIOS at boot time. The utility may tell the user that the RAID array is in a degraded state.

Output may vary depending on platform type and configuration:

OUTPUT AT BOOT TIME WITH SUN STK ADAPTEC CONTROLLER:

Adaptec RAID BIOS V5.3-0 [Build 16732]
(c) 1998-2008 Adaptec, Inc. All Rights Reserved
Press <Ctrl><A> for Adaptec RAID
Booting the Controller Kernel....Controller started
Controller #00: Sun STK RAID EXT at PCI Slot:02, Bus:04, Dev:00, Func:00
Waiting for Controller to Start....Controller started
Controller monitor V5.3-0 [16732], Controller kernel V5.3-0 [16732]
Battery Backup Unit Present
Controller POST operation successful
Controller Memory Size: 256 MB
Controller Serial Number: SOMESERIALNUM
Controller WWN: SOMEWWNNUMBER

One or more drives are either missing or not responding.
Please check if the drives are connected and powered on.
Press <Enter> to accept the current configuration.
Press <Ctrl-A> to enter Adaptec RAID Configuration Utility.
Press <Ctrl-H> to Pause Configuration Messages.
(Default is not to accept if no valid key pressed in 30 second)
Timeout. BIOS took the default Configuration.

Location         Model             Rev#    Speed  Size
----------------------------------------------------------
J3 : Dev 00 ATA  SEAGATE ST32500N  3AZQ    3.0G   238.4 GB
-- : --          No device

Note that the “Location” of the device “Dev 01” is missing populated information and the “Model” of the disk is populated as “No device

VERIFY ADAPTEC CONTROLLER STATUS FROM WITHIN SOLARIS:

Verify if the “StorMan” package is installed otherwise the following commands will not be available to query the array status. Output may vary depending on platform type and configuration:

StorMan not installed:

# /usr/bin/pkginfo -l StorMan
ERROR: information for "StorMan" was not found

StorMan installed:

# /usr/bin/pkginfo -l StorMan
PKGINST: StorMan

NAME: Sun StorageTek RAID Manager
CATEGORY: application
ARCH: i386
VERSION: 6.10 (17551)
BASEDIR: /
VENDOR: Sun
DESC: Sun StorageTek RAID Manager for Sun Solaris 10 (i386)
PSTAMP: Tue Jun 9 09:47:21 2009
INSTDATE: Sep 03 2009 11:01
STATUS: completely installed
FILES: 403 installed pathnames
11 directories
392 executables
45211 blocks used (approx)

If the StorMan package is not installed, refer to the www.intel.com/support/go/sunraid.htm site to download and install the utility.

Once installed, execute the following command to review the array status. Output may vary depending on platform type and configuration:

# /opt/StorMan/arcconf GETCONFIG 1
Controllers found: 1
-----------------------------------------------------------
Controller information
-----------------------------------------------------------
Controller Model : Sun STK RAID
Physical Slot : 3
Temperature : 73 C/ 163 F
Installed memory : 256 MB
Defunct disk drive count : 1
Logical devices/Failed/Degraded : 1/0/1
----------------------------------------------------------------------
Logical device information
----------------------------------------------------------------------
Logical device name : Array
RAID level : 1
Status of logical device : Degraded
Size : 238471 MB
Stripe-unit size : 256 KB
Protected by Hot-Spare : No
Bootable : Yes
Failed stripes : No
--------------------------------------------------------
Logical device segment information
--------------------------------------------------------
Segment 0 : Present (0,0) SOMESERIALNUM
Segment 1 : Inconsistent (0,1) SOMESERIALNUM
----------------------------------------------------------------------
Physical Device information
----------------------------------------------------------------------
Device #0
State : Online
Reported Channel,Device : 0,0
Reported Location : Connector 0, Device 0
Model : SEAGATE ST32500N
Size : 238471 MB
Device #1
State : Failed
Reported Channel,Device : 0,1
Reported Location : Connector 0, Device 1
Model : SEAGATE ST32500N
Size : 0 MB

The output show above is an extract from the full output provided on screen with failures in BOLD.

In failed situations, the user should try to perform the following before considering a disk replacement:

  1. Reinsert the suspect drive to check the drive is properly seated.

  2. Check any internal flex cables to the disk backplane for loose connectivity or damage.

  3. Recheck the Adaptec BIOS Utility status.

Previously Published As 91624
Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback