9 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
Hello.
I have an export of an associative array build using declare -p SOME_ARRAY_NAME > SOME_FILE_NAME.txt.
Producing some thing like declare -A SOME_ARRAY_NAME=( ="some_text" ="a_text" ......... ="another_text" ) in a text file.
I have a stock of functions which are sourced from... (1 Reply)
Discussion started by: jcdole
1 Replies
2. UNIX for Advanced & Expert Users
Thank you in advanced,
I had a Buffalo DUO crap out on me that was setup as RAID 0. I dont belive it was the drives but rather the controller in the DUO unit. I bought another external HDD enclosure and was able to fireup the two older DUO drives in it and I think I resembled the RAID... (12 Replies)
Discussion started by: metallica1973
12 Replies
3. Shell Programming and Scripting
Hi, I have a problem with awk array when iam trying to use awk in solaris box as below..Iam unable to figure out the problem..
Need your help. is there any alternative to make it in arrays from variable values
nawk 'BEGIN {SUBSEP=" ";
split("101880|110045 101887|110045 101896|110045... (9 Replies)
Discussion started by: cskumar
9 Replies
4. Red Hat
Dear all ,
i ve configured raid 0 in redhat machine(VM ware), by following steps:
#mdadm -C /dev/md0 -l 0 -n 2 /dev/sdb1 /dev/sdc1
#mkfs.ext3 /dev/md0
#mdadm --detail --scan --config=mdadm.conf >/etc/mdadm.conf
then
mounted the/dev/md0 device and also added a entry in fstab.
how... (2 Replies)
Discussion started by: sriniv666
2 Replies
5. Solaris
Hi Peeps,
Can anyone help me an EFI lablel on a 3510 raid array that I cannot get rid of, format -e and label just asks you if you want to label it. Want an SMI label writing to it.
Anyone got any ideas on how to remove the EFI label?
Thanks in advance
Martin (2 Replies)
Discussion started by: callmebob
2 Replies
6. UNIX for Advanced & Expert Users
Hi guys,
i must install an old old old ml370 server...
I must create a RAID 5 with my 4 SCSI disk.
I need a SmartStart disk for create it or a Floppy Disk called "Array configuration Tool". I don't find it on the hp website...:mad::mad::mad:
Anyone have it??
Thanks in advance.
Zio (0 Replies)
Discussion started by: Zio Bill
0 Replies
7. UNIX for Dummies Questions & Answers
Hello,
I have been stuck on this aspect of loading a comma delimited file into an array. I thought i had the syntax right, but my commands are not working the way I want them to. Basically my cut command is splitting the file up by spaces and commas. I want the cut command to ignore white spaces.... (2 Replies)
Discussion started by: grandtheftander
2 Replies
8. AIX
I created a RAID 5 array and when I list out the attributes of the "hdisk" it reports back raid_level = 5 but the RAID level of the array = false. What does this actually indicate about my array? I've never paid much attention to this until now since I have a disk reporting failure I want to make... (0 Replies)
Discussion started by: scottsl
0 Replies
9. UNIX for Advanced & Expert Users
Percent complete SCO 5.0.6 / No longer an issue (0 Replies)
Discussion started by: Henrys
0 Replies
sautil(1M) sautil(1M)
NAME
sautil - support utility for the HP SmartArray RAID controller family
SYNOPSIS
device_file [-N]
device_file [-s]
device_file fw_image
device_file fw_image physical_drive_id
device_file fw_image encl_physical_drive_id
device_file
device_file
device_file
device_file logical_drive_number
device_file rate
device_file
device_file
device_file
device_file [-raw]
device_file
device_file physical_drive_id [-raw]
device_file
device_file
device_file
DESCRIPTION
The command is a support tool for the HP SmartArray RAID Controller Family. This command allows the system administrator to perform tasks
such as:
1) Retrieving RAID configuration and status information for the controller, logical drive, physical disk, cache, etc.;
2) Retrieving RAID driver information (driver state, trace log, statistics, etc.);
3) Downloading new revisions of controller or disk firmware;
4) Sending instructions to the firmware (reset controller, scan SCSI bus, etc.); and
5) Recreating the controller device file(s).
Prerequisites
Some of the options are intended for use by HP support personnel and require detailed knowledge of the RAID SA driver or firmware to inter-
pret the output.
Security Restrictions
requires either the superuser privilege or and privileges. See privileges(5) for more information about privileged access on systems that
support fine-grained privileges.
Options
recognizes the following options and parameters as indicated in the section above. Keyword options are order-dependent, but are not case-
sensitive.
device_file Most options require a device file parameter, e.g., The device file for a specific RAID SA controller can be determined from
the output.
When the device file parameter is specified without any options, will display information such as the RAID SA driver state,
controller hardware path, firmware revision, capacity expansion and rebuild priority settings, cache status and settings,
logical drive configuration and physical drive properties.
When the optional argument is specified, persistent device files (see intro(7)) are displayed for logical drives.
When the optional argument is specified, a subset of the information is displayed.
This option downloads the specified firmware image file
(fw_image) to the controller. The image file name is case-sensitive. The firmware download process usually completes
within one minute, but could theoretically take up to eight minutes. All I/O to the controller are temporarily halted dur-
ing this time.
This option downloads the specified firmware image file
(fw_image) to physical disk specified by the (physical_drive_id). The image file name is case-sensitive.
physical_drive_id
To specify the SCSI physical disk. It can be represented as such as: 4:12. Valid channel numbers are between 1 and 4.
Valid target numbers are between 0 and 15.
To specify the SAS/SATA physical disk. It can be represented as either such as: 2I:1:10 or (wwid), such as:
0x500000e010f16432.
This option downloads the specified firmware image file
(fw_image) to the storage enclosure processor. This option is supported on SAS Smart Array HBAs only. The image file name
is case-sensitive. The firmware download process takes ten to fifteen minutes. All I/O to the controller are temporarily
halted during this time.
encl_physical_drive_id
To specify the storage enclosure processor. It can be represented as either such as: 1E:1:0 or (wwid), such as:
0x500000e010f16432.
This option resets the controller.
Some situations that may require a controller reset are:
1) OLR was performed and the logical drives on the replacement controller are not detected;
2) a disk enclosure with an existing RAID configuration was hot-added and the logical drives on that enclosure are not
detected.
This option tells the controller to rescan all SCSI buses.
A situation that may require a scan is when a physical disk is hot-inserted into the system's internal drive bay.
This option tells the controller to start rebuilding any logical drives that
are in state. All logical drives in this state will eventually transition to Heavy I/O to the controller may delay this
transition. There is no adverse impact if this option is invoked when no logical drives are in state.
This option grants permission to the controller to set the state of the
specified failed logical drive (logical_drive_number) to "OK" and to set the states of all failed physical disks that have
been replaced via hot-plug exchanges to "OK".
WARNING: While this option preserves the RAID configuration (logical drive configurations, controller settings, etc.), data
on the failed logical drive may have already been compromised. If more disks have failed than the RAID level can accommo-
date, you will need to restore your data from backup media.
This option tells the controller to set the SCSI transfer rate to a lower
speed than it would normally allow. Valid arguments for the rate field are (and ultra-160 for controllers that support
Ultra-320).
This option displays statistics counters maintained by the RAID SA "ciss"
driver.
This option clears the statistics counters maintained by the RAID SA "ciss"
driver.
This option displays the trace buffer of the RAID SA "ciss" driver.
This option displays the firmware error log of the RAID SA controller.
When the optional argument is specified, the raw data (in bytes) are displayed.
This option clears the firmware error log of the RAID160 SA controller.
It is not available for SmartArray 640x controllers.
This option displays the error log for the physical disk specified by the
(physical_drive_id). When the optional argument is specified, the raw data (in bytes) are displayed.
This option displays the RAID SA controller's PCI configuration header.
This option allows interactive reading of the RAID SA controller's
registers.
WARNING: Reading an invalid register may cause a system crash.
This option is only available for SAS/SATA.
Vital Product Data contains Product Description, Part Number, Engineering Date Code, Serial Number, Miscellaneous Informa-
tion, Manufacturing Date Code, EFI Version, Asset Tag, HBA Firmware Version, and WWN.
This option runs the RAID SA startup script to recreate the device files
(/dev/cissX).
Logical Drive State Definitions
All physical disks in the logical drive are operational.
Some possible causes:
1) Multiple physical disks in a fault-tolerant (RAID 1, 1+0, 5, ADG) logical drive have failed.
2) One or more disks in a RAID 0 logical drive have failed.
3) Cache data loss has occurred.
4) Array expansion was aborted.
5) The logical drive is temporarily disabled because another logical drive on the controller had a missing disk at power-up.
Also known as "degraded" state. A physical disk in a fault tolerant logical
drive has failed. For RAID 1, 1+0 or 5, data loss may result if a second disk should fail. For RAID ADG, data loss may
result if two additional disks should fail.
A replacement disk is present, but rebuild hasn't started yet (another logical
drive may be currently rebuilding). The logical drive will also return to this state if the rebuild had been aborted due to
unrecoverable read errors from another disk.
One or more physical disks in this logical drive are being rebuilt.
While the logical drive was in a degraded state, the system was powered off
and a disk other than the failed disk was replaced. Shut off the system and replace the correct (failed) disk.
While the system was off, one or more disks were removed. Note: the other
logical drives are held in a temporary "failed" state when this occurs.
The data in the logical drive is being reorganized because:
1) Physical disks have been added to the array (capacity expansion).
2) The stripe size is being changed (stripe-size migration).
3) The RAID level is being changed (RAID-level migration).
A capacity expansion operation is in progress (or is queued up) that will make
room on the disks for this new logical drive. Until room has been made on the physical disks, this newly configured logical
drive cannot be read or written.
The logical drive is waiting to undergo data reorganization (see
above). Possible causes for the delay are a rebuild or expansion operation may already be in progress.
Physical Disk State Definitions
The physical disk is configured in one or more logical drives and is
operational.
The physical disk is configured as a spare disk.
The physical disk has not been configured in any logical drives.
The configured physical disk has failed.
RETURN VALUE
returns the following values:
Successful completion.
Command line syntax error.
Incompatible CISS driver API.
Failure opening a file.
Other error.
EXAMPLES
Display RAID subsystem information for the controller
Update the firmware on the controller using the firmware image file
Update the firmware on the physical disk (SCSI ID "13") connected to channel "2" of controller using the firmware image file located in the
current directory:
Recreate the device files for all RAID SA controllers in the system:
AUTHOR
was developed by HP.
FILES
Executable file.
Device files.
SEE ALSO
saconfig(1M), privileges(5), intro(7).
sautil(1M)