"No devices listed in conf file were found" due to mdadm RAID1 array UUID different from actual UUID reported by vol_id
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Early in the boot process for Feisty, I get a message from mdadm
No devices listed in conf file were found
When I read Bug #120504 (maybe this is a duplicate of that), I got a clue that the UUIDs in /etc/mdadm/
The bug is is that mdadm and vol_id are reporting different UUIDs for the same device.
# uname -a
Linux atlas 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux
# vol_id /dev/md0
ID_FS_USAGE=
ID_FS_TYPE=ext3
ID_FS_VERSION=1.0
ID_FS_UUID=
ID_FS_LABEL=/boot
ID_FS_LABEL_
# mdadm --detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Sun Jul 31 00:58:00 2005
Raid Level : raid1
Array Size : 979840 (957.04 MiB 1003.36 MB)
Device Size : 979840 (957.04 MiB 1003.36 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Tue Jul 17 02:48:22 2007
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : f69e981b:
Events : 0.11860
Number Major Minor RaidDevice State
0 22 1 0 active sync /dev/hdc1
1 3 1 1 active sync /dev/hda1
# ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 9 2007-07-17 02:29 3d721ac2-
lrwxrwxrwx 1 root root 28 2007-07-17 02:29 630f92e4-
lrwxrwxrwx 1 root root 10 2007-07-17 02:29 a3150b2e-
lrwxrwxrwx 1 root root 9 2007-07-17 02:29 bff2d095-
# mdadm --detail --scan
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=f69e981b:
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=6b73608b:
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=711d6d5c:
ARRAY /dev/md4 level=raid1 num-devices=2 UUID=8e449434:
# vol_id -u /dev/md0
bff2d095-
# vol_id /dev/md1
ID_FS_USAGE=raid
ID_FS_TYPE=
ID_FS_VERSION=LVM2 001
ID_FS_UUID=
ID_FS_LABEL=
ID_FS_LABEL_SAFE=
# vol_id /dev/md2
ID_FS_USAGE=other
ID_FS_TYPE=swap
ID_FS_VERSION=2
ID_FS_UUID=
ID_FS_LABEL=
ID_FS_LABEL_SAFE=
# vol_id /dev/md4
ID_FS_USAGE=
ID_FS_TYPE=ext3
ID_FS_VERSION=1.0
ID_FS_UUID=
ID_FS_LABEL=data
ID_FS_LABEL_
Since the recommended method to create mdadm.conf is through appending the output of "mdadm --detail --scan", if mdadm isn't getting UUIDs the same way vol_id is, problems result.
I started having this problem after upgrading to Feisty.
In my case, my arrays did start OK even with this error because (I think) they are type FD and the kernel was able to start them by itself.
This occurs with:
mdadm 2.5.6-7ubuntu5
volumeid 108-0ubuntu4
mdadm superblock versions are .90. Perhaps this bit from the mdadm man page is relevant:
For version-0.90
of the UUID.
I haven't tried updating the UUID with mdadm --update. I'm not sure if this can be done without losing the array.
FIX:
Manually editing the UUIDs in /etc/mdadm/
Changed in mdadm: | |
status: | New → Confirmed |
Regarding the fix, after updating mdadm.conf, one also needs to regenerate the initrd.img files:
update- initramfs -k all -u