Bug#553896: mdadm: update-initramfs warning due to /dev/md/0 vs. /dev/md0.
tags 553896 patch thanks also sprach Julian Mehnle jul...@mehnle.net [2010.01.29.0324 +1300]: I cannot figure out from the bugscript what your problem is. Hopefully you'll be able to spot the issue soon. I'll make another attempt at upgrading my system, although it make take me another two or three weeks before I get to it. Right now is not a good time. It occured to me that the patch at http://git.debian.org/?p=pkg-mdadm/mdadm.git;a=commitdiff;h=a82f419df02a4dacf4046cbee9dfb48ccbeaab11 should fix your problem, because it checks for the UUID instead of the devname. Please try applying it to /usr/share/initramfs-tools/hooks/mdadm, rerunning update-initramfs -u, and seeing if the problem persists. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#553896: mdadm: update-initramfs warning due to /dev/md/0 vs. /dev/md0.
martin f krafft wrote: Which sensitive bits? I am asking to be able to improve the bug script. Several bind mounts that were much more specific than the typical mount point. Serial numbers in hard disk device names. Stuff like that. I cannot figure out from the bugscript what your problem is. Hopefully you'll be able to spot the issue soon. I'll make another attempt at upgrading my system, although it make take me another two or three weeks before I get to it. Right now is not a good time. Thanks, -Julian signature.asc Description: This is a digitally signed message part.
Bug#553896: mdadm: update-initramfs warning due to /dev/md/0 vs. /dev/md0.
I've been having the same problem. I'm attaching my mdadm bug script output (with a few sensitive bits redacted). Also: | $ sudo mdadm -Ds | ARRAY /dev/md/0 metadata=0.90 UUID=222a461f:8303a4d2:4a90023e:7c4f4b06 -Julian --- mount output /dev/mapper/vg0-main_crypt on / type xfs (rw,noatime) 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) 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) fusectl on /sys/fs/fuse/connections type fusectl (rw) /dev/mapper/vg0-boot on /boot type xfs (rw,noatime) /dev/mapper/vg0-bare on /media/bare type xfs (rw,noatime) /dev/mapper/usbdisk0_crypt on /media/usbdisk0 type fuseblk (rw,noexec,nosuid,nodev,allow_other,default_permissions,blksize=4096) /dev/sdd1 on /media/usbdisk1 type fuseblk (rw,noexec,nosuid,nodev,allow_other,default_permissions,blksize=4096) (bind mounts redacted for privacy reasons) --- 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=222a461f:8303a4d2:53851496:d0cc6843 #ARRAY /dev/md/0 level=raid1 num-devices=2 UUID=222a461f:8303a4d2:53851496:d0cc6843 #ARRAY /dev/md0 level=raid1 num-devices=2 UUID=222a461f:8303a4d2:4a90023e:7c4f4b06 ARRAY /dev/md/0 level=raid1 num-devices=2 UUID=222a461f:8303a4d2:4a90023e:7c4f4b06 # This file was auto-generated on Thu, 25 Dec 2008 23:23:49 + # by mkconf $Id$ --- /proc/mdstat: Personalities : [raid1] md0 : active raid1 sda1[0] sdb1[1] 488383936 blocks [2/2] [UU] bitmap: 6/233 pages [24KB], 1024KB chunk unused devices: none --- /proc/partitions: major minor #blocks name 80 488386584 sda 81 488384001 sda1 8 16 488386584 sdb 8 17 488384001 sdb1 90 488383936 md0 2530 122880 dm-0 2531 456257536 dm-1 2532 32002048 dm-2 8 32 488386584 sdc 8 33 32098 sdc1 8 34 488351902 sdc2 8 48 488386584 sdd 8 49 488384001 sdd1 2533 456256508 dm-3 2534 488351386 dm-4 --- initrd.img-2.6.30-2-amd64: 50770 blocks 66818791d08ce4ca57f4989c6e3b7d54 ./etc/mdadm/mdadm.conf 13b4102c11a94b2d9e300b617c9f806a ./lib/modules/2.6.30-2-amd64/kernel/drivers/md/dm-mod.ko 988339597939b708e346a61bd4a6a343 ./lib/modules/2.6.30-2-amd64/kernel/drivers/md/dm-crypt.ko f4762b1f0d4f3e303072c637753ce366 ./lib/modules/2.6.30-2-amd64/kernel/drivers/md/dm-snapshot.ko 16ee20acf5405ba0947bdb6cc9cd54b9 ./lib/modules/2.6.30-2-amd64/kernel/drivers/md/dm-log.ko 4863981fb1954174ea77b9f476991536 ./lib/modules/2.6.30-2-amd64/kernel/drivers/md/dm-region-hash.ko 165fe6c1793eaedea1aa2db2cdb1aed3 ./lib/modules/2.6.30-2-amd64/kernel/drivers/md/dm-mirror.ko fac315a287715e2ca70756f758912cb0 ./lib/modules/2.6.30-2-amd64/kernel/drivers/md/md-mod.ko 3a081ea94071a3e5b2e72dd4c67eb671 ./lib/modules/2.6.30-2-amd64/kernel/drivers/md/linear.ko 20d388cd4ea7636d903ab522c20a97bb ./lib/modules/2.6.30-2-amd64/kernel/drivers/md/multipath.ko 60c056c6dbbd2c46e932f5b25be86354 ./lib/modules/2.6.30-2-amd64/kernel/drivers/md/raid0.ko 2fc7df8b12010f788514021ddab80f12 ./lib/modules/2.6.30-2-amd64/kernel/drivers/md/raid1.ko 3c33b6068a91402431f25ab2a855fe08 ./lib/modules/2.6.30-2-amd64/kernel/drivers/md/raid6_pq.ko b1538856e0c3b7883940eeb800f68e20 ./lib/modules/2.6.30-2-amd64/kernel/drivers/md/raid456.ko 773fa6a5cdd4930ae7be012e37a6 ./lib/modules/2.6.30-2-amd64/kernel/drivers/md/raid10.ko 7966ccb72128e7a86d09b7c3b5df7557 ./sbin/mdadm 6b782ae76f866914ec236b2d14b43f24 ./scripts/local-top/mdadm --- /proc/modules: dm_crypt 12920 2 - Live 0xa01ba000 dm_mirror 14616 0 - Live 0xa01b1000 dm_region_hash 12704 1 dm_mirror, Live 0xa01ab000 dm_log 9924 2 dm_mirror,dm_region_hash, Live 0xa01a3000 dm_snapshot 22860 0 - Live 0xa0198000 dm_mod 59256 17 dm_crypt,dm_mirror,dm_log,dm_snapshot, Live 0xa0184000 raid1 21104 1 - Live 0xa0179000 md_mod 86628 2 raid1, Live 0xa015e000 --- /var/log/syslog: --- volume detail: /dev/sda is not recognised by mdadm. /dev/sda1: Magic : a92b4efc Version : 0.90.00 UUID : 222a461f:8303a4d2:4a90023e:7c4f4b06 Creation Time : Tue Dec 30 02:18:29 2008 Raid Level : raid1 Used Dev Size : 488383936 (465.76 GiB 500.11 GB) Array Size :
Bug#553896: mdadm: update-initramfs warning due to /dev/md/0 vs. /dev/md0.
also sprach Julian Mehnle jul...@mehnle.net [2010.01.28.1658 +1300]: I've been having the same problem. I'm attaching my mdadm bug script output (with a few sensitive bits redacted) Which sensitive bits? I am asking to be able to improve the bug script. I cannot figure out from the bugscript what your problem is. Hopefully you'll be able to spot the issue soon. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#553896: mdadm: update-initramfs warning due to /dev/md/0 vs. /dev/md0.
also sprach David Anselmi anse...@anselmi.us [2009.11.02.1541 +1300]: The issue is that /usr/share/initramfs-tools/hooks/mdadm finds /dev/md/0 and the mdadm.conf contained /dev/md0. Does this bug still bother you? Can you try to figure out why mdadm -Ds reports /dev/md/0 on your system? Can you please attach the output of /usr/share/bug/mdadm/script to this bug report? -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#553896: mdadm: update-initramfs warning due to /dev/md/0 vs. /dev/md0.
Package: mdadm Version: 3.0-3.1 Severity: minor Subject: mdadm: update-initramfs warning due to /dev/md/0 vs. /dev/md0. Package: mdadm Version: 3.0-3.1 Severity: minor During upgrade of mdadm (and kernel to 2.6.30), update-initramfs reports: W: mdadm: You appear to be missing /dev/md/0 from /etc/mdadm/mdadm.conf ! W: mdadm: If this array is required to boot, you must add the following line: W: mdadm: ARRAY /dev/md/0 UUID=03d88b02:ff765a00:54ce3db4:23a8abf8 The issue is that /usr/share/initramfs-tools/hooks/mdadm finds /dev/md/0 and the mdadm.conf contained /dev/md0. I wouldn't have reported this except that README.upgrading-2.5.3.gz says to use /usr/share/mdadm/mkconf as a guide and it finds /dev/md0. It appears that this warning doesn't mean anything, but... The UUID in my mdadm.conf was different than what the array is using (naturally I tried changing it before digging down to the differing devices). I wonder why, as I know I've had the wrong one in the past and at one point had the correct one? So I've matched it to mdadm --examine reports. I'll reply if I'm not able to boot. I wonder whether ignorning the warning would have prevented rebooting due to the incorrect UUID? Thanks for all your work! Dave -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages mdadm depends on: ii debconf 1.5.28 Debian configuration management sy ii libc6 2.9-25 GNU C Library: Shared libraries ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip ii makedev 2.3.1-89 creates device files in /dev ii udev 146-5 /dev/ and hotplug management daemo Versions of packages mdadm recommends: ii exim4-daemon-light [mail-tran 4.69-11+b1 lightweight Exim MTA (v4) daemon ii module-init-tools 3.11-1 tools for managing Linux kernel mo mdadm suggests no packages. -- debconf information excluded -- Package-specific info: IMPORTANT: please do not forget to include all relevant system information with this bug report. You could run /usr/share/bug/mdadm/script 31 as root and attach or include the output. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages mdadm depends on: ii debconf 1.5.28 Debian configuration management sy ii libc6 2.9-25 GNU C Library: Shared libraries ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip ii makedev 2.3.1-89 creates device files in /dev ii udev 146-5 /dev/ and hotplug management daemo Versions of packages mdadm recommends: ii exim4-daemon-light [mail-tran 4.69-11+b1 lightweight Exim MTA (v4) daemon ii module-init-tools 3.11-1 tools for managing Linux kernel mo mdadm suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
