Sponsored Content
Homework and Emergencies Emergency UNIX and Linux Support Loading a RAID array after OS crash Post 302438454 by CRGreathouse on Monday 19th of July 2010 08:04:45 PM
Old 07-19-2010
Loading a RAID array after OS crash

One of my very old drive farm servers had an OS fault and can't boot now but I'd like to restore some files from it. I tried booting Ubuntu from a CD, but it couldn't see the drives -- possibly because they're RAIDed together. Is there a good way to get at my files?

The data in question is a series of old genotyping arrays (basically extremely high-res photos and some associated data files). The RAID level is just 1+0, I think. My predecessor's notes say that the system was Debian Sarge, but I think it's actually some version of Xubuntu (the OS was probably upgraded without the notes being changed). I have all the passwords as well as physical access to the system, but I don't know much about the original setup (it was all 'the last guy').

Any help would be appreciated. I don't think the lab would be willing to pay for a hard drive restoration service (16 RAID drives would presumably be fairly expensive), but anything short of that may be fair game.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Percent complete error while scanning RAID array during 5.0.6 load

Percent complete SCO 5.0.6 / No longer an issue (0 Replies)
Discussion started by: Henrys
0 Replies

2. AIX

RAID level of array = false?

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

3. UNIX for Dummies Questions & Answers

Loading a comma Delimited file into an Array

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

4. UNIX for Advanced & Expert Users

Create RAID - Smart Array Tool - ML370

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

5. Solaris

EFI Disk labels on 3510 raid array

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. Red Hat

missing raid array after reboot

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

7. Shell Programming and Scripting

Problem with awk array when loading from shell variable

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

8. UNIX for Advanced & Expert Users

Revive RAID 0 Array From Buffalo Duo NAS

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

9. UNIX for Beginners Questions & Answers

Loading associative array from exported function

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
saconfig(1M)															      saconfig(1M)

