Sponsored Content
Operating Systems Linux Raid0 recovery from external HD Post 302385020 by pludi on Thursday 7th of January 2010 01:18:31 AM
Old 01-07-2010
For this to work you'd need to know the parameters the hardware controller used, or at least the stripe size used. If you can get that it might be possible using dd to create a complete image, and use that to start reconstructing your data.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Password recovery

We recently terminated a developer at my place of employment who created scripts on a windows server (that i do not have access to) that invoke FTP sessions on my UnixWare 7.1.1 servers. I need to know the password that is being used. Does anyone know of a good password crack? (8 Replies)
Discussion started by: rm -r *
8 Replies

2. Solaris

Solaris RAID0 doubt...

friends, Suppose I am typing metastat command and it is showing: d100: Concat/Stripe Size: 369495 blocks (180 MB) Stripe 0: (interlace: 32 blocks) Device Start Block Dbase Reloc c1d0s0 16065 Yes Yes c1d0s1 0 No Yes... (4 Replies)
Discussion started by: saagar
4 Replies

3. Solaris

Solaris recovery

Some thing happened to our solaris 10 ( sparc ) box and it is not coming up now. These are some of the console messages : I assume it is not able to find very basic system libraries so i need to tell it some how to find it under /lib:/usr/lib. I booted it from the CD but now i... (4 Replies)
Discussion started by: rajwinder
4 Replies

4. UNIX for Dummies Questions & Answers

Why is RAID0 faster?

I have read anecdotes about people installing RAID0 (RAID - Wikipedia, the free encyclopedia) on some of their machines because it gives a performance boost. Because bandwidth on the motherboard is limited, can someone explain exactly why it should be faster? (7 Replies)
Discussion started by: figaro
7 Replies

5. UNIX for Advanced & Expert Users

live upgrade with raid0 soft partitions

Hi, I have this mirrored system with soft-partitions. I have a difficulty determining the lucreate cmd in this env. #metastat -p d0 -m d10 d20 1 d10 1 1 c1t2d0s0 d20 1 1 c1t3d0s0 d1 -m d11 d21 1 d11 1 1 c1t2d0s5 d21 1 1 c1t3d0s5 d100 -p d1 -o 58720384 -b 8388608 d200 -p d1 -o... (1 Reply)
Discussion started by: chaandana
1 Replies

6. Hardware

HP9000 Server - Stuck on RAID0

Hey all, I've got an old HP9000 L1000 server with HP-UX installed. The drives that the OS is running on are in RAID0. I am concerned for the reliability of the server. The four hard drives in the front of the server are LVD 18.2 drives. I know with RAID0, if one drive fails, they all fail. ... (2 Replies)
Discussion started by: mroselli
2 Replies

7. Solaris

Cloning RAID0 drives, Solaris 10u11

Hello all, this is my first time posting here. Where I work we have multiple servers (x3-2's) running Solaris 10u11 with 2 drives configured as RAID0, 300GB per. There are 4-6 open slots for drives to clone to. Past attempts to clone/backup these drives has failed. One of the machines is... (1 Reply)
Discussion started by: eprlsguy
1 Replies

8. Gentoo

Data recovery of formatted external HDD

accidentally formatted ext3 external hard disk .. im using EAse us tool in windows system to recover the data ... will this works?? if yes ... the another external hard disk have to be formatted in which file system ? is there any other option ..please help me out (1 Reply)
Discussion started by: rajeshz
1 Replies

9. Solaris

Solaris 11 recovery

Hi, I need to recover the Solaris 11 OS, and it backup via Netbackup 7.6 file level backup only. Does anyone know what are steps to recover it? Thanks. :confused::confused::confused: (3 Replies)
Discussion started by: freshmeat
3 Replies

10. UNIX for Dummies Questions & Answers

Raid0 array stresses only 1 disk out of 3

Hi there, I've setup a raid0 array of 3 identical disks using : mdadm --create --verbose /dev/md0 --level=stripe --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1I'm using dstat to monitor the disk activity : dstat --epoch -D sdb,sdc,sdd --disk-util 30The results show that the stress is not... (8 Replies)
Discussion started by: chebarbudo
8 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 04:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy