Your message dated Wed, 13 Sep 2006 05:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#386468: fixed in mdadm 2.5.3.git200608202239-3 has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---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: [EMAIL PROTECTED], [EMAIL PROTECTED] (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
--- End Message ---
--- Begin Message ---Source: mdadm Source-Version: 2.5.3.git200608202239-3 We believe that the bug you reported is fixed in the latest version of mdadm, which is due to be installed in the Debian FTP archive: mdadm-udeb_2.5.3.git200608202239-3_i386.udeb to pool/main/m/mdadm/mdadm-udeb_2.5.3.git200608202239-3_i386.udeb mdadm_2.5.3.git200608202239-3.diff.gz to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-3.diff.gz mdadm_2.5.3.git200608202239-3.dsc to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-3.dsc mdadm_2.5.3.git200608202239-3_i386.deb to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-3_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. martin f. krafft <[EMAIL PROTECTED]> (supplier of updated mdadm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Thu, 7 Sep 2006 14:32:04 +0200 Source: mdadm Binary: mdadm mdadm-udeb Architecture: source i386 Version: 2.5.3.git200608202239-3 Distribution: unstable Urgency: medium Maintainer: Debian mdadm maintainers <[EMAIL PROTECTED]> Changed-By: martin f. krafft <[EMAIL PROTECTED]> Description: mdadm - tool to administer Linux MD arrays (software RAID) mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb) Closes: 384614 384754 385017 385690 385951 385994 386468 387017 Changes: mdadm (2.5.3.git200608202239-3) unstable; urgency=medium . * Urgency medium because of RC bugs. * Add versioned dependency to debconf (closes: #385994); temporary fix until we find a proper fix for #386439. * Add patch by Steinar H. Gunderson to ensure mdadm does not interpret a superblock as belonging to a device when it's actually part of a partition on that device (closes: #385951). * Do not override the superblock default version in mdadm.conf to prevent creation of superblocks that the kernel can't handle (closes: #384614). * Added a note to alert people that the warning about arrays not listed in the configuration file is only relevant if the arrays are needed to be brought up by mdadm from initramfs during boot (closes: #385017). * Added bootloader/cmdline info to bugscript so that future bug reports via bug/reportbug include information on how the system is booted with respect to RAID (the root partition). * If mdadm is being configured in a chroot, it now defaults to starting all arrays from the initial ramdisk, rather than trying to figure out the root MD array (we're using /proc information, so it would be the one of the host, not the one of the chroot) (closes: #386468). * Added LSB headers to init scripts. * Reworked the documentation with respect to the use of "MD" and "RAID", and added a FAQ entry on the meaning of "MD". Thanks to Frans Pop for his help! * Updated debconf translations: - Czech by Miroslav Kure (closes: #384754). - French by Florentin Duneau (closes: #385690). - Russian by Yuri Kozlov (closes: #387017). Files: ab3afa3d115d66238d13f5b59312a123 760 admin optional mdadm_2.5.3.git200608202239-3.dsc c66a67dc5d71ae8b1a99f9ad121718b1 89230 admin optional mdadm_2.5.3.git200608202239-3.diff.gz eff02d5b331491a5e84be2e05ebe1870 198692 admin optional mdadm_2.5.3.git200608202239-3_i386.deb ed4e1efa7c3e782a5f0045d7a9b82324 68348 debian-installer optional mdadm-udeb_2.5.3.git200608202239-3_i386.udeb Package-Type: udeb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFB/WXIgvIgzMMSnURApjdAKCGM7Um0aJpgzXF6CCwLHmBhMEPKgCg0HPu GOzEoOXeoK3R3xbEy3rBxCU= =Ys1W -----END PGP SIGNATURE-----
--- End Message ---
