Bug#515279: mdadm fails to reassemble RAID1 after upgrade etch->lenny

Sun Feb 15 13:20:02 UTC 2009

Package: mdadm
Version: 2.6.7.2-1
Severity: normal

Hi,

I just upgraded one of my servers from etch to lenny. Everything went well but
the restart. It hung while starting the root-raid1 and couldn't find any raid
devices anymore.

I managed to bring the server back up with bulding the raid with specifying
the partitons.

I see now that if I do a mdadm --examine --scan that it doens't show any
raidsets anymore. If I do a mdadm --examine --scan --config=partitions it
works ok.

root at wkx:~# mdadm --examine --scan
root at wkx:~# mdadm --examine --scan --config=partitions
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=f19f0a12:58279226:0e55279a:bf9f3d58

I am not sure what went wrong here. I'd be very glad if you could help me
here.

thanks
Philipp

-- Package-specific info:
--- mount output
/dev/md0 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/sdb1 on /exchangebackup type ext3 (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 /dev/hd[a-z] /dev/sd*[a-z]

# 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 root

# definitions of existing MD arrays
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=f19f0a12:58279226:0e55279a:bf9f3d58
	devices=/dev/sda1,/dev/sdc1

--- /proc/mdstat:
Personalities : [raid1] 
md0 : active raid1 sda1[0] sdc1[1]
      72605632 blocks [2/2] [UU]

unused devices: <none>

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

   8     0   72613056 sda
   8     1   72605736 sda1
   8    16  293036184 sdb
   8    17  293033601 sdb1
   8    32   72613056 sdc
   8    33   72605736 sdc1
   9     0   72605632 md0

--- initrd.img-2.6.26-1-686:
27838 blocks
etc/mdadm
etc/mdadm/mdadm.conf
lib/modules/2.6.26-1-686/kernel/drivers/md/md-mod.ko
lib/modules/2.6.26-1-686/kernel/drivers/md/raid1.ko
lib/modules/2.6.26-1-686/kernel/drivers/md/linear.ko
lib/modules/2.6.26-1-686/kernel/drivers/md/multipath.ko
lib/modules/2.6.26-1-686/kernel/drivers/md/raid0.ko
lib/modules/2.6.26-1-686/kernel/drivers/md/raid456.ko
lib/modules/2.6.26-1-686/kernel/drivers/md/raid10.ko
sbin/mdadm
scripts/local-top/mdadm

--- /proc/modules:
raid1 18016 1 - Live 0xf881a000
md_mod 67036 2 raid1, Live 0xf882a000

--- /var/log/syslog:
Feb 15 13:04:08 wkx kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Feb 15 13:04:08 wkx kernel: md: bitmap version 4.39
Feb 15 13:04:08 wkx kernel: md: raid1 personality registered for level 1
Feb 15 13:04:08 wkx kernel: md: md0 stopped.
Feb 15 13:04:08 wkx kernel: md: bind<sdc1>
Feb 15 13:04:08 wkx kernel: md: bind<sda1>
Feb 15 13:11:19 wkx kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Feb 15 13:11:19 wkx kernel: md: bitmap version 4.39
Feb 15 13:11:19 wkx kernel: md: raid1 personality registered for level 1
Feb 15 13:11:19 wkx kernel: md: md0 stopped.
Feb 15 13:11:19 wkx kernel: md: bind<sdc1>
Feb 15 13:11:19 wkx kernel: md: bind<sda1>
Feb 15 13:35:37 wkx kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Feb 15 13:35:37 wkx kernel: md: bitmap version 4.39
Feb 15 13:35:37 wkx kernel: md: raid1 personality registered for level 1
Feb 15 13:35:37 wkx kernel: md: md0 stopped.
Feb 15 13:35:37 wkx kernel: md: bind<sdc1>
Feb 15 13:35:37 wkx kernel: md: bind<sda1>
Feb 15 13:40:22 wkx kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Feb 15 13:40:22 wkx kernel: md: bitmap version 4.39
Feb 15 13:40:22 wkx kernel: md: raid1 personality registered for level 1
Feb 15 13:40:22 wkx kernel: md: md0 stopped.
Feb 15 13:40:22 wkx kernel: md: bind<sdc1>
Feb 15 13:40:22 wkx kernel: md: bind<sda1>

--- volume detail:

--- /proc/cmdline
BOOT_IMAGE=.26_PK ro root=900

--- lilo:
lilo.conf file not readable.

-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages mdadm depends on:
ii  debconf                       1.5.24     Debian configuration management sy
ii  libc6                         2.7-18     GNU C Library: Shared libraries
ii  lsb-base                      3.2-20     Linux Standard Base 3.2 init scrip
ii  makedev                       2.3.1-88   creates device files in /dev
ii  udev                          0.125-7    /dev/ and hotplug management daemo

Versions of packages mdadm recommends:
ii  exim4-daemon-heavy [mail-tran 4.69-9     Exim MTA (v4) daemon with extended
ii  module-init-tools             3.4-1      tools for managing Linux kernel mo

mdadm suggests no packages.

-- 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