NAME
saconfig - Command Line Configuration Utility for the HP SmartArray RAID Controller Family SYNOPSIS
<device_file> <device_file> -N <device_file> -R <RAID_level> [-S <stripe_size>] -p <physical_drive_id> [-p <physical_drive_id> ...] [-s <physical_drive_id>] [-c <capac- ity>] <device_file> -e <low|medium|high> <device_file> -r <low|medium|high> <device_file> -P <default|shortest|longest> <device_file> -A <logical_drive_num> -s <physical_drive_id> <device_file> -D <logical_drive_num> -s <physical_drive_id> <device_file> -D <logical_drive_num> -s all <device_file> -D <logical_drive_num> <device_file> -D all <device_file> -C <read_caching_percentage> <device_file> -F on <device_file> -F off <device_file> -I -p <physical_drive_id> [-p <physical_drive_id> ...] <device_file> -I -l <logical_drive_num> <device_file> -E <logical_drive_num> -c <capacity> <device_file> -E <logical_drive_num> -p <physical_drive_id> [-p <physical_drive_id> ...] <device_file> -M <logical_drive_num> -R <RAID_level> [-S <stripe_size>] <device_file> -M <logical_drive_num> -S <stripe_size> DESCRIPTION
The command is a command line configuration tool for the HP SmartArray RAID Controller Family. This command provides the ability to create a logical drive, add a spare drive to existing logical drive, display configuration, delete a logical drive, and clear configuration. This command also enables the cache when it is used to create the first logical drive on the SmartArray RAID Controller. Furthermore it allows the option of changing the percentage of total cache size used for read caching and write caching. The auto-fail missing disks at boot fea- ture can be enabled or disabled using this command. Prerequisites needs to be able to create the /tmp/saconfig.lock file when it starts executing. This prevents multiple users from running This lock file is removed when exits. 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 SYNOPSIS section above. <device_file> To specify the device file for the SmartArray RAID Controller. The device file is as displayed by the command for the appropriate SmartArray RAID Controller. With no other options, displays size and status for all physical drives and RAID level, size, and status for all logical drives. With the option saconfig displays size and status for all physical drives and RAID level, size, and status for all logical drives. But the persistent device files (see intro(7)) will be displayed as against legacy device files in the absence of this option. -R <RAID_level> To create a logical drive with the specified RAID level. The supported RAID levels are 0, 1, 1+0, 5, and ADG. The lowest logical drive number not already in use will be given to the newly created logical drive, starting from 0. To determine the hardware path and device file for the logical drive, use the command. The logical drives are dis- played in the same order as in the output. RAID 1+0 logical drive requires even number of physical drives (minimum of 2). To achieve optimal fault tolerance, it is best to specify the same number of physical drives per channel if possible when creating a RAID 1+0 logical drive. This ensures the physical drives in each mirrored pairs would be on different channels. -S <stripe_size> To specify the stripe size for the logical drive to be created. The supported stripe sizes are 8, 16, 32, 64, 128, and 256 (KB). 128 and 256 stripe sizes are not available for RAID 5 or ADG logical drive. If this option is not used to specify the stripe size, default stripe size will be used to create the logical drive. For RAID 0 and 1+0 logical drive, the default size is 128. For RAID 5 and ADG logical drive, the default size is 16. -p <physical_drive_id> To specify the SCSI physical disk. It can be represented as <channel_id>:<target_id> (e.g., 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 <connector>:<enclosure>:<bay> (e.g., 2I:1:10) or <wwid> (e.g., 0x500000e010f16432). -s <physical_drive_id> To specify a spare drive to be included in the logical drive configuration. Refer <physical_drive_id> to -p option. -c <capacity> To specify the size in GB of a logical drive to be created. -A <logical_drive_num> To specify which logical drive to add spare drive to. -e <low | medium | high> To change the expand priority of controller to one of Low, Medium, High. When there are no logical drives, expand priority cannot be changed. When the configuration is cleared, or the last logical drive is deleted, the subse- quent logical drive creation will change the expand priority value of the controller to medium. -r <low | medium | high> To change the rebuild priority of controller to one of Low, Medium, High. When there are no logical drives, rebuild priority cannot be changed. When the configuration is cleared, or the last logical drive is deleted, the subsequent logical drive creation will change the rebuild priority value of the controller to high. -P <default | shortest | longest> To change the path selection method by the controller firmware. If it is set to default, firmware will select the Active path on its own. If the selection method is set to shortest, firmware will select the shortest path as the Active Path. If the path selection method is longest, firmware will select the longest path as the Active Path. All multi path configurations are Active-Standby configurations. -D <logical_drive_num> -s <physical_drive_id> To delete the spare drive from the specified logical drive. -D <logical_drive_num> -s all To delete all of spare drives from the specified logical drive. -D <logical_drive_num> To delete the specified logical drive. -D all To clear configuration. -C <read_caching_percentage> To specify the percentage of total cache size to be used for read caching. The remaining percentage will be used for write caching. Valid read caching percentage numbers are 0, 25, 50, 75, and 100 (%). -F on To enable auto-fail missing disks at boot feature. -F off To disable auto-fail missing disks at boot feature. -I -p <physical_drive_id> [-p <physical_drive_id> ...] To identify SAS/SATA physical drive(s) by LED. -I -l <logical_drive_num> To identify a SAS/SATA logical drive by LED. -E <logical_drive_num> -c <capacity> To extend the capacity of the specified logical drive up to larger capacity. The capacity is in GB. -E <logical_drive_num> -p <physical_drive_id> [-p <physical_drive_id> ...] To expand the specified logical drive and others in an array by physical drive(s). -M <logical_drive_num> -R <RAID_level> [-S <stripe_size>] To perform RAID level [with stripe size] migration on the specified logical drive. The stripe size is in KB. -M <logical_drive_num> -S <stripe_size> To perform stripe size migration on the specified logical drive. The stripe size is in KB. Logical Drive State Definitions All physical disks in the logical drive are operational. Some possible causes: Multiple physical disks in a fault-tolerant (RAID 1, 1+0, 5, ADG) logical drive have failed. One or more disks in a RAID 0 logical drive have failed. Cache data loss has occurred. Array expansion was aborted. 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: Physical disks have been added to the array (capacity expansion). The stripe size is being changed (stripe-size migration). 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 EXPANDING 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 To display configuration on the SmartArray RAID Controller /dev/ciss5 - To create a RAID 1+0 logical drive to include physical drives 4:0 and 4:1 and spare drive 4:2 - -R -p -p -s To create a RAID ADG logical drive with stripe size 64 to include physical drives 1:2, 2:2, 3:2 and 4:2 - -R -S -p -p -p -p To create a RAID 5 logical drive with capacity 45 GB to include SAS physical drives 1I:1:16, 1I:1:15, and 1I:1:14 - -R -c -p -p -p To set the expand priority of logical drives on a controller to medium -e To set the rebuild priority of logical drives on a controller to high -r To add spare drive 1:0 to logical drive 1 - -A -s To delete spare drive 1:0 from logical drive 1 - -D -s To delete all spare drives from logical drive 1 - -D -s To delete logical drive 0 - -D To clear configuration - -D To change read caching percentage to 75% - -C To extend logical drive 2 upto 45 GB in capacity - -E -c To expand logical drive 0 with 2 SAS physical drives - -E -p -p To migrate logical drive 2 with stripe 32 - -M -S To migrate logical drive 2 to RAID level 5 with stripe 64 - -M -R -S AUTHOR
was developed by HP. FILES
Executable file. saconfig lock file. Device files. SEE ALSO
sautil(1M), privileges(5), intro(7). saconfig(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