Bug#386468: mdadm: cannot mount root filesystem after upgrade (system unbootable)

Cyrille Bollu cyrille.bollu at tiscali.be
Thu Sep 7 20:27:44 UTC 2006


Package: mdadm
Version: 2.5.2-7
Followup-For: Bug #383727


Hi,

I've seen quite a few bugs related to this matter on the BTS, and 
have seen that a new version of mdadm is already in unstable, but, 
as none of the bug reported apply exactly to my case, I decided to open 
mine.

HISTORY
-------

As some others, my "Debian testing" doesn't boot since I upgraded a few 
weeks ago.

after rebooting on my "Debian stable" (on the same computer), I saw 
that the upgrade changed the names of my raid arrays. Hopefully, not enough 
to make this distribution unbootable.

So, after a little work, I updated my grub config and rebooted my 
"Debian testing"... But the boot process got stuck "waiting for root 
filesystem".

Back to my "Debian stable", chroot to my "Debian testing", I could 
upgrade it again and see that "mdadm" was complaining a little.

Now, I think I solved it, but it still gets stuck "waiting for root 
filesystem".

CURRENT SITUATION
-----------------

If I wait long enough for the boot process to give up and to give me a 
busybox shell, I see that the /dev/md3 device exists and that all 
required modules (md and raid1) are loaded, but, still, when I try 
"mount /dev/md3 /", I got a very strange error "Invalid argument". 

Second problem, if I run "mdadm --examine --scan", the output gives me 2 
entries for /dev/md4 (I updated manually the mdadm.conf file hereunder 
to leave only 1 entry).

Now, maybe a third problem I'm discovering while writing this report, 
"mount" says that "/dev/md2" is mounted at root...

Well, that's it. I cannot say much more. It seems that my raid setup is 
completly screwed up but it is very difficult for me to debug such a 
problem within a chrooted environment.

Is all this due to an mdadm bug?

Cyrille

-- Package-specific info:
--- mount output
/dev/md2 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev type tmpfs (rw,size=10M,mode=0755)
proc on /proc type proc (rw)
proc on /proc type proc (rw)
proc on /proc type proc (rw)

--- mdadm.conf
DEVICE partitions
ARRAY /dev/md4 level=raid1 num-devices=2 UUID=811eaa24:c9694dbc:5fa24ebc:83dc003d
ARRAY /dev/md5 level=raid1 num-devices=2 UUID=fe7cbc7c:00b73704:1321a79d:dcfcd580
ARRAY /dev/md6 level=raid1 num-devices=2 UUID=aaedc3a2:78e89542:bcc7b974:19ab8fa3
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=c9d8a15d:69fcfbf6:b89fb943:69968fad
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=947adb2e:9b939d79:1998a9c0:14891ae4
ARRAY /dev/md3 level=raid1 num-devices=2 UUID=8ac60f9b:d74f9589:c2bf554b:0cad9b87
MAILADDR root

--- /proc/mdstat:
Personalities : [raid1] 
md6 : active raid1 hda12[0] hdc12[1]
      48130624 blocks [2/2] [UU]
      
md5 : active raid1 hda11[0] hdc11[1]
      6305408 blocks [2/2] [UU]
      
md4 : active raid1 hda10[0] hdc10[1]
      5116544 blocks [2/2] [UU]
      
md3 : active raid1 hda9[0] hdc9[1]
      7678912 blocks [2/2] [UU]
      
md2 : active raid1 hdc7[1]
      3076352 blocks [2/1] [_U]
      
md0 : active raid1 hda5[0] hdc5[1]
      2040128 blocks [2/2] [UU]
      
md1 : active raid1 hda6[0] hdc6[1]
      6650752 blocks [2/2] [UU]
      
unused devices: <none>

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

   3     0  120060864 hda
   3     1     514048 hda1
   3     2          1 hda2
   3     3   39062500 hda3
   3     5    2048256 hda5
   3     6    6650878 hda6
   3     7    3076416 hda7
   3     8     514048 hda8
   3     9    7679038 hda9
   3    10    5116671 hda10
   3    11    6305481 hda11
   3    12   48130708 hda12
  22     0   80043264 hdc
  22     1     514048 hdc1
  22     2          1 hdc2
  22     5    2048256 hdc5
  22     6    6650878 hdc6
  22     7    3076416 hdc7
  22     8     514048 hdc8
  22     9    7679038 hdc9
  22    10    5116671 hdc10
  22    11    6305481 hdc11
  22    12   48130708 hdc12
   9     1    6650752 md1
   9     0    2040128 md0
   9     2    3076352 md2
   9     3    7678912 md3
   9     4    5116544 md4
   9     5    6305408 md5
   9     6   48130624 md6

--- initrd.img-2.6.8-3-686:

--- /proc/modules:
raid1 17856 7 - Live 0xf081c000
md 49832 5 raid1, Live 0xf0825000

--- volume detail:


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-3-686
Locale: LANG=fr_BE at euro, LC_CTYPE=fr_BE at euro (charmap=ISO-8859-15)

Versions of packages mdadm depends on:
ii  debconf [debconf-2.0]        1.5.3       Debian configuration management sy
ii  libc6                        2.3.6.ds1-4 GNU C Library: Shared libraries
ii  lsb-base                     3.1-15      Linux Standard Base 3.1 init scrip
ii  makedev                      2.3.1-82    creates device files in /dev

Versions of packages mdadm recommends:
ii  exim4-daemon-light [mail-tran 4.63-3     lightweight exim MTA (v4) daemon

-- debconf information:
* mdadm/autostart: true
* mdadm/initrdstart: /dev/md3
* mdadm/warning:
* mdadm/start_daemon: true
* mdadm/mail_to: root
* mdadm/autocheck: true




More information about the pkg-mdadm-devel mailing list