Solution Raidconf

Solution Type Technical Instruction
Solution 203544 : Labeling volumes and drives when working with Sun
Fire[TM] T2000 RAID
Related Categories
* Home>Product>Systems>Servers
Description
JYBFU5F Internal ID use only.
After creating or deleting a RAID volume on the Sun Fire[TM] T2000

server, steps need to be taken to properly label the newly created
volume or the available drives (used in the RAID volume) so that
Solaris[TM] may use them correctly.
Steps to Follow
NA8WC3F Internal ID use only.
After using the 'raidctl' command to create a RAID volume on the T2000
the user needs to ensure that steps are taken to label the volume
properly for use by Solaris. The 'raidctl' command will create the
volume, but it does not create a new label for this volume so Solaris
will not see the correct information until this step is taken.
here is an example of creating and labeling a striped RAID volume:

----------
root@t2000 # raidctl -c -r 0 c3t1d0 c3t2d0 c3t3d0

Creating RAID volume c3t1d0 will destroy all data on member disks,
proceed (yes/no)? yes
Apr 14 11:23:40 t2000 scsi: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2
(mpt0):
Apr 14 11:23:40 t2000 Physical disk 0 created.
(mpt0):
(mpt0):
(mpt0):
Apr 14 11:23:42 t2000 Volume 1 created.
(mpt0):
Apr 14 11:23:42 t2000 Volume 1 is |enabled||optimal|
(mpt0):
Apr 14 11:23:42 t2000 Volume 1 is |enabled||optimal|
Volume 'c3t1d0' created
root@t2000 #
root@t2000 # raidctl
RAID Volume RAID RAID Disk
Volume Type Status Disk Status
------------------------------------------------------
c3t1d0 IS OK c3t1d0 OK
c3t2d0 OK
c3t3d0 OK
root@t2000 # format
Searching for disks...done
AVAILABLE DISK SELECTIONS:

0. c3t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@0,0
Specify disk (enter its number): 1
----------
As you can see the volume c3t1d0 still displays the label of the 72GB
disk even though it is now a striped RAID volume of ~204 GB. It needs to
be labeled correctly by using the 'type' and 'label' options in the
format utility.
First, eelect the 'type' command at the 'format>' prompt, then select 0
(zero) to auto configure the volume:
----------

