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
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
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
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
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
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
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
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
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
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
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
BIO(4) BSD Kernel Interfaces Manual BIO(4)
NAME
bio -- Block IO ioctl tunnel pseudo-device
SYNOPSIS
pseudo-device bio
DESCRIPTION
The bio driver provides userland applications ioctl(2) access to devices otherwise not found as /dev nodes. The /dev/bio device node oper-
ates by delegating ioctl calls to a requested device driver. Only drivers which have registered with the bio device can be accessed via this
interface.
The following device drivers register with bio for volume management:
arcmsr(4) Areca Technology Corporation SATA RAID controller
cac(4) Compaq RAID array controller
ciss(4) Compaq Smart ARRAY 5/6 SAS/SATA/SCSI RAID controller
mfi(4) LSI Logic & Dell MegaRAID SAS RAID controller
The following ioctl calls apply to the bio device:
BIOCLOCATE Locate a named device and give back a cookie to the application for subsequent ioctl calls. The cookie is used to tunnel
further ioctls to the right device.
BIOCINQ Retrieve number of volumes and physical disks for a specific device.
BIOCDISK Retrieve detailed information for the specified physical disk. Information returned can include status, size, channel,
target, lun, vendor name, serial number, and processor device (ses).
BIOCDISK_NOVOL Is just the same as BIOCDISK but doesn't require the disks to be in volume sets, so this applies to any physical disk con-
nected to the controller.
Note: this ioctl might not be supported on all hardware.
BIOCVOL Retrieve detailed information for the specified volume. Information returned can include status, size, RAID level, number
of disks, device name association (sd?) and vendor name.
BIOCALARM Control the alarm beeper on the device. Supported states are: disable alarm, enable alarm, silence alarm, status and test
alarm.
Note: These options might not be supported on all hardware.
BIOCBLINK Blink an LED of the specified physical disk. Supported blink states are: blink LED, unblink LED and blink alarm LED.
Note: This option is only supported if the disk is governed by ses(4) and the hardware supports hardware blinking.
BIOCSETSTATE Alter the state of specified physical disk. Supported states are: create/remove hot-spare, create/remove pass through
disk, start/stop consistency check in a volume, online disk and offline disk.
Note: These options might not be supported on all hardware.
BIOCVOLOPS For operations in volume sets. It's able to create and remove a volume set in a supported RAID controller.
Note: this ioctl might not be supported on all hardware.
FILES
/dev/bio ioctl tunnel device
SEE ALSO
ioctl(2), bioctl(8)
HISTORY
The bio driver first appeared in OpenBSD 3.2 and NetBSD 4.0.
AUTHORS
The bio driver was written by Niklas Hallqvist <niklas@openbsd.org>. The API was written by Marco Peereboom <marco@openbsd.org> and was
extended even more for NetBSD by Juan Romero Pardines <xtraeme@netbsd.org>.
BSD
May 25, 2008 BSD