Bug#570516: mdadm: UUID changed upon upgrade
Josselin Mouette
joss at debian.org
Fri Feb 19 14:00:28 UTC 2010
Package: mdadm
Version: 3.0.3-2
Severity: normal
When upgrading one of my systems from lenny to squeeze, I was confronted
to a very strange message in all update-initramfs calls, asking me to
update my mdadm.conf so that my RAID volume is usable at boot time.
This was surprising since the mdadm.conf was already here. It turned out
that the UUID detected by mdadm had changed between lenny and squeeze.
Which pretty much defeats the point of an UUID!
The original UUID was "9f7c3f20:73a6e4da:6edb20b8:0abfba2a".
I had to change it to "9f7c3f20:73a6e4da:3998e195:148949b1" - see my
mdadm.conf below.
I don’t think it would have been a serious issue on my system, since
this is not a boot partition, but I suspect it could make some systems
unbootable.
-- Package-specific info:
--- mount output
/dev/sda1 on / type reiserfs (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)
/dev/sdb1 on /home type reiserfs (rw,relatime)
/dev/md0 on /stock type reiserfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,size=1200m)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
nfsd on /proc/fs/nfsd type nfsd (rw)
/dev/hdb on /media/Bokura no type iso9660 (ro,nosuid,nodev,uhelper=devkit,uid=1004,gid=1004,iocharset=utf8,mode=0400,dmode=0500)
--- 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 metadata=00.90 UUID=9f7c3f20:73a6e4da:6edb20b8:0abfba2a
ARRAY /dev/md/0 UUID=9f7c3f20:73a6e4da:3998e195:148949b1
# This file was auto-generated on Mon, 23 Mar 2009 13:07:20 +0100
# by mkconf $Id$
--- /proc/mdstat:
Personalities : [raid1]
md0 : active raid1 sda3[0] sdb3[1]
473539904 blocks [2/2] [UU]
unused devices: <none>
--- /proc/partitions:
major minor #blocks name
8 0 488386584 sda
8 1 13671283 sda1
8 2 1172745 sda2
8 3 473539972 sda3
8 16 488386584 sdb
8 17 14651248 sdb1
8 18 192780 sdb2
8 19 473539972 sdb3
9 0 473539904 md0
--- initrd.img-2.6.32-trunk-amd64:
49819 blocs
e2a21ee1504e66807807fc52044ebdd6 ./etc/mdadm/mdadm.conf
dfd5b6814dbf14350570d0abaabc7fbe ./lib/modules/2.6.32-trunk-amd64/kernel/drivers/md/md-mod.ko
5a09af71f3b7f6885d7b66d6bec40e2e ./lib/modules/2.6.32-trunk-amd64/kernel/drivers/md/linear.ko
db0a9b480d9f1b93dced01c66d1fca9b ./lib/modules/2.6.32-trunk-amd64/kernel/drivers/md/multipath.ko
000317b61506670ed615c64044a83894 ./lib/modules/2.6.32-trunk-amd64/kernel/drivers/md/raid0.ko
ae6554df8cddfb42c5beaebf7002e967 ./lib/modules/2.6.32-trunk-amd64/kernel/drivers/md/raid1.ko
01bc5c24d8510aef6a51250229137489 ./lib/modules/2.6.32-trunk-amd64/kernel/drivers/md/raid6_pq.ko
3146bbdb5751d2978c527456392b2860 ./lib/modules/2.6.32-trunk-amd64/kernel/drivers/md/raid456.ko
8f8c981b6895d54605255e9147c13c01 ./lib/modules/2.6.32-trunk-amd64/kernel/drivers/md/raid10.ko
7966ccb72128e7a86d09b7c3b5df7557 ./sbin/mdadm
6b782ae76f866914ec236b2d14b43f24 ./scripts/local-top/mdadm
--- /proc/modules:
raid1 18175 1 - Live 0xffffffffa019b000
md_mod 73616 2 raid1, Live 0xffffffffa017f000
--- /var/log/syslog:
--- volume detail:
/dev/hdb is not recognised by mdadm.
/dev/sda is not recognised by mdadm.
/dev/sda1 is not recognised by mdadm.
/dev/sda2 is not recognised by mdadm.
/dev/sda3:
Magic : a92b4efc
Version : 0.90.00
UUID : 9f7c3f20:73a6e4da:3998e195:148949b1
Creation Time : Mon Mar 23 13:10:45 2009
Raid Level : raid1
Used Dev Size : 473539904 (451.60 GiB 484.90 GB)
Array Size : 473539904 (451.60 GiB 484.90 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Update Time : Tue Feb 2 23:38:27 2010
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : bbda6a3b - correct
Events : 54
Number Major Minor RaidDevice State
this 0 8 3 0 active sync /dev/sda3
0 0 8 3 0 active sync /dev/sda3
1 1 8 19 1 active sync /dev/sdb3
--
/dev/sdb is not recognised by mdadm.
/dev/sdb1 is not recognised by mdadm.
/dev/sdb2 is not recognised by mdadm.
/dev/sdb3:
Magic : a92b4efc
Version : 0.90.00
UUID : 9f7c3f20:73a6e4da:3998e195:148949b1
Creation Time : Mon Mar 23 13:10:45 2009
Raid Level : raid1
Used Dev Size : 473539904 (451.60 GiB 484.90 GB)
Array Size : 473539904 (451.60 GiB 484.90 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Update Time : Tue Feb 2 23:38:27 2010
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : bbda6a4d - correct
Events : 54
Number Major Minor RaidDevice State
this 1 8 19 1 active sync /dev/sdb3
0 0 8 3 0 active sync /dev/sda3
1 1 8 19 1 active sync /dev/sdb3
--
--- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-amd64 root=UUID=7bd37f3b-5b40-4dd8-afff-e4d87acbef70 ro quiet
--- grub2:
set root=(hd0,1)
set root=(hd0,1)
set root=(hd0,1)
linux /boot/vmlinuz-2.6.32-trunk-amd64 root=UUID=7bd37f3b-5b40-4dd8-afff-e4d87acbef70 ro quiet
set root=(hd0,1)
linux /boot/vmlinuz-2.6.32-trunk-amd64 root=UUID=7bd37f3b-5b40-4dd8-afff-e4d87acbef70 ro single
set root=(hd0,1)
linux /boot/vmlinuz-2.6.26-2-amd64 root=UUID=7bd37f3b-5b40-4dd8-afff-e4d87acbef70 ro quiet
set root=(hd0,1)
linux /boot/vmlinuz-2.6.26-2-amd64 root=UUID=7bd37f3b-5b40-4dd8-afff-e4d87acbef70 ro single
set root=(hd0,1)
linux /boot/vmlinuz-2.6.26-1-amd64 root=UUID=7bd37f3b-5b40-4dd8-afff-e4d87acbef70 ro quiet
set root=(hd0,1)
linux /boot/vmlinuz-2.6.26-1-amd64 root=UUID=7bd37f3b-5b40-4dd8-afff-e4d87acbef70 ro single
--- grub legacy:
kernel /boot/vmlinuz-2.6.32-trunk-amd64 root=/dev/sda1 ro
kernel /boot/vmlinuz-2.6.32-trunk-amd64 root=/dev/sda1 ro single
kernel /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sda1 ro
kernel /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sda1 ro single
kernel /boot/vmlinuz-2.6.26-1-amd64 root=/dev/sda1 ro
kernel /boot/vmlinuz-2.6.26-1-amd64 root=/dev/sda1 ro single
--- udev:
ii udev 150-2 /dev/ and hotplug management daemon
4a574fcd059040d33ea18a8aa605a184 /lib/udev/rules.d/64-md-raid.rules
--- /dev:
brw-rw---- 1 root disk 9, 0 févr. 2 22:40 /dev/md0
/dev/disk/by-id:
total 0
lrwxrwxrwx 1 root root 9 févr. 2 22:41 ata-ST3500320AS_9QMAC8XB -> ../../sda
lrwxrwxrwx 1 root root 10 févr. 2 22:39 ata-ST3500320AS_9QMAC8XB-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 févr. 2 22:39 ata-ST3500320AS_9QMAC8XB-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 févr. 2 22:39 ata-ST3500320AS_9QMAC8XB-part3 -> ../../sda3
lrwxrwxrwx 1 root root 9 févr. 2 22:39 ata-ST3500320AS_9QMADR3K -> ../../sdb
lrwxrwxrwx 1 root root 10 févr. 2 22:39 ata-ST3500320AS_9QMADR3K-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 févr. 2 22:39 ata-ST3500320AS_9QMADR3K-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 févr. 2 22:39 ata-ST3500320AS_9QMADR3K-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 9 févr. 2 22:40 ata-TOSHIBA_DVD-ROM_SD-M1712_ -> ../../hdb
lrwxrwxrwx 1 root root 9 févr. 2 22:39 md-uuid-9f7c3f20:73a6e4da:3998e195:148949b1 -> ../../md0
lrwxrwxrwx 1 root root 9 févr. 2 22:41 scsi-SATA_ST3500320AS_9QMAC8XB -> ../../sda
lrwxrwxrwx 1 root root 10 févr. 2 22:39 scsi-SATA_ST3500320AS_9QMAC8XB-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 févr. 2 22:39 scsi-SATA_ST3500320AS_9QMAC8XB-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 févr. 2 22:39 scsi-SATA_ST3500320AS_9QMAC8XB-part3 -> ../../sda3
lrwxrwxrwx 1 root root 9 févr. 2 22:39 scsi-SATA_ST3500320AS_9QMADR3K -> ../../sdb
lrwxrwxrwx 1 root root 10 févr. 2 22:39 scsi-SATA_ST3500320AS_9QMADR3K-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 févr. 2 22:39 scsi-SATA_ST3500320AS_9QMADR3K-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 févr. 2 22:39 scsi-SATA_ST3500320AS_9QMADR3K-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 9 févr. 2 22:39 wwn-0x5000c50010e0c9df -> ../../sdb
lrwxrwxrwx 1 root root 10 févr. 2 22:39 wwn-0x5000c50010e0c9df-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 févr. 2 22:39 wwn-0x5000c50010e0c9df-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 févr. 2 22:39 wwn-0x5000c50010e0c9df-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 9 févr. 2 22:41 wwn-0x5000c50010e0e041 -> ../../sda
lrwxrwxrwx 1 root root 10 févr. 2 22:39 wwn-0x5000c50010e0e041-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 févr. 2 22:39 wwn-0x5000c50010e0e041-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 févr. 2 22:39 wwn-0x5000c50010e0e041-part3 -> ../../sda3
/dev/disk/by-path:
total 0
lrwxrwxrwx 1 root root 9 févr. 2 22:41 pci-0000:00:11.0-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 févr. 2 22:39 pci-0000:00:11.0-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 févr. 2 22:39 pci-0000:00:11.0-scsi-0:0:0:0-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 févr. 2 22:39 pci-0000:00:11.0-scsi-0:0:0:0-part3 -> ../../sda3
lrwxrwxrwx 1 root root 9 févr. 2 22:39 pci-0000:00:11.0-scsi-2:0:0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 févr. 2 22:39 pci-0000:00:11.0-scsi-2:0:0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 févr. 2 22:39 pci-0000:00:11.0-scsi-2:0:0:0-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 févr. 2 22:39 pci-0000:00:11.0-scsi-2:0:0:0-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 9 févr. 2 22:40 pci-0000:00:14.1 -> ../../hdb
/dev/disk/by-uuid:
total 0
lrwxrwxrwx 1 root root 10 févr. 2 22:39 053f70ef-0c5a-4c5c-9553-72c42ed4b798 -> ../../sdb1
lrwxrwxrwx 1 root root 10 févr. 2 22:39 7a417705-3057-42d4-8692-5e36469569de -> ../../sdb2
lrwxrwxrwx 1 root root 10 févr. 2 22:39 7bd37f3b-5b40-4dd8-afff-e4d87acbef70 -> ../../sda1
lrwxrwxrwx 1 root root 10 févr. 2 22:39 c6388175-f3c9-4c73-8cf3-01d961a04745 -> ../../sda2
lrwxrwxrwx 1 root root 9 févr. 2 22:39 e459c48a-956b-463d-8b6e-31881c073fab -> ../../md0
/dev/md:
total 0
lrwxrwxrwx 1 root root 6 févr. 2 22:39 0 -> ../md0
Auto-generated on Tue, 02 Feb 2010 23:48:42 +0100
by mdadm bugscript 3.0.3-2
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mdadm depends on:
ii debconf 1.5.28 Debian configuration management sy
ii libc6 2.10.2-2 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 150-2 /dev/ and hotplug management daemo
Versions of packages mdadm recommends:
ii exim4-daemon-light [mail-tran 4.71-3 lightweight Exim MTA (v4) daemon
ii module-init-tools 3.11-1 tools for managing Linux kernel mo
mdadm suggests no packages.
-- debconf information:
* mdadm/autostart: true
mdadm/mail_to: root
mdadm/initrdstart_msg_errmd:
* mdadm/initrdstart: all
mdadm/initrdstart_msg_errconf:
mdadm/initrdstart_notinconf: false
mdadm/initrdstart_msg_errexist:
mdadm/initrdstart_msg_intro:
mdadm/autocheck: true
mdadm/initrdstart_msg_errblock:
mdadm/start_daemon: true
--
.''`. Josselin Mouette
: :' :
`. `' “A handshake with whitnesses is the same
`- as a signed contact.” -- Jörg Schilling
More information about the pkg-mdadm-devel
mailing list