Sponsored Content
Operating Systems AIX Power8 S812L:HMC issue and ... Post 302962243 by The Doctor on Thursday 10th of December 2015 09:11:19 AM
Old 12-10-2015
From the Diag utility, I'd expect to see devices behind your SAS RAID controller that look something like:
  • pdisk0 & pdisk1 - for the 2 physical disks.... in 2 slot locations ranging from P2-D1 thru P2-D12
  • hdisk0, hdisk1, hdisk2, hdisk3, etc. - for any logical disks created by the SAS Disk Array Manager
  • OR
  • hdisk0 & hdisk1 - if the disks are configured as the default, regular JBOD
RAID isn't needed. If RAID is not configured, they are just a bunch of disks (JBOD). Look for the RAID Array Manager in your Diag screens.... it will show you if any RAID configuration is present (provided the drives are readable)...... or not.

I find it odd that you would have 2 faulty drives right out of the box.... unless your e-bay supplier knowingly sold it that way. But what do I know ?

I assume you've re-seated the drives & even tried another disk slot ?
This User Gave Thanks to The Doctor For This Post:
 

10 More Discussions You Might Find Interesting

1. AIX

Hmc

Well i am right now working on an IBM P550 risc server with an HMC connected.. The server has 2 logical partitions (Lpar). both lpar is having Aix 5.3 installed. Now I have a doubt.. is it possible to have Aix in one lpar and windows 2003 in another.. cheers Bala (4 Replies)
Discussion started by: balaji_prk
4 Replies

2. AIX

Hmc

Hello everybody, had a question. Iam having a p650 box here, System Model: IBM,7038-6M2 Machine Serial Number: 1078DCC managed system - 1 which has 2 lpars on it i added memory to the box(made sure that memory added was in proper quads and was verified by a CE) after i rebooted the box, the... (4 Replies)
Discussion started by: karthikosu
4 Replies

3. AIX

CDROM Issue on LPAR HMC VIO

Whenever I assign/unassign a CDROM ( RAID CTRL ) to Active LPAR from HMC, I have to reboot the LPAR. How can I do it without rebooting the LPARS. POWER6 with HMC LPARS = AIX 6.1 Any info developerWorks : AIX and UNIX : PowerVM Forum : Moving CD-ROM/DVD-ROM dynamically ... But... (5 Replies)
Discussion started by: filosophizer
5 Replies

4. AIX

AIX and HMC installation issue

I started the AIX install with a fiber channel disk, and let it run: restricted by GSA ADP Schedule Contract with IBM Corp. . . . . . << End of copyright notice for perfagent.tools >>. . . . ... (2 Replies)
Discussion started by: Gideon1a
2 Replies

5. AIX

HMC Commands

Hello All, Can anybody knows a command, what I can check the processes in the HMC restricted shell? :wall: (1 Reply)
Discussion started by: kalaso
1 Replies

6. AIX

[TIP] Migration to POWER8

Read "Migration to POWER8" article to get prepared for migration to POWER8: link removed, advertisement (0 Replies)
Discussion started by: pave01
0 Replies

7. AIX

New IBM Power8 (S822) and StorWiz V3700 SAN, best practices for production setup/config?

Hello, Got a IBM Power8 box (S822) that I am configuring for replacement of our existing IBM machine. Wanted to touch base with the expert community here to ensure I don't miss anything critical in my setup/config of AIX. Did a fresh AIX 7.1 install on the internal scsi hdisk, mirror'ed... (3 Replies)
Discussion started by: c3rb3rus
3 Replies

8. AIX

StorWize v3700 and Power8 (S822) AIX, configuration best practice for LUNs?

Hello, We have an Power8 System (S822) and a IBM StorWize v3700 SAN. The OS is AIX 7.1. With this hardware from what I read I need to download/install special SDDPCM drivers, so I did (SDDPCM VERSION 2.6.6.0 (devices.sddpcm.71.rte). I carved my volumes in the StorWize and presented to... (3 Replies)
Discussion started by: c3rb3rus
3 Replies

9. AIX

HMC in VmWare NIC sl0 issue.

Hi There, First of all I'm new to *nix world, so bear with me and English is not my native tongue :) Now I'm working on the HMC 7.3.3.0 ServPack:0 base_version:20080402.1 to make it work in VmWare (testing in Workstation) I've got HMC installed and realized that network options in GUI... (8 Replies)
Discussion started by: JKat
8 Replies

10. AIX

IBM Power Linux Cluster Fence device on Power8 Platform

wasn't quite sure which forum to post in. What typical fence device to configure for a Power Linux PaceMaker Cluster running on the Power8 Platform (S822 Model of hardware), or what should be ordered with the S822 for use as a Fence Device? (5 Replies)
Discussion started by: mrmurdock
5 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)
All times are GMT -4. The time now is 10:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy