Bug#384222: mdadm: Fails to parse mdadm.conf on upgrade
Gabor Gombas
gombasg at sztaki.hu
Tue Aug 22 18:52:04 UTC 2006
Package: mdadm
Version: 2.5.3.git200608202239-1
Severity: normal
Hi,
When upgrading mdadm, I got the following message:
----->
Configuring mdadm
-----------------
The array you have specified (/dev/md0) is not listed in the configuration file /etc/mdadm/mdadm.conf.
Therefore it cannot be started during boot, unless you correct the configuration file and recreate the
initial ramdisk.
<-----
But md0 _is_ listed in mdadm.conf. Maybe the postinst script is
confused by the multi-line syntax?
Gabor
-- Package-specific info:
--- mdadm.conf
DEVICE partitions
MAILADDR root
# /
ARRAY /dev/md0
level=raid1
num-devices=4
UUID=56b957d9:f9501329:df2509bc:dc8333e1
auto=yes
# /usr
ARRAY /dev/md1
level=raid5
num-devices=4
UUID=6787ec68:3c880a4c:c124f3f1:5e89281d
auto=yes
# /var
ARRAY /dev/md2
level=raid5
num-devices=4
UUID=b6554f20:6c55e676:5c7081ec:b41b1652
auto=yes
# /u
ARRAY /dev/md3
level=raid5
num-devices=4
UUID=0a861bca:55f4db0b:e6996597:fce7720f
auto=yes
--- /proc/mdstat:
Personalities : [raid0] [raid1] [raid10] [raid5] [raid4]
md1 : active raid5 sdd5[2] sdc5[1] sdb5[0] sda5[3]
8795136 blocks level 5, 256k chunk, algorithm 2 [4/4] [UUUU]
md2 : active raid5 sdd6[2] sdc6[1] sdb6[0] sda6[3]
5855232 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
md3 : active raid5 sdd8[2] sdc8[1] sdb8[0] sda8[3]
713815680 blocks level 5, 128k chunk, algorithm 2 [4/4] [UUUU]
md0 : active raid1 sdd1[1] sdc1[0] sdb1[2] sda1[3]
393472 blocks [4/4] [UUUU]
unused devices: <none>
--- /proc/partitions:
major minor #blocks name
8 0 245117376 sda
8 1 393561 sda1
8 2 1 sda2
8 5 2931831 sda5
8 6 1951866 sda6
8 7 979933 sda7
8 8 237938683 sda8
8 16 245117376 sdb
8 17 393561 sdb1
8 18 1 sdb2
8 21 2931831 sdb5
8 22 1951866 sdb6
8 23 979933 sdb7
8 24 237938683 sdb8
8 32 244198584 sdc
8 33 393561 sdc1
8 34 1 sdc2
8 37 2931831 sdc5
8 38 1951866 sdc6
8 39 979933 sdc7
8 40 237938683 sdc8
8 48 244198584 sdd
8 49 393561 sdd1
8 50 1 sdd2
8 53 2931831 sdd5
8 54 1951866 sdd6
8 55 979933 sdd7
8 56 237938683 sdd8
9 0 393472 md0
9 3 713815680 md3
9 2 5855232 md2
9 1 8795136 md1
8 128 19535040 sdi
8 129 19535008 sdi1
--- initrd.img-2.6.17libata:
--- /proc/modules:
dm_snapshot 16672 0 - Live 0xf9b68000
dm_mirror 19664 0 - Live 0xf9b62000
dm_mod 55448 2 dm_snapshot,dm_mirror, Live 0xf9b74000
--- volume detail:
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17libata
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages mdadm depends on:
ii debconf [debconf-2.0] 1.5.3 Debian configuration management sy
ii libc6 2.3.6.ds1-2 GNU C Library: Shared libraries
ii lsb-base 3.1-14 Linux Standard Base 3.1 init scrip
ii makedev 2.3.1-82 creates device files in /dev
Versions of packages mdadm recommends:
ii postfix [mail-transport-agent 2.3.2-1 A high-performance mail transport
-- debconf information:
* mdadm/autostart: true
* mdadm/initrdstart: /dev/md0
mdadm/initrdstart_notinconf: false
mdadm/initrdstart_msg_errexist:
mdadm/initrdstart_msg_intro:
mdadm/initrdstart_msg_errblock:
* mdadm/warning:
* mdadm/start_daemon: true
* mdadm/mail_to: root
mdadm/initrdstart_msg_errmd:
mdadm/initrdstart_msg_errconf:
* mdadm/autocheck: true
More information about the pkg-mdadm-devel
mailing list