mdadm --examine /dev/sdX1:
[hannes@hannes-pc ~]$ sudo mdadm --examine /dev/sdb1
[sudo] Passwort für hannes:
/dev/sdb1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 98dd94ed:3c274d90:692d310b:eafeb147
Name : hannes-pc:0 (local to host hannes-pc)
Creation Time : Fri Nov 14 15:05:27 2014
Raid Level : raid5
Raid Devices : 3
Avail Dev Size : 3906560143 (1862.79 GiB 2000.16 GB)
Array Size : 3906560000 (3725.59 GiB 4000.32 GB)
Used Dev Size : 3906560000 (1862.79 GiB 2000.16 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=143 sectors
State : clean
Device UUID : 6966a6df:8d55c0d2:631480cb:b7a2780f
Internal Bitmap : 8 sectors from superblock
Update Time : Wed Jun 3 16:56:57 2015
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : 61765fea - correct
Events : 30828
Layout : left-symmetric
Chunk Size : 256K
Device Role : Active device 0
Array State : AAA ('A' == active, '.' == missing, 'R' == replacing)
[hannes@hannes-pc ~]$ sudo mdadm --examine /dev/sdc1
/dev/sdc1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 98dd94ed:3c274d90:692d310b:eafeb147
Name : hannes-pc:0 (local to host hannes-pc)
Creation Time : Fri Nov 14 15:05:27 2014
Raid Level : raid5
Raid Devices : 3
Avail Dev Size : 3906560143 (1862.79 GiB 2000.16 GB)
Array Size : 3906560000 (3725.59 GiB 4000.32 GB)
Used Dev Size : 3906560000 (1862.79 GiB 2000.16 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=143 sectors
State : clean
Device UUID : 45e0ce01:637e7f94:ca8751e4:8798efe5
Internal Bitmap : 8 sectors from superblock
Update Time : Wed Jun 3 16:57:53 2015
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : 34a66c0c - correct
Events : 30828
Layout : left-symmetric
Chunk Size : 256K
Device Role : Active device 1
Array State : AAA ('A' == active, '.' == missing, 'R' == replacing)
[hannes@hannes-pc ~]$ sudo mdadm --examine /dev/sdd1
/dev/sdd1:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x1
Array UUID : 98dd94ed:3c274d90:692d310b:eafeb147
Name : hannes-pc:0 (local to host hannes-pc)
Creation Time : Fri Nov 14 15:05:27 2014
Raid Level : raid5
Raid Devices : 3
Avail Dev Size : 3906560143 (1862.79 GiB 2000.16 GB)
Array Size : 3906560000 (3725.59 GiB 4000.32 GB)
Used Dev Size : 3906560000 (1862.79 GiB 2000.16 GB)
Data Offset : 262144 sectors
Super Offset : 8 sectors
Unused Space : before=262056 sectors, after=143 sectors
State : clean
Device UUID : ca51ddfe:9006161a:0ed80d9d:27026964
Internal Bitmap : 8 sectors from superblock
Update Time : Wed Jun 3 16:58:03 2015
Bad Block Log : 512 entries available at offset 72 sectors
Checksum : ee811fad - correct
Events : 30828
Layout : left-symmetric
Chunk Size : 256K
Device Role : Active device 2
Array State : AAA ('A' == active, '.' == missing, 'R' == replacing)
mdadm.conf:
# mdadm configuration file
#
# mdadm will function properly without the use of a configuration file,
# but this file is useful for keeping track of arrays and member disks.
# In general, a mdadm.conf file is created, and updated, after arrays
# are created. This is the opposite behavior of /etc/raidtab which is
# created prior to array construction.
#
#
# the config file takes two types of lines:
#
# DEVICE lines specify a list of devices of where to look for
# potential member disks
#
# ARRAY lines specify information about how to identify arrays so
# so that they can be activated
#
# You can have more than one device line and use wild cards. The first
# example includes SCSI the first partition of SCSI disks /dev/sdb,
# /dev/sdc, /dev/sdd, /dev/sdj, /dev/sdk, and /dev/sdl. The second
# line looks for array slices on IDE disks.
#
#DEVICE /dev/sd[bcdjkl]1
#DEVICE /dev/hda1 /dev/hdb1
#
# The designation "partitions" will scan all partitions found in
# /proc/partitions
DEVICE partitions
# ARRAY lines specify an array to assemble and a method of identification.
# Arrays can currently be identified by using a UUID, superblock minor number,
# or a listing of devices.
#
# super-minor is usually the minor number of the metadevice
# UUID is the Universally Unique Identifier for the array
# Each can be obtained using
#
# mdadm -D <md>
#
# To capture the UUIDs for all your RAID arrays to this file, run these:
# to get a list of running arrays:
# # mdadm -D --scan >>/etc/mdadm.conf
# to get a list from superblocks:
# # mdadm -E --scan >>/etc/mdadm.conf
#
#ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371
#ARRAY /dev/md1 super-minor=1
#ARRAY /dev/md2 devices=/dev/hda1,/dev/hdb1
#
# ARRAY lines can also specify a "spare-group" for each array. mdadm --monitor
# will then move a spare between arrays in a spare-group if one array has a
# failed drive but no spare
#ARRAY /dev/md4 uuid=b23f3c6d:aec43a9f:fd65db85:369432df spare-group=group1
#ARRAY /dev/md5 uuid=19464854:03f71b1b:e0df2edd:246cc977 spare-group=group1
#
# When used in --follow (aka --monitor) mode, mdadm needs a
# mail address and/or a program. To start mdadm's monitor mode, enable
# mdadm.service in systemd.
#
# If the lines are not found, mdadm will exit quietly
MAILADDR xxxx@gmail.com
#PROGRAM /usr/bin/sendmail
#PROGRAM /usr/sbin/handle-mdadm-events
ARRAY /dev/md0 metadata=1.2 spares=1 name=hannes-pc:0 UUID=98dd94ed:3c274d90:692d310b:eafeb147
Die letzte Zeile in der mdadm.conf könnte es dann vielleicht sein... Was ist mit metadata und name? spares muss sicher raus, ich weiß auch nicht wo ich die Zeile so her habe..