Bug#434138: mdadm fails to assemble arrays on system boot

Eric Lauriault eric at linux.ca
Sat Jul 21 20:34:04 UTC 2007


Package: mdadm
Version: 2.6.2-2
Severity: important
Tags: patch



-- Package-specific info:
--- mount output
/dev/md1 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/md0 on /boot type ext3 (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)

--- mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR xortex at elvira

# definitions of existing MD arrays
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=9e079472:2d36e892:7162d9ad:12f46be2
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=9aeb215f:9b1b51bc:7162d9ad:12f46be2


--- /proc/mdstat:
Personalities : [raid1] 
md1 : active raid1 sdb2[0] sda2[1]
      16901056 blocks [2/2] [UU]
      
md0 : active raid1 sdb1[0] sda1[1]
      97216 blocks [2/2] [UU]
      
unused devices: <none>

--- /proc/partitions:
major minor  #blocks  name

   8     0   17782540 sda
   8     1      97280 sda1
   8     2   16901120 sda2
   8     3   17781760 sda3
   8     4     783360 sda4
   8    16   17782540 sdb
   8    17      97280 sdb1
   8    18   16901120 sdb2
   8    19   17781760 sdb3
   8    20     783360 sdb4
   9     0      97216 md0
   9     1   16901056 md1

--- initrd.img-2.6.21-2-sparc64-smp:
31359 blocks
etc/mdadm
etc/mdadm/mdadm.conf
lib/modules/2.6.21-2-sparc64-smp/kernel/drivers/md/md-mod.ko
lib/modules/2.6.21-2-sparc64-smp/kernel/drivers/md/raid1.ko
lib/modules/2.6.21-2-sparc64-smp/kernel/drivers/md/linear.ko
lib/modules/2.6.21-2-sparc64-smp/kernel/drivers/md/multipath.ko
lib/modules/2.6.21-2-sparc64-smp/kernel/drivers/md/raid0.ko
lib/modules/2.6.21-2-sparc64-smp/kernel/drivers/md/xor.ko
lib/modules/2.6.21-2-sparc64-smp/kernel/drivers/md/raid456.ko
lib/modules/2.6.21-2-sparc64-smp/kernel/drivers/md/raid10.ko
sbin/mdadm
scripts/local-top/mdadm

--- /proc/modules:
dm_snapshot 21504 0 - Live 0x00000000100fc000
dm_mirror 26352 0 - Live 0x00000000100f2000
dm_mod 65944 2 dm_snapshot,dm_mirror, Live 0x00000000100de000
raid1 27904 2 - Live 0x000000001006a000
md_mod 93600 4 raid1, Live 0x0000000010050000

--- /var/log/syslog:
Jul 21 15:11:11 elvira kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Jul 21 15:11:11 elvira kernel: md: bitmap version 4.39
Jul 21 15:11:11 elvira kernel: md: raid1 personality registered for level 1
Jul 21 15:11:11 elvira kernel: md: md0 stopped.
Jul 21 15:11:11 elvira kernel: md: bind<sda1>
Jul 21 15:11:11 elvira kernel: md: bind<sdb1>
Jul 21 15:11:11 elvira kernel: md: md1 stopped.
Jul 21 15:11:11 elvira kernel: md: bind<sda2>
Jul 21 15:11:11 elvira kernel: md: bind<sdb2>
Jul 21 15:21:57 elvira kernel: md: raid1 personality registered for level 1
Jul 21 15:21:57 elvira kernel: md: md0 stopped.
Jul 21 15:21:57 elvira kernel: md: bind<sda1>
Jul 21 15:21:57 elvira kernel: md: bind<sdb1>
Jul 21 15:21:57 elvira kernel: md: md1 stopped.
Jul 21 15:21:57 elvira kernel: md: bind<sda2>
Jul 21 15:21:57 elvira kernel: md: bind<sdb2>

--- volume detail:

--- /proc/cmdline
root=/dev/md1 ro md=0,/dev/sda1,/dev/sdb1


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: sparc (sparc64)

Kernel: Linux 2.6.21-2-sparc64-smp (SMP w/1 CPU core)
Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages mdadm depends on:
ii  debconf [debconf-2.0]         1.5.13     Debian configuration management sy
ii  libc6                         2.6-2      GNU C Library: Shared libraries
ii  lsb-base                      3.1-23.1   Linux Standard Base 3.1 init scrip
ii  makedev                       2.3.1-83   creates device files in /dev

Versions of packages mdadm recommends:
ii  module-init-tools            3.3-pre11-4 tools for managing Linux kernel mo
ii  postfix [mail-transport-agen 2.4.3-1     High-performance mail transport ag

-- debconf information:
  mdadm/autostart: true
  mdadm/mail_to: xortex at elvira
  mdadm/initrdstart_msg_errmd:
* mdadm/initrdstart: all
  mdadm/initrdstart_msg_errconf:
  mdadm/initrdstart_notinconf: false
  mdadm/initrdstart_msg_errexist:
  mdadm/initrdstart_msg_intro:
  mdadm/autocheck: true
  mdadm/initrdstart_msg_errblock:
  mdadm/start_daemon: true
-------------- next part --------------
--- /usr/share/initramfs-tools/scripts/local-top/mdadm.orig	2007-07-21 16:32:07.000000000 -0400
+++ /usr/share/initramfs-tools/scripts/local-top/mdadm	2007-07-21 15:15:58.000000000 -0400
@@ -64,6 +64,8 @@
 # handle /dev/md/X nodes
 mkdir --parent /dev/md
 
+sleep 5
+
 CONFIG=/etc/mdadm/mdadm.conf
 # in case the hook failed to install a configuration file, this is our last
 # attempt... the "emergency procedure"... <drumroll>


More information about the pkg-mdadm-devel mailing list