![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||
Solution Type Problem Resolution Sure Solution 1551086.1 : raidctl output shows inconsistent configuration information (T1000/T2000)
raidctl output may show inconsistent configuration information if there are two raid volumes configured, and Solaris version is Solaris10_U4 or older and raidctl patches are not applied In this Document
Created from <SR 3-7109455966> Applies to:Sun Fire T2000 Server - Version Not Applicable to Not Applicable [Release N/A]Sun SPARC Enterprise T2000 Server - Version Not Applicable to Not Applicable [Release N/A] Sun Fire T1000 Server - Version Not Applicable to Not Applicable [Release N/A] Sun SPARC Enterprise T1000 Server - Version Not Applicable to Not Applicable [Release N/A] Sun SPARC Enterprise T5140 Server Oracle Solaris on SPARC (64-bit) Oracle Solaris on SPARC (32-bit) Generic UNIX Sysadmins use raidctl in order to check current raid volumes configuration and status information from Solaris. Under certain circumstances, raidctl may display inconsistent output. When troubleshooting internal disk errors, sysadmin needs to rely on raidctl information to determine whether there is a hard disk that needs replacement. Symptoms
# cat /etc/release Solaris 10 8/07 s10s_u4wos_12b SPARC Copyright 2007 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 16 August 2007
# showrev -p | egrep 127127 # Notice that the output is empty, meaning patches are not installed.
# raidctl -l Controller: 0 Volume:c0t0d0 Volume:c0t2d0 Disk: 0.2.0 Disk: 0.2.0 Disk: 0.2.0 Disk: 0.2.0 Disk: 0.2.0 Disk: 0.2.0 Disk: 0.2.0 Disk: 0.2.0 Disk: 0.2.0 Disk: 0.2.0 Disk: 0.2.0 # Notice there are two volumes created; and " Disk: 0.2.0 " is displayed many times; there should be 4 different devices, not only one !!
# raidctl -l c0t0d0 Volume Size Stripe Status Cache RAID Sub Size Level Disk ---------------------------------------------------------------- c0t0d0 68.3G N/A DEGRADED N/A RAID1 0.3.0 68.3G FAILED 0.2.0 68.3G GOOD # # # raidctl -l c0t2d0 Volume Size Stripe Status Cache RAID Sub Size Level Disk ---------------------------------------------------------------- c0t2d0 136.6G N/A DEGRADED N/A RAID1 0.3.0 136.6G FAILED 0.2.0 136.6G GOOD
Notice from above that both c0t0d0 and c0t2d0 are shown as they were configured from the same pair of disks (0.3.0 and 0.2.0). This is not a supported configuration; output is inconsistent !
CauseSystem may have hit known bugs; e.g: SolutionWorkaround (requires a system outage): Sysadmins may rely on OBP commands in order to view the correct raid configuration and raid volume components statuses:
Solution: Either
Both approaches fix the raidctl misbehavior described in this document. After fix is implemented, you can confirm raidctl output is correct: # raidctl -l c0t0d0 Volume Size Stripe Status Cache RAID Sub Size Level Disk ---------------------------------------------------------------- c0t0d0 68.3G N/A DEGRADED OFF RAID1 0.0.0 68.3G GOOD 0.1.0 68.3G FAILED # # # raidctl -l c0t2d0 Volume Size Stripe Status Cache RAID Sub Size Level Disk ---------------------------------------------------------------- c0t2d0 136.6G N/A OPTIMAL OFF RAID1 0.2.0 136.6G GOOD 0.3.0 136.6G GOOD
References<NOTE:1520814.1> - Onboard RAID - How to get disk and controller details on model and firmware at Solaris level<NOTE:1013116.1> - How to Verify the LSI RAID Controller is Functional on Sun Fire[TM] V215/V245, Sun Fire[TM] V440/V445, Sun Fire[TM] T1000/T2000. <NOTE:1012950.1> - How to enable Hardware RAID on Sun Fire[TM] T1000/T2000 Servers <NOTE:1009346.1> - How To Use Hardware RAID on the T2000 T1000 Systems <NOTE:1007109.1> - Internal RAID controllers on T1000/T2000, T5120/T5220/T5140/T5240, V215/V245/V440/V445, Ultra 25/45 and Sun Blade T6300/T6320/T6340 <NOTE:1002561.1> - Labeling volumes and drives when working with Sun Fire[TM] T2000 RAID <NOTE:1009723.1> - Troubleshooting inability to see a pre-existing RAID volume on T1000/T2000 T5120/T5140/T5220/T5240/T5440 T6320/T6340 Attachments This solution has no attachment |
||||||||||||||||||
|