01-21-2014
Just going to follow up with what I did in hopes it helps someone else who has this issue arise.
Use diag command to check array and find failed disk(s).
# diag
---> Task Selection
---> RAID Array Manager
---> PCI-X SCSI Disk Array Manager
---> List PCI-X SCSI Disk Array Configuration
---> sisioa1 Available 06-08 PCI-X Dual Channel U320 SCSI RAID
Activate the LED indicator of the physical disk to locate it on the rack.
# diag
---> Task Selection
---> Hot Plug Task
---> SCSI and SCSI RAID Hot Plug Manager
---> Replace/Remove a Device Attached to an SCSI Hot Swap Enclosure
---> select failed disk here(pdisk#)
A message will appear in regards to an LED and Remove state. Find the physical drive that is now flashing amber from its LED and remove it from the array. After you remove the failed physical drive, replace it with the new unit.
Hit Enter on that message screen to remove that slot from the "remove state".
# diag
---> Task Selection
---> Hot Plug Task
---> SCSI and SCSI RAID Hot Plug Manager
---> Configure Added/Replaced Devices
# diag
---> Task Selection
---> Log Repair Action (Select affected disk)
Rebuild the array
# diag
---> Task Selection
---> RAID Array Manager
---> PCI-X SCSI Disk Array Manager
---> Reconstruct a PCI-X SCSI Disk Array
These 2 Users Gave Thanks to mpeter05 For This Post:
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
AIX 4.3.3
I am investigating methods of creating system backups. One method I am investigating is installing a hot swap hard drive and creating a mksysb to that hard drive. Does anyone have any ideas on getting this accomplished? I am thinking that I need a mounted file system from the 2nd... (0 Replies)
Discussion started by: jalburger
0 Replies
2. UNIX for Advanced & Expert Users
Hey everyone,
first of all, this is the motherboard I have: GigaByte GA-K8NXP-9 , nForce4 Ultra. It supports RAID 0, 1, 0+1 apparently both on the IDE and S-ATA HDD.
Now what I had in mind is popping 2 x 6Gb HDD in the IDE slots as slave 1 & 2 where my 2 DVD/CD burners are master. I then plan... (2 Replies)
Discussion started by: temba
2 Replies
3. UNIX for Dummies Questions & Answers
How do you view Drive/RAID configuration in UNIX?
We are running an ML370 with 6 drives in it...
Version: Sco 5.2.0
Sco Openserver Release 5 (2 Replies)
Discussion started by: bpoulson
2 Replies
4. OS X (Apple)
I am trying to recover data off a drive that failed in my iMac. Apple returned the drive to me and I purchased a hard drive enclosure. I have been doing research on prices for data recovery services, way too expensive. I seen some links using Unix DD commands in the terminal none of which worked.... (6 Replies)
Discussion started by: KJ1906
6 Replies
5. UNIX for Dummies Questions & Answers
Hello,
I have a machine that has software based RAID. One of the hard drives failed. The problem is that the old systems administrator created LVM and then RAID. My understanding is that RAID had to be created before and then the LVM's. Is there someway to install the new drive without loosing... (2 Replies)
Discussion started by: mojoman
2 Replies
6. Hardware
Hey All,
Im using Fedora 2.6 (which is cannot be changed for compatibility reasons).
I cloned a drive from a different server and when i added this drive to a new box, during startup it hangs on "Configuring Kernel Parameters:"
Is there any way to bypass this process and still boot... (0 Replies)
Discussion started by: robfwauk
0 Replies
7. Hardware
I am having trouble connecting my 4TB G-Raid Hard drive to my Compaq Hp laptop can anyone tell me how or what I need in order to connect the 4T and getting it working. (10 Replies)
Discussion started by: Jake Wolf
10 Replies
8. SCO
Our tape drive died and I installed a newer Quantum DAT72 drive in it's place with the same SCSI ID. It still works, but with one major flaw, the system will lock up if I try to upgrade BackupEDGE or view NFS settings in scoadmin.
I get a Transition to ready failure on ha=0* message when the... (4 Replies)
Discussion started by: psytropic
4 Replies
9. UNIX for Advanced & Expert Users
Good Evening,
2 years ago, I set up an Ubuntu file-server for a friend, who is a photograph amateur. Basically, the server offers a software RAID-5 that can be accessed remotely from a MAC. Unfortunately, I didn't labeled the hard drives (i.e. which physical drive corresponds to the /dev/sdX... (2 Replies)
Discussion started by: Loic Domaigne
2 Replies
10. Filesystems, Disks and Memory
I found out that the raid 1 was degraded:
# cat /proc/mdstat
Personalities :
md3 : active raid1 sda5 sdb5
1822445428 blocks super 1.0
md2 : active raid1 sda3(F) sdb3
1073741688 blocks super 1.0
md1 : active raid1 sda2 sdb2
524276 blocks super 1.0
md0 : active raid1 sda1... (0 Replies)
Discussion started by: ZaNaToS
0 Replies
HPSA(4) Linux Programmer's Manual HPSA(4)
NAME
hpsa - HP Smart Array SCSI driver
SYNOPSIS
modprobe hpsa [ hpsa_allow_any=1 ]
DESCRIPTION
hpsa is a SCSI driver for HP Smart Array RAID controllers.
Options
hpsa_allow_any=1: This option allows the driver to attempt to operate on any HP Smart Array hardware RAID controller, even if it is not
explicitly known to the driver. This allows newer hardware to work with older drivers. Typically this is used to allow installation of
operating systems from media that predates the RAID controller, though it may also be used to enable hpsa to drive older controllers that
would normally be handled by the cciss(4) driver. These older boards have not been tested and are not supported with hpsa, and cciss(4)
should still be used for these.
Supported hardware
The hpsa driver supports the following Smart Array boards:
Smart Array P700M
Smart Array P212
Smart Array P410
Smart Array P410i
Smart Array P411
Smart Array P812
Smart Array P712m
Smart Array P711m
StorageWorks P1210m
Configuration details
To configure HP Smart Array controllers, use the HP Array Configuration Utility (either hpacuxe(8) or hpacucli(8)) or the Offline ROM-based
Configuration Utility (ORCA) run from the Smart Array's option ROM at boot time.
FILES
Device nodes
Logical drives are accessed via the SCSI disk driver (sd(4)), tape drives via the SCSI tape driver (st(4)), and the RAID controller via the
SCSI generic driver (sg(4)), with device nodes named /dev/sd*, /dev/st*, and /dev/sg*, respectively.
HPSA-specific host attribute files in /sys
/sys/class/scsi_host/host*/rescan
This is a write-only attribute. Writing to this attribute will cause the driver to scan for new, changed, or removed devices (e.g,.
hot-plugged tape drives, or newly configured or deleted logical drives, etc.) and notify the SCSI midlayer of any changes detected.
Normally a rescan is triggered automatically by HP's Array Configuration Utility (either the GUI or the command-line variety); thus,
for logical drive changes, the user should not normally have to use this attribute. This attribute may be useful when hot plugging
devices like tape drives, or entire storage boxes containing preconfigured logical drives.
/sys/class/scsi_host/host*/firmware_revision
This attribute contains the firmware version of the Smart Array.
For example:
# cd /sys/class/scsi_host/host4
# cat firmware_revision
7.14
HPSA-specific disk attribute files in /sys
/sys/class/scsi_disk/c:b:t:l/device/unique_id
This attribute contains a 32 hex-digit unique ID for each logical drive.
For example:
# cd /sys/class/scsi_disk/4:0:0:0/device
# cat unique_id
600508B1001044395355323037570F77
/sys/class/scsi_disk/c:b:t:l/device/raid_level
This attribute contains the RAID level of each logical drive.
For example:
# cd /sys/class/scsi_disk/4:0:0:0/device
# cat raid_level
RAID 0
/sys/class/scsi_disk/c:b:t:l/device/lunid
This attribute contains the 16 hex-digit (8 byte) LUN ID by which a logical drive or physical device can be addressed. c:b:t:l are
the controller, bus, target, and lun of the device.
For example:
# cd /sys/class/scsi_disk/4:0:0:0/device
# cat lunid
0x0000004000000000
Supported ioctl() operations
For compatibility with applications written for the cciss(4) driver, many, but not all of the ioctls supported by the cciss(4) driver are
also supported by the hpsa driver. The data structures used by these ioctls are described in the Linux kernel source file
include/linux/cciss_ioctl.h.
CCISS_DEREGDISK, CCISS_REGNEWDISK, CCISS_REGNEWD
These three ioctls all do exactly the same thing, which is to cause the driver to rescan for new devices. This does exactly the
same thing as writing to the hpsa-specific host "rescan" attribute.
CCISS_GETPCIINFO
Returns PCI domain, bus, device and function and "board ID" (PCI subsystem ID).
CCISS_GETDRIVVER
Returns driver version in three bytes encoded as:
(major_version << 16) | (minor_version << 8) |
(subminor_version)
CCISS_PASSTHRU, CCISS_BIG_PASSTHRU
Allows "BMIC" and "CISS" commands to be passed through to the Smart Array. These are used extensively by the HP Array Configuration
Utility, SNMP storage agents, and so on. See cciss_vol_status at <http://cciss.sf.net> for some examples.
SEE ALSO
cciss(4), sd(4), st(4), cciss_vol_status(8), hpacucli(8), hpacuxe(8),
<http://cciss.sf.net>, and Documentation/scsi/hpsa.txt and Documentation/ABI/testing/sysfs-bus-pci-devices-cciss in the Linux kernel source
tree
Linux 2012-08-05 HPSA(4)