Your message dated Wed, 27 Jan 2010 10:09:01 +0000
with message-id <[email protected]>
and subject line Bug#549083: fixed in mdadm 3.1.1-1
has caused the Debian Bug report #549083,
regarding mdadm: metadata=1 problems with initramfs
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
549083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549083
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mdadm
Version: 2.5.6-9
Severity: normal


I created my md RAID1 arrays with the Knoppix 5.3 mdadm.
Unfortunately, this creates --metadata=1.0 arrays by default (although
its docs say that 0.90 is the default), which led to trouble with LILO
(LILO understands only 0.90 RAIDs, so I had to recreate the /boot
device) and to the problem reported here.  I then copied my existing
Debian system onto the devices, and installed mdadm, which created the
following mdadm.conf automatically:

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

# definitions of existing MD arrays
ARRAY /dev/md0 level=raid1 num-devices=2 
UUID=c7cbc2ed:d3588b4c:10e5f891:5873cf48
ARRAY /dev/md1 level=raid1 metadata=1 num-devices=2 
UUID=96af1b1dc7:e76499d5:9948635b:17bd73 name='c8':1
ARRAY /dev/md2 level=raid1 metadata=1 num-devices=2 
UUID=2473df0404:071747e8:67967c27:560ec4 name='c8':2
ARRAY /dev/md3 level=raid1 metadata=1 num-devices=2 
UUID=55bda5cd26:8fdbd256:0497e87f:8bbf44 name='c8':3
ARRAY /dev/md4 level=raid1 metadata=1 num-devices=2 
UUID=60e4df589f:bf2b134a:2a0c6921:e70d17 name='c8':4

# This file was auto-generated on Wed, 11 Jun 2008 23:22:53 +0200
# by mkconf $Id: mkconf 261 2006-11-09 13:32:35Z madduck $
---------------------------

After these ARRAY lines were integrated into the initramfs, only
/dev/md0 was assembled in the initrd stage of booting, so I did not
get a root file system etc.  I eventually solved the problem by
leaving away the metadata and name columns of the ARRAY lines (see the
mdadm.conf below for the result), but I think that the mkconf script
should create the ARRAY lines in a format that the local-top/mdadm
script understands.

- anton

-- 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/md2 on /home type ext3 (rw)
/dev/md3 on /usr/local 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 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 root

# definitions of existing MD arrays
ARRAY /dev/md0 level=raid1 num-devices=2 
UUID=c7cbc2ed:d3588b4c:10e5f891:5873cf48
ARRAY /dev/md1 level=raid1 num-devices=2 
UUID=96af1b1dc7:e76499d5:9948635b:17bd73
ARRAY /dev/md2 level=raid1 num-devices=2 
UUID=2473df0404:071747e8:67967c27:560ec4
ARRAY /dev/md3 level=raid1 num-devices=2 
UUID=55bda5cd26:8fdbd256:0497e87f:8bbf44
ARRAY /dev/md4 level=raid1 num-devices=2 
UUID=60e4df589f:bf2b134a:2a0c6921:e70d17


--- /proc/mdstat:
Personalities : [raid1] 
md4 : active raid1 sda9[0] sdb9[1]
      15631140 blocks super 1.0 [2/2] [UU]
      
md3 : active raid1 sda7[0] sdb7[1]
      16008668 blocks super 1.0 [2/2] [UU]
      
md2 : active raid1 sda6[0] sdb6[1]
      128005816 blocks super 1.0 [2/2] [UU]
      
md1 : active raid1 sda5[0] sdb5[1]
      16008668 blocks super 1.0 [2/2] [UU]
      
md0 : active raid1 sda3[0] sdb3[1]
      473792 blocks [2/2] [UU]
      
unused devices: <none>

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

   1     0      65536 ram0
   1     1      65536 ram1
   1     2      65536 ram2
   1     3      65536 ram3
   1     4      65536 ram4
   1     5      65536 ram5
   1     6      65536 ram6
   1     7      65536 ram7
   1     8      65536 ram8
   1     9      65536 ram9
   1    10      65536 ram10
   1    11      65536 ram11
   1    12      65536 ram12
   1    13      65536 ram13
   1    14      65536 ram14
   1    15      65536 ram15
   8     0  732574584 sda
   8     1   20482843 sda1
   8     2  127556100 sda2
   8     3     473917 sda3
   8     4          1 sda4
   8     5   16008741 sda5
   8     6  128005888 sda6
   8     7   16008741 sda7
   8     8    4008186 sda8
   8     9   15631213 sda9
   8    16  732574584 sdb
   8    17   20482843 sdb1
   8    18  127556100 sdb2
   8    19     473917 sdb3
   8    20          1 sdb4
   8    21   16008741 sdb5
   8    22  128005888 sdb6
   8    23   16008741 sdb7
   8    24    4008186 sdb8
   8    25   15631213 sdb9
   9     0     473792 md0
   9     1   16008668 md1
   9     2  128005816 md2
   9     3   16008668 md3
   9     4   15631140 md4

--- initrd.img-2.6.25.6-perfctr:

--- /proc/modules:
dm_snapshot 22600 0 - Live 0xffffffff8821e000
dm_mirror 32004 0 - Live 0xffffffff88215000
dm_mod 68920 2 dm_snapshot,dm_mirror, Live 0xffffffff88203000

