Your message dated Wed, 13 Sep 2006 05:47:06 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#385017: 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.3.git200608202239-2
Severity: normal

While upgrading to this version, I got a debconf message:

    The array you have specified (/dev/md3) 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.

    Please refer to /usr/share/doc/mdadm/README.upgrading-2.5.3.gz if
    you intend to continue.

    Proceed with starting arrays not listed in mdadm.conf?


Firstly, it's not clear where I specified this... I now see (upon manual
inspection of the debconf-show output, which reportbug somehow failed to
obtain) that I at some point apparently had entered it (I can't recall
this, BTW).  Here's the debconf-show output:

$ debconf-show mdadm
debconf: DbDriver "passwords" warning: could not open
/var/cache/debconf/passwords.dat: Permission denied
* mdadm/autostart: false
  mdadm/autocheck: true
* mdadm/warning:
  mdadm/mail_to: root
  mdadm/initrdstart: /dev/md3
  mdadm/start_daemon: true

I have all my md components tagged as linux raid-autodetect, and hence
they're started automagically by the kernel (my self-compiled kernel of
course) at boottime.

Perhaps the /proc/cmdline info could be queried? Mine contains:
    root=/dev/md3 ro vga=6
No hint of an initrd there.

Anyway: I answered "No" to the question.

Additionally the further output is a bit confusing:

    W: unable to determine MD arrays needed for boot.
    W: falling back to starting all of them...
    Starting MD monitoring service: mdadm --monitor.
    Assembling MD arrays...done (disabled in /etc/default/mdadm).

As the assembling is disabled, why first say you're going to assemble...
and then say "done".


Thanks,
Paul Slootman

-- Package-specific info:
--- mount output
/dev/md3 on / type ext3 (rw)
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)
/dev/md1 on /boot type ext2 (rw)
/dev/mapper/vg0- [deleted]
nfsd on /proc/fs/nfsd type nfsd (rw)

--- mdadm.conf
DEVICE partitions
MAILADDR root

--- /proc/mdstat:
Personalities : [raid1] [raid5] [raid4] 
md1 : active raid1 sdc1[2] sdb1[1] sda1[0]
      248896 blocks [3/3] [UUU]
      
md2 : active raid5 sdc2[2] sdb2[1] sda2[0]
      3919616 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
      
md3 : active raid5 sdc3[2] sdb3[1] sda3[0]
      5879552 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
      
md4 : active raid5 sdc4[2] sdb4[1] sda4[0]
      614839552 blocks level 5, 64k chunk, algorithm 0 [3/3] [UUU]
      
unused devices: <none>

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

   8     0  312571224 sda
   8     1     248976 sda1
   8     2    1959930 sda2
   8     3    2939895 sda3
   8     4  307419840 sda4
   8    16  312571224 sdb
   8    17     248976 sdb1
   8    18    1959930 sdb2
   8    19    2939895 sdb3
   8    20  307419840 sdb4
   8    32  312571224 sdc
   8    33     248976 sdc1
   8    34    1959930 sdc2
   8    35    2939895 sdc3
   8    36  307419840 sdc4
   9     4  614839552 md4
   9     3    5879552 md3
   9     2    3919616 md2
   9     1     248896 md1
 253     0    4194304 dm-0
 253     1    6291456 dm-1
 253     2   33554432 dm-2
 253     3   83886080 dm-3
 253     4  104857600 dm-4
 253     5  125829120 dm-5
 253     6   52428800 dm-6
 253     7    5242880 dm-7
 253     8   72351744 dm-8
 253     9    5242880 dm-9
 253    10   52428800 dm-10
 253    11  120954880 dm-11
   8    64    1004800 sde
   8    65    2009478 sde1

--- initrd.img-2.6.17-rc5:

--- /proc/modules:

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (650, 'testing'), (625, 'stable'), (600, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-rc5
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ANSI_X3.4-1968) (ignored: LC_ALL 
set to C)

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

Versions of packages mdadm recommends:
ii  exim4-daemon-heavy [mail-tran 4.62-1     exim MTA (v4) daemon with extended

-- debconf-show failed


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

Reply via email to