--- Begin Message ---
Package: mdadm
Version: 1.12.0-1
Severity: normal
*** Please type your report below this line ***
Hi all,
I was using raidtools2 for a while now on my raid5 arrays.
Here is my /etc/raidtab :
####
raiddev /dev/md0
raid-level 5
nr-raid-disks 4
nr-spare-disks 0
persistent-superblock 1
parity-algorithm left-symmetric
chunk-size 32
device /dev/sda1
raid-disk 0
device /dev/sdb1
raid-disk 1
device /dev/sdc1
raid-disk 2
device /dev/sdd1
raid-disk 3
raiddev /dev/md1
raid-level 5
nr-raid-disks 4
nr-spare-disks 0
persistent-superblock 1
parity-algorithm left-symmetric
chunk-size 32
device /dev/sda2
raid-disk 0
device /dev/sdb2
raid-disk 1
device /dev/sdc2
raid-disk 2
device /dev/sdd2
raid-disk 3
raiddev /dev/md2
raid-level 5
nr-raid-disks 4
nr-spare-disks 0
persistent-superblock 1
parity-algorithm left-symmetric
chunk-size 32
device /dev/sda3
raid-disk 0
device /dev/sdb3
raid-disk 1
device /dev/sdc3
raid-disk 2
device /dev/sde3
raid-disk 3
raiddev /dev/md3
raid-level 5
nr-raid-disks 4
nr-spare-disks 0
persistent-superblock 1
parity-algorithm left-symmetric
chunk-size 32
device /dev/sda4
raid-disk 0
device /dev/sdb4
raid-disk 1
device /dev/sdc4
raid-disk 2
device /dev/sdd4
raid-disk 3
#####
Two days ago I run apt-get dist-upgrade, raidtools2 has been removed
from debian. I tried to assemble raid arrays with mdadm but failed. It
seems something is wrong, probably raid5 headers.
Here some information about parts of md0 :
traktopel:/# mdadm -E /dev/sda1
/dev/sda1:
Magic : a92b4efc
Version : 00.90.00
UUID : 7dc1acb8:02c1869a:8e9ab5d5:de61ddfe
Creation Time : Wed Jul 28 01:29:55 2004
Raid Level : raid5
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Update Time : Sun Jan 15 18:03:45 2006
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : 1cefd6eb - correct
Events : 0.7264315
Layout : left-symmetric
Chunk Size : 32K
Number Major Minor RaidDevice State
this 2 8 1 2 active sync /dev/.static/dev/sda1
0 0 8 49 0 active sync /dev/.static/dev/sdd1
1 1 8 17 1 active sync /dev/.static/dev/sdb1
2 2 8 1 2 active sync /dev/.static/dev/sda1
3 3 8 33 3 active sync /dev/.static/dev/sdc1
traktopel:/# mdadm -E /dev/sdb1
/dev/sdb1:
Magic : a92b4efc
Version : 00.90.00
UUID : 7dc1acb8:02c1869a:8e9ab5d5:de61ddfe
Creation Time : Wed Jul 28 01:29:55 2004
Raid Level : raid5
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Update Time : Sun Jan 15 18:03:45 2006
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : 1cefd6eb - correct
Events : 0.7264315
Layout : left-symmetric
Chunk Size : 32K
Number Major Minor RaidDevice State
this 2 8 1 2 active sync
/dev/.static/dev/sda1
0 0 8 49 0 active sync
/dev/.static/dev/sdd1
1 1 8 17 1 active sync
/dev/.static/dev/sdb1
2 2 8 1 2 active sync
/dev/.static/dev/sda1
3 3 8 33 3 active sync
/dev/.static/dev/sdc1
Here the mdadm scan
traktopel:/# mdadm -E --scan
ARRAY /dev/md0 level=raid5 num-devices=4
UUID=7dc1acb8:02c1869a:8e9ab5d5:de61ddf
e
ARRAY /dev/.static/dev/md1 level=raid5 num-devices=4
UUID=e034bf24:f2767c99:de90
1fed:e40ccf76
ARRAY /dev/.static/dev/md2 level=raid5 num-devices=4
UUID=0f6852c5:9faa45c6:a57a
ada6:004b5c70
ARRAY /dev/.static/dev/md3 level=raid5 num-devices=4
UUID=86931930:5a70a39c:dabd
e2d3:5a587303
And Finally here the assembly try :
traktopel:/# mdadm -A /dev/.static/dev/md0 -v
mdadm: looking for devices for /dev/.static/dev/md0
mdadm: /dev/sdf4 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdf3 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdf2 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdf1 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdf is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sde4 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sde3 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sde2 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sde1 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sde is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdd4 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdd3 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdd2 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdd1 is identified as a member of /dev/.static/dev/md0, slot 2.
mdadm: /dev/sdd is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdc4 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdc3 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdc2 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdc1 is identified as a member of /dev/.static/dev/md0, slot 2.
mdadm: /dev/sdc is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdb4 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdb3 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdb2 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sdb1 is identified as a member of /dev/.static/dev/md0, slot 2.
mdadm: /dev/sdb is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sda4 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sda3 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sda2 is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: /dev/sda1 is identified as a member of /dev/.static/dev/md0, slot 2.
mdadm: /dev/sda is not one of /dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1
mdadm: no uptodate device for slot 0 of /dev/.static/dev/md0
mdadm: no uptodate device for slot 1 of /dev/.static/dev/md0
mdadm: no uptodate device for slot 3 of /dev/.static/dev/md0
mdadm: added /dev/sdd1 to /dev/.static/dev/md0 as 2
mdadm: /dev/.static/dev/md0 assembled from 1 drive - not enough to start the
arr
ay.
As you can see all sd[abcd]1 composing md0 are identified as slot 2. I
do think this the problem. What is strange is that mdadm -E /dev/sda1
gives good informations about slots.
So is it a bug ? a raid5 alteration ? something else ?
And how to reassemble my raid ?
Please help.
Thanks.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-k7
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Versions of packages mdadm depends on:
ii debconf [debconf-2.0] 1.4.67 Debian configuration management
sy
ii libc6 2.3.5-11 GNU C Library: Shared libraries
an
ii makedev 2.3.1-79 creates device files in /dev
mdadm recommends no packages.
-- debconf information:
* mdadm/autostart: false
* mdadm/warning:
* mdadm/start_daemon: true
* mdadm/mail_to: djdeath
--
Telefonieren Sie schon oder sparen Sie noch?
NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie
--- End Message ---
signature.asc
