09-26-2012
Hi Lem,
Thanks so much. I did not mount them, however I just unmounted them as you said and there was very good progress. Though it does not seem to complete the array creation as there is a problem with one or 2 disks [UU_].
See outputs below:
root@gokopjolicloud:~# umount /dev/sdb1 |
root@gokopjolicloud:~# umount /dev/sdc1 |
root@gokopjolicloud:~# umount /dev/sdd1 |
root@gokopjolicloud:~# mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 /dev/sd[bcd]1 --auto=md |
mdadm: layout defaults to left-symmetric |
mdadm: chunk size defaults to 64K |
mdadm: size set to 15633280K |
mdadm: largest drive (/dev/sdb1) exceed size (15633280K) by more than 1% |
Continue creating array? y |
mdadm: array /dev/md0 started. |
root@gokopjolicloud:~# cat /proc/mdstat |
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] |
md0 : active raid5 sdd1[3] sdc1[1] sdb1[0] |
31266560 blocks level 5, 64k chunk, algorithm 2 [3/2] [UU_] |
[>....................] recovery = 0.1% (23520/15633280) finish=534.0min speed=486K/sec |
|
unused devices: <none> |
You have mail in /var/mail/root |
root@gokopjolicloud:~# mdadm --examine /dev/md0 |
mdadm: No md superblock detected on /dev/md0. |
root@gokopjolicloud:~# mdadm --detail /dev/md0 |
/dev/md0: |
Version : 00.90 |
Creation Time : Wed Sep 26 16:05:30 2012 |
Raid Level : raid5 |
Array Size : 31266560 (29.82 GiB 32.02 GB) |
Used Dev Size : 15633280 (14.91 GiB 16.01 GB) |
Raid Devices : 3 |
Total Devices : 3 |
Preferred Minor : 0 |
Persistence : Superblock is persistent |
Update Time : Wed Sep 26 16:05:33 2012 |
State : clean, degraded, recovering |
Active Devices : 2 |
Working Devices : 3 |
Failed Devices : 0 |
Spare Devices : 1 |
Layout : left-symmetric |
Chunk Size : 64K |
Rebuild Status : 0% complete |
UUID : 0e6fee1c:4a05e886:b1380be4:00007494 (local to host gokopjolicloud) |
Events : 0.2 |
Number Major Minor RaidDevice State |
0 8 17 0 active sync /dev/sdb1 |
1 8 33 1 active sync /dev/sdc1 |
3 8 49 2 spare rebuilding /dev/sdd1 |
Regards
Powell
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I setup a RAID 5 with 5 drives, one failed, hardware failure so I physically removed it from the raid after powering the machine off then powered it back on and my raid was still good but no 5th drive. I built a 5th drive from scratch and added it in the raid thinking the raid would go into... (0 Replies)
Discussion started by: lacakid
0 Replies
2. Ubuntu
Hey Guys
I have an Ubuntu CD and I was thinking of creating like a bootable hard drive with various OS so that I can just boot OSs with t drive and not require the CDs. I was just wondering is there a way I can do this, like have Ubuntu boot from a USB stick? If yes how is that possible(even if I... (3 Replies)
Discussion started by: rbansal2
3 Replies
3. Solaris
Hi all,
First post so be gentile :)
It's my first time installing Solaris on T2000 server.
I have 2 72GB HD's on it.
After configuring HW raid and running raidctl command I get this output:
bash-3.00# raidctl -l c0t0d0
Volume Size Stripe Status Cache RAID
... (2 Replies)
Discussion started by: Obi-Wan
2 Replies
4. Hardware
Hi,
We have a Sunfire 4150 with On-Board Internal Raid Controller connected to 4 X 146 GB SAS disks.
This also has an External Raid Controller (Storagetek Eight-Port, External HBA
Model SG-XPCIESAS-R-EXT-Z) connected to a JBOD array ( Storagetek XTA2530 ) which has 5 X 300 GB Hard disk.
... (1 Reply)
Discussion started by: ranjansukumar
1 Replies
5. Ubuntu
Hi,
I need to override ioctl operation for a few USB drivers (sierra, option, cdc-acm) on Linux Ubuntu 2.6.34sb2 to support TIOCOUTQ command.
Unfortunately, none of the drivers I mentioned above support TIOCOUTQ because it seems unclear to know amount of data inside a modem.
Does Linux... (12 Replies)
Discussion started by: SDoroshenko
12 Replies
6. Ubuntu
I am trying to dual boot on an external USB 500GB drive using my laptop.I have Windows 7 installed and booting on 1st partition 230GB now as active primary, 2nd partition is 100GB as primary, and 3rd partition is 135GB as primary. I was intending on installing Ubuntu onto the 2nd partition. I read... (12 Replies)
Discussion started by: coolecho
12 Replies
7. Ubuntu
Hello all,
I am looking for a way to copy the existing Ubuntu server 12.04 to a USB (with all the packages and such) and make it boot from the USB.
I have seen other threads about copying the CD image to the USB, which is not exactly I am looking for.
Before I start diving into anything I... (4 Replies)
Discussion started by: br1an
4 Replies
8. Ubuntu
I'd like to install the OS on my stick. I would like to be able to save my works there and install apps or customize the OS.
What can I do
Ps. At home I use an iMac, but in the school where I work there are only PC...
Ty (2 Replies)
Discussion started by: Fabio_Puricelli
2 Replies
9. 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
LEARN ABOUT REDHAT
mdadm.conf
MDADM.CONF(5) File Formats Manual MDADM.CONF(5)
NAME
mdadm.conf - configuration for management of Software Raid with mdadm
SYNOPSIS
/etc/mdadm.conf
DESCRIPTION
mdadm is a tool for creating, managing, and monitoring RAID devices using the md driver in Linux.
Some common tasks, such as assembling all arrays, can be simplified by describing the devices and arrays in this configuration file.
SYNTAX
The file should be seen as a collection of words separated by white space (space, tab, or newline). Any word that beings with a hash sign
(#) starts a comment and that word together with the remainder of the line is ignored.
Any line that starts with white space (space or tab) is treated as though it were a continuation of the previous line.
Empty lines are ignored, but otherwise each (non continuation) line must start with a keyword as listed below. The keywords are case
insensitive and can be abbreviated to 3 characters.
The keywords are:
DEVICE A device line lists the devices (whole devices or partitions) that might contain a component of an MD array. When looking for the
components of an array, mdadm will scan these devices (or any devices listed on the command line).
The device line may contain a number of different devices (separated by spaces) and each device name can contain wild cards as
defined by glob(7).
Also, there may be several device lines present in the file.
For example:
DEVICE /dev/hda* /dev/hdc*
DEV /dev/sd*
DEVICE /dev/discs/disc*/disc
ARRAY The ARRAY lines identify actual arrays. The second word on the line should be the name of the device where the array is normally
assembled, such as /dev/md1. Subsequent words identify the array, or identify the array as a member of a group. If multiple identi-
ties are given, then a component device must match ALL identities to be considered a match. Each identity word has a tag, and
equals sign, and some value. The tags are:
uuid= The value should be a 128 bit uuid in hexadecimal, with punctuation interspersed if desired. This must match the uuid stored in
the superblock.
super-minor=
The value is an integer which indicates the minor number that was stored in the superblock when the array was created. When an
array is created as /dev/mdX, then the minor number X is stored.
devices=
The value is a comma separated list of device names. Precisely these devices will be used to assemble the array. Note that the
devices listed there must also be listed on a DEVICE line.
level= The value is a raid level. This is not normally used to identify an array, but is supported so that the output of
mdadm --examine --scan
can be use directly in the configuration file.
num-devices=
The value is the number of devices in a complete active array. As with level= this is mainly for compatibility with the output
of
mdadm --examine --scan.
spare-group=
The value is a textual name for a group of arrays. All arrays with the same spare-group name are considered to be part of the
same group. The significance of a group of arrays is that mdadm will, when monitoring the arrays, move a spare drive from one
array in a group to another array in that group if the first array had a failed or missing drive but no spare.
MAILADDR
The mailaddr line gives an E-mail address that alerts should be sent to when is running in --monitor mode (and was given the --scan
option). There should only be one MAILADDR line and it should have only one address.
PROGRAM
The program line gives the name of a program to be run when mdadm --monitor detects potentially interesting events on any of the
arrays that it is monitoring. This program gets run with two or three arguments, they being the Event, the md device, and possibly
the related component device.
There should only be one program line and it should be give only one program.
EXAMPLE
DEVICE /dev/sd[bcdjkl]1
DEVICE /dev/hda1 /dev/hdb1
# /dev/md0 is known by it's UID.
ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
# /dev/md1 contains all devices with a minor number of
# 1 in the superblock.
ARRAY /dev/md1 superminor=1
# /dev/md2 is made from precisey these two devices
ARRAY /dev/md2 devices=/dev/hda1,/dev/hda2
# /dev/md4 and /dev/md5 are a spare-group and spares
# can be moved between them
ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df
spare-group=group1
ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977
spare-group=group1
MAILADDR root@mydomain.tld
PROGRAM /usr/sbin/handle-mdadm-events
SEE ALSO
mdadm(8), md(4).
MDADM.CONF(5)