selecting c3t1d0
[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
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
!<cmd> - execute <cmd>, then return
quit
format> type
AVAILABLE DRIVE TYPES:
0. Auto configure
1. Quantum ProDrive 80S
3. CDC Wren IV 94171-344
4. SUN0104
5. SUN0207
6. SUN0327
7. SUN0340
8. SUN0424
9. SUN0535
10. SUN0669
11. SUN1.0G
12. SUN1.05
13. SUN1.3G
14. SUN2.1G
15. SUN2.9G
16. Zip 100
17. Zip 250
18. Peerless 10GB
19. SUN72G
20. other
Specify disk type (enter its number)[19]: 0
c3t1d0: configured with capacity of 204.49GB
<LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 409>
selecting c3t1d0
[disk formatted]
format>
------------
Write the new label to the disk using the 'label' command:
------------
format> label
Ready to label disk, continue? yes
format> disk

1. c3t1d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec
409>
Specify disk (enter its number)[1]:
----------
Now, after the label has been fixed, the volume will be properly
recognized by the format utility.
The same needs to be done after deleting a volume for Solaris to

properly recognize the newly available disks that were previously used
by the RAID volume. Before correcting the label, you may see messages
like this indicating the label is not correct:
----------
WARNING: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/sd@1,0 (sd4):
Corrupt label - bad geometry
Label says 428854496 blocks; Drive says 143374738 blocks
----------
These messages will be not be seen after the label is corrected. Here is
an example of the deletion of a volume and creating a proper label
afterwards:
----------
RAID Volume RAID RAID Disk
Volume Type Status Disk Status
------------------------------------------------------
c3t1d0 IS OK c3t1d0 OK
c3t2d0 OK
c3t3d0 OK
root@t2000 # raidctl -d c3t1d0

Deleting volume c3t1d0 will destroy all data it contains, proceed
(yes/no)? yes
(mpt0):
Apr 14 15:38:23 t2000 Volume 1 deleted.
(mpt0):
Apr 14 15:38:23 t2000 Physical disk 0 deleted.
(mpt0):
(mpt0):
Volume 'c3t1d0' deleted.
No RAID volumes found
root@t2000 # format
Searching for disks...done

1. c3t1d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec
409>
Specify disk (enter its number):
----------
Notice that the RAID volume label is still showing on c3t1d0. This will
be corrected with the same steps used to create the label before. Select
the 'type' command at the 'format>' prompt, then select 0 (zero) to auto
configure the drive:
----------

selecting c3t1d0
[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
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
!<cmd> - execute <cmd>, then return
quit
format> type
AVAILABLE DRIVE TYPES:

0. Auto configure
3. CDC Wren IV 94171-344
4. SUN0104
5. SUN0207
6. SUN0327
7. SUN0340
8. SUN0424
9. SUN0535
10. SUN0669
11. SUN1.0G
12. SUN1.05
13. SUN1.3G
14. SUN2.1G
15. SUN2.9G
16. Zip 100
17. Zip 250
18. Peerless 10GB
19. SUN72G
20. LSILOGIC-LogicalVolume-3000
21. other
Specify disk type (enter its number)[20]: 0
c3t1d0: configured with capacity of 68.35GB
<SUN72G cyl 14087 alt 2 hd 24 sec 424>
selecting c3t1d0
[disk formatted]
format>
------------
Write the new label to the disk using the 'label' command:
------------
format> label
Ready to label disk, continue? yes
format> disk

Specify disk (enter its number)[1]:
----------
The drives may now be used normally by Solaris again. Depending upon what type of
RAID volume was in use, you may need
MANY, many, .. tools
A wide variety of performance tools can be found.. from the high end.. using
end-to-end third party products such as Teamquest (which provides a graphical,
historical vantage point).. than need to be purchased, installed, and trained on...
to the OS built-in utilities and the freely available open source / public domain
variteies.
However, either way you go, be prepared for the requiring learning curve.. along
with the extensive manual process and time required to identify and run the
utilities, before you can capture and begin the extensive correlation process on
the data from several disparate utilities (before you even get to do the analysis
of your findings).
Either approach has it's advantages and disadvantages.. along with their
strengths and weaknesses (3rd party purchased suites might save you time in
graphical aggregation and correlation.. but tend to limit the level of detail and
granularity available vs. what the OS utilities will provide).
The basic list of KEY "built-in" tools historically available for monitoring
performance applies to nearly any Unix/Linux distribution, including the following
partial list of common utilities used ... following the basic breakdown of
computing subsystems :
** CPU / Kernel Utilization :
--> vmstat (vm system cpu and kernel utilization metrics ** a great starting pt
**)
--> mpstat (multi processor .. per cpu performance statistics)
** Memory / Kenel Utilization :
--> vmstat
--> ipcs
--> swap
--> top
** I/O Performance :
--> iostat (Standard IO.. ufs, .. IO performance utility)
--> vxstat (Veritas vxfs filesystem IO performance)
** Network Utilization :
--> netstat
--> ping
--> traceroute
** Process / Kernel :
--> ps
--> top
--> prstat
--> ...
* sar (provides most basic types of high level performance metrics, assuming
that system accounting is turned on, which does incur some level of system
overhead when always running)
SOLARIS 10 ... Above and Beyond other Unix / Linux

Distributions ...
In addition to the basic toolsets available, there exist the following key additions
that Solaris 10 provides, which sets it apart from the other Unix / Linux variants.
** DTrace (Dynamic Tracing via "D" language scripting and probe/providers)
__ Dtrace is the "Electron microscope" of performance analysis for a Solaris 10

system
See the DtraceToolkit for a long list of specific Dtrace scripts (several of which
are used
within sys_diag, among others created)
** lockstat (uses the kernel dtrace infrastructure) Summarizes system

lock/mutex contention
** Mdb (Modular Debugger)
* kstat (Kernel statistics .. counters, etc..)

* cpustat / cputrack (cpu statistics, system-wide or per process)
* intrstat, trapstat (interrupt and system trap, I/DTLB_miss statistics, ..)
* ... & many more.. [this list will be re-done in a future blog with a more
thorough breakdown.. ]
________________________________________________________________
___________________
The Time Saving.. automated nature... of SYS_DIAG :)
Over the past several years, I have created a utility called "sys_diag" that offers
the capability of automatically capturing performance statistics, using nearly all
available system utilities.. and aggregating the data, performing analysis and
HTML report generation of findings. Sys_diag creates a single .tar.Z compressed
archive that can be emailed/ftp'd.. for performing system configuration and/or
performance analysis off-site.. from virtually anywhere.. saving a LOT of time..
not requiring any 3rd party tools or agents to be installed on a system other than
downloading the "sys_diag" ksh script itself (with a color coded dashboard.. and
links to detailed analysis findings). Virtually no learning curve is required for
loading, running, and reflecting basic performance profiling, including high level
subsystem bottlenecks (deeper root cause correlation might require some level
of advanced sys admin knowledge).
Beyond performance analysis, sys_diag can be used to also generate a detailed

configuration snapshot report, including OS, HW, Storage, SW, 3PP configuration
attributes, among several other capabilities that it provides.
** See the next blog entry for more details and examples on sys_diag **.
The published repository and high level description of sys_diag is always
available at BigAdmin using the following URL :
http://www.sun.com/bigadmin/jsp/descFile.jsp?
url=descAll/sys_diag__solaris_c
(Copyright 2007 Todd A. Jobson)

Solution Raidconf

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Solution Raidconf

Uploaded by

Copyright:

Available Formats

Solution Type Technical Instruction

JYBFU5F Internal ID use only.

After creating or deleting a RAID volume on the Sun Fire[TM] T2000

NA8WC3F Internal ID use only.

here is an example of creating and labeling a striped RAID volume:

root@t2000 # raidctl -c -r 0 c3t1d0 c3t2d0 c3t3d0

AVAILABLE DISK SELECTIONS:

Specify disk (enter its number): 1

AVAILABLE DISK SELECTIONS:

The same needs to be done after deleting a volume for Solaris to

Label says 428854496 blocks; Drive says 143374738 blocks

root@t2000 # raidctl -d c3t1d0

AVAILABLE DISK SELECTIONS:

Specify disk (enter its number): 1

AVAILABLE DRIVE TYPES:

AVAILABLE DISK SELECTIONS:

** CPU / Kernel Utilization :

** Memory / Kenel Utilization :

SOLARIS 10 ... Above and Beyond other Unix / Linux

** DTrace (Dynamic Tracing via "D" language scripting and probe/providers)

__ Dtrace is the "Electron microscope" of performance analysis for a Solaris 10

** lockstat (uses the kernel dtrace infrastructure) Summarizes system

** Mdb (Modular Debugger)

* kstat (Kernel statistics .. counters, etc..)

* intrstat, trapstat (interrupt and system trap, I/DTLB_miss statistics, ..)

The Time Saving.. automated nature... of SYS_DIAG :)

Beyond performance analysis, sys_diag can be used to also generate a detailed

(Copyright 2007 Todd A. Jobson)

You might also like