11-25-2014
Hi,
i got this everytime i want to add a disk to the array. Meanwhile i think its a problem with the marvel chipset on the sata controller and perhaps smart. this seems to crash the disks if they under heavy load.
10 More Discussions You Might Find Interesting
1. Programming
Hi,
I am using gmake to compile a c program with a makefile. The make file runs ld. I get the following error
jsh1035c:/users/egate453/admegate/kapil/samples $ gmake -e -f GNUmakefile queue_c
gmake -f ./GNUmakefile queue_c in_objdir=1 build_root=/users/egate453/admegate/kapil/samples... (2 Replies)
Discussion started by: handak9
2 Replies
2. Linux
Hi,
I have a three disk raid 5, with 500GB disks.
This is close to being full, and whilst I can just add another disk and rebuild to add another 500GB, I would prefer to replace with 1TB disks. So i have some questions.
Can I replace these disks one by one with bigger disks? I... (1 Reply)
Discussion started by: snoop2048
1 Replies
3. Virtualization and Cloud Computing
Hello Unix Community:
My task to figure out how to add a 20G volume to an existing EBS Array (RAID0) at AWS.
I haven't been told that growing the existing volumes isn't an option, or adding another larger volume to the existing array is the way to go. The client's existing data-store is... (0 Replies)
Discussion started by: Habitual
0 Replies
4. Emergency UNIX and Linux Support
Hi All
I have a RAID 5 array consisting of 4 drives that had a partial drive failure in one of the drives.
Rebooting shows the faulty drive as background rebuilding and mdadm /dev/ARRAYID shows three drives as in sync with the fourth drive as spare rebuilding.
However the array won't come... (9 Replies)
Discussion started by: Bashingaway
9 Replies
5. UNIX for Advanced & Expert Users
Hello, I have 4 drives (500G each) in a raid 10, I got a power failior and this is the result?
cat /proc/mdstat
Personalities :
md126 : inactive sdb sdc sdd sde
1953536528 blocks super external:-md127/0
md127 : inactive sdd(S) sde(S) sdb(S) sdc(S)
9028 blocks super... (3 Replies)
Discussion started by: rmokros
3 Replies
6. UNIX for Advanced & Expert Users
Hi everyone,
I am not sure if I understand how mdadm --create /dev/md0 --level=container works?
A device called /dev/md0 appears in /proc/mdstat but I am not sure how to use that device?
I have 2 blank drives with 1 500GB partition on each. I would like to setup mirroring, but not in the... (0 Replies)
Discussion started by: hytron
0 Replies
7. Red Hat
had this RHEL 5 installation with /dev/sda1 and /dev/sda2 running..
created two more partitions /dev/sdj1 and /dev/sdj2 , the same sized partition as /dev/sda
trying to use mdadm to create RAID1 ..
I cannot even do it in "rescue" mode, I wonder if it can be done..
it kept... (2 Replies)
Discussion started by: ppchu99
2 Replies
8. UNIX for Dummies Questions & Answers
hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
9. UNIX for Advanced & Expert Users
Hi All,
I have been trying to create a USB RAID 5 using mdadm tool on Joli OS 1.2 (Ubuntu) but with no luck. I cannot even get pass the creation of array device (/dev/md0) and superblock. I am using 3 USB keys (2 16.4 GB kingston and 1 16GB sandisk).
My steps are:
... (5 Replies)
Discussion started by: powelltallen
5 Replies
10. UNIX for Advanced & Expert Users
Hi guys,
I'm new to RAID although I've had a server running raid5 for a while. It was delivered preinstalled like this and I never really wondered how to monitor and maintain it. This quick introduction just to let you understand why I'm such an idiot asking such a silly question.
Now what... (0 Replies)
Discussion started by: chebarbudo
0 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