Your message dated Sun, 20 Aug 2006 17:02:13 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#382450: fixed in mdadm 2.5.3.git200608202239-1 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-10 Severity: normal Hi Martin, I am running a LVM on RAID setup for some time now and never had any problems. Yesterday I upgraded mdadm and today my system would not boot anymore. After some research I found out that /dev/md0 and /dev/md1 magically disappeared which was the reason why lvm could not activate my volume group called "raid" which is located there. The system still locates md0 and md1 fine during boot (I am booting from md0, which is also a raid1). However, according to lvmdiskscan it does not see md1 anymore. I know that it would probably work fine if mdadm would activate the arrays but I think my setup is just as valid. In it, mdadm is used exclusively for checking if anything is wrong with the arrays. Looking at #381181, I'd say that this is really a bug in initramfs as it should compare devices via the major and minor numbers and not just using theirs paths. Your mileage may vary ;) Greetings, Torsten -- Package-specific info: --- mount output /dev/md0 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) /dev/mapper/raid-usr on /usr type xfs (rw) /dev/mapper/raid-var on /var type ext3 (rw) /dev/mapper/raid-cache on /var/cache type ext3 (rw) /dev/mapper/raid-home on /home type xfs (rw) /dev/mapper/raid-backup on /backup type xfs (rw) /dev/mapper/raid-mirror on /home/torsten/mirror type ext3 (rw) tmpfs on /dev type tmpfs (rw,size=10M,mode=0755) stargate:/home on /mnt/stargate type nfs (rw,addr=192.168.2.1) stargate:/music on /music type nfs (rw,addr=192.168.2.1) nfsd on /proc/fs/nfsd type nfsd (rw) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) --- mdadm.conf DEVICE partitions ARRAY /dev/.static/dev/md0 level=raid1 num-devices=2 UUID=3e30ef63:0c27f545:cd3840a6:d20fc5b6 ARRAY /dev/.static/dev/md1 level=raid1 num-devices=2 UUID=c0bf03b8:63dd5a05:9fa2ce57:c2b0ec92 MAILADDR root --- /proc/mdstat: Personalities : [raid1] md1 : active raid1 sdc4[1] sdb4[0] 280326144 blocks [2/2] [UU] md0 : active raid1 sdc1[1] sdb1[0] 2931712 blocks [2/2] [UU] unused devices: <none> --- /proc/partitions: major minor #blocks name 3 0 40209120 hda 3 1 2000061 hda1 3 2 2000092 hda2 3 3 36202477 hda3 8 16 312567413 sdb 8 17 2931831 sdb1 8 18 14651280 sdb2 8 19 14651280 sdb3 8 20 280326217 sdb4 8 32 312567413 sdc 8 33 2931831 sdc1 8 34 14651280 sdc2 8 35 14651280 sdc3 8 36 280326217 sdc4 9 0 2931712 md0 9 1 280326144 md1 253 0 26214400 dm-0 253 1 3145728 dm-1 253 2 2097152 dm-2 253 3 409600 dm-3 253 4 409600 dm-4 253 5 1048576 dm-5 253 6 10485760 dm-6 253 7 3145728 dm-7 253 8 5242880 dm-8 253 9 73400320 dm-9 253 10 78643200 dm-10 253 11 2097152 dm-11 253 12 52428800 dm-12 --- initrd.img-2.6.18-rc3: --- /proc/modules: -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-rc3 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages mdadm depends on: ii debconf [debconf-2.0] 1.5.3 Debian configuration management sy ii libc6 2.3.6-18 GNU C Library: Shared libraries ii lsb-base 3.1-12 Linux Standard Base 3.1 init scrip ii makedev 2.3.1-82 creates device files in /dev Versions of packages mdadm recommends: ii exim [mail-transport-agent] 3.36-18.1 An obsolete MTA (Mail Transport Ag -- debconf information: * mdadm/autostart: true mdadm/initrdstart: /dev/md0 * mdadm/warning: mdadm/start_daemon: true mdadm/mail_to: root mdadm/autocheck: true
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---Source: mdadm Source-Version: 2.5.3.git200608202239-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_2.5.3.git200608202239-1_i386.udeb to pool/main/m/mdadm/mdadm-udeb_2.5.3.git200608202239-1_i386.udeb mdadm_2.5.3.git200608202239-1.diff.gz to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1.diff.gz mdadm_2.5.3.git200608202239-1.dsc to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1.dsc mdadm_2.5.3.git200608202239-1_i386.deb to pool/main/m/mdadm/mdadm_2.5.3.git200608202239-1_i386.deb mdadm_2.5.3.git200608202239.orig.tar.gz to pool/main/m/mdadm/mdadm_2.5.3.git200608202239.orig.tar.gz 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: Mon, 21 Aug 2006 00:25:22 +0100 Source: mdadm Binary: mdadm mdadm-udeb Architecture: source i386 Version: 2.5.3.git200608202239-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: 381057 381303 382263 382389 382450 382480 382876 383688 383806 383891 Changes: mdadm (2.5.3.git200608202239-1) unstable; urgency=low . * Tracking upstream git releases. - now the --run switch behaves as stated in the manpage. This properly fixes #287415 - new version-1 partitionable arrays are now named X instead of _dX (e.g. 0 instead of _d0) for device names like md_dX. I actually think this is a bug and hope upstream will use dX (e.g. d0) instead in a future version. - we specify --symlink=no and thus disable the new feature to create /dev/mdX symlinks to /dev/md/X devices until the entire device node mess is cleared up. No need to introduce yet another complicating factor at this stage. * Instead of trying to do a whole lot of magic with respect to detecting RAID devices to start, mdadm from now on requires a valid mdadm.conf file to be installed. It still tries to do what it can, but there are no heuristics anymore. See /usr/share/doc/mdadm/README.upgrading-2.5.3 . * Removed the zero-superblock warning because we require the user to sign off the configuration file anyway. * This also enables us to use mdadm.conf from the initial ramdisk and thus closes: #381303. * In case the user chooses to assemble all arrays from the initial ramdisk, use the new homehost feature of mdadm (closes: #381057). This will start only those arrays belonging to the local system, unless it is the first run on a system, in which case it will start all arrays and mark them as belonging to the local system. * Improved the debconf control script: integrated error messages into the frontends, and made it a bit smarter. Error messages can now be translated, and the script checks whether the user's choice is listed in the configuration file and only proceeds if it is, or the user chooses to ignore that it is not. * mkconf can now take a generate/force-generate parameter to write directly to /etc/mdadm/mdadm.conf. A second parameter specifies an alternate filename. * mkconf now outputs comments for the settings it suggests. * Removed all udev-related stuff. We must coexist with udev because there are setups that assemble arrays without mdadm, so the device nodes must be created by udev, if that is used. (closes: #382263, #382450, #383688, #383891, #383806, #382480) Staying at low urgency since these (RC) bugs only exist in unstable. * Now installs MD modules and mdadm/mdrun into initial ramdisk regardless of whether the hook script thinks there are devices to start. This was done to enable recovery from the initramfs shell. * Now uses 'MD' instead of 'RAID' consistently in all messages. * Now rebuilds initramfs for all installed kernels. * Now breaks the endless config loop only when the user does not see the question (see #381284, #381007). * Don't fail mdadm-raid when /dev is on a read-only filesystem (closes: #382876). * Updated debconf translations: - French by Florentin Duneau (closes: #382389). Files: 4b7ff47f67a0cb0b3e304de701a95d5d 760 admin optional mdadm_2.5.3.git200608202239-1.dsc 8006fce30bdac088dfb396410428377b 176469 admin optional mdadm_2.5.3.git200608202239.orig.tar.gz 11e33373fcaf6439cf70cf4c25d6a7d2 84117 admin optional mdadm_2.5.3.git200608202239-1.diff.gz 40fa2bfdc60770eb1f0e58105bcd6b24 194126 admin optional mdadm_2.5.3.git200608202239-1_i386.deb 1017b063b913f43dbe7e8f23dd427d03 68188 debian-installer optional mdadm-udeb_2.5.3.git200608202239-1_i386.udeb Package-Type: udeb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE6PP5IgvIgzMMSnURAndkAJ0a8BYhN+jfjkGuGtzG/phkZDfczgCgwjvg PhYHYrDEZtB7Y4lLtyLp6Bk= =FDVN -----END PGP SIGNATURE-----
--- End Message ---