--- volume detail:

--- /proc/cmdline
BOOT_IMAGE=etch-2.6.25.6p ro root=901

--- lilo:
root=/dev/md1


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable'), (99, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.25.6-perfctr
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

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

Versions of packages mdadm recommends:
ii  exim4-daemon-light [mail-tran 4.63-17    lightweight exim MTA (v4) daemon
ii  module-init-tools             3.3-pre4-2 tools for managing Linux kernel mo

-- debconf information:
* mdadm/autostart: true
* mdadm/mail_to: root
  mdadm/initrdstart_msg_errmd:
* mdadm/initrdstart: /dev/md1
  mdadm/initrdstart_msg_errconf:
* mdadm/initrdstart_notinconf: true
  mdadm/initrdstart_msg_errexist:
  mdadm/initrdstart_msg_intro:
* mdadm/autocheck: false
  mdadm/initrdstart_msg_errblock:
* mdadm/start_daemon: false



--- End Message ---
--- Begin Message ---
Source: mdadm
Source-Version: 3.1.1-1

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_3.1.1-1_amd64.udeb
  to main/m/mdadm/mdadm-udeb_3.1.1-1_amd64.udeb
mdadm_3.1.1-1.debian.tar.gz
  to main/m/mdadm/mdadm_3.1.1-1.debian.tar.gz
mdadm_3.1.1-1.dsc
  to main/m/mdadm/mdadm_3.1.1-1.dsc
mdadm_3.1.1-1_amd64.deb
  to main/m/mdadm/mdadm_3.1.1-1_amd64.deb
mdadm_3.1.1.orig.tar.bz2
  to main/m/mdadm/mdadm_3.1.1.orig.tar.bz2



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

Format: 1.8
Date: Wed, 27 Jan 2010 10:14:25 +1300
Source: mdadm
Binary: mdadm mdadm-udeb
Architecture: source amd64
Version: 3.1.1-1
Distribution: unstable
Urgency: low
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: 539103 544558 549083 558823
Changes: 
 mdadm (3.1.1-1) unstable; urgency=low
 .
   * New upstream release.
   * Retire fixed/blkid-dev branch.
   * Reword warning about unbootable system when mdadm is purged
     (closes: #544558).
   * Updated FAQ to include s2ram as one of the reasons that can prevent an
     array from being stopped; thanks to Pascal Hambourg for writing in.
   * Install udev rules into udeb package (closes: #558823).
   * Update mdadd.sh (formerly /usr/share/doc/mdadm/examples/newdisk.gz) from
     Arno's website, refactoring the script into its own branch/patch
     (closes: #539103).
   * Do not single-quote homehost in initramfs script (closes: #549083).
Checksums-Sha1: 
 a46eb43b086abd6b7f39d52e39e69f343b1a206c 1264 mdadm_3.1.1-1.dsc
 8902fd57eeb416455182bf0627a808275c5183ba 270338 mdadm_3.1.1.orig.tar.bz2
 8a5690b6694f4ac15cfa9f7af4a581ffa70428f9 130649 mdadm_3.1.1-1.debian.tar.gz
 ef3008337863daed2d6831a940f50d2d5014867f 443322 mdadm_3.1.1-1_amd64.deb
 f78984080dacfa99116e861e2b6543d6a5ccc594 142072 mdadm-udeb_3.1.1-1_amd64.udeb
Checksums-Sha256: 
 170a8b5df6f572370186de7a9029880f7b252a1d0099499242854460af4e0d1d 1264 
mdadm_3.1.1-1.dsc
 31c0d3040774283b1e1fad7830cef53a3b89087b2021ec108696a7fad0eb005e 270338 
mdadm_3.1.1.orig.tar.bz2
 4fc26fa6a22c48274b2ad3c84d007d7beca01626093e187a911a932a91bf6c83 130649 
mdadm_3.1.1-1.debian.tar.gz
 de60e1b356d9097fd2db3ceac61cc18f8a7afe21b7342350ea1810305a6b7c8c 443322 
mdadm_3.1.1-1_amd64.deb
 53c04d0600e72f02b77f3613a09f1936bbe0a1d08aff6f4006034ae7cd800f9b 142072 
mdadm-udeb_3.1.1-1_amd64.udeb
Files: 
 b5bfd366c92372625a9d0f513effdd18 1264 admin optional mdadm_3.1.1-1.dsc
 4fd8e375a2ee314becd3196c1a250d98 270338 admin optional mdadm_3.1.1.orig.tar.bz2
 4decd460d2cd8146bf3926d276fe427f 130649 admin optional 
mdadm_3.1.1-1.debian.tar.gz
 e5236180008c66690c26671050e7b737 443322 admin optional mdadm_3.1.1-1_amd64.deb
 ccaf00bb6250c97c4ccb8365aad813ce 142072 debian-installer optional 
mdadm-udeb_3.1.1-1_amd64.udeb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEAREDAAYFAktfmjsACgkQIgvIgzMMSnWR+QCfSkAXCXMLRiofpqNznyG7EEyi
5/8An3YARsAmOkRpSk03x9y+ddiAYN9y
=LCh+
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to