Note that your output with the patch is bogus, the UUID is wrong. See following from Kay Sievers (udev upstream):
> We've had a bug report filed for Ubuntu caused by vol_id not correctly > detecting a RAID1 with 1.0 metadata: > > https://bugs.launchpad.net/ubuntu/+source/udev/+bug/133773 Seems like a bug for metadata 1.0, yes. > A patch is attached to the bug (attached again here), does this seem a > reasonable fix? But the UUID looks strange: ID_FS_UUID=9c0818c2:00000000:00000000:00000000 I see the same thing here with this patch: $ mdadm -E /dev/sda7 Array UUID : 847bf627:97a28f2a:37e21246:25b446b1 $ extras/volume_id/vol_id /dev/sda7 ID_FS_UUID=2a8fa297:00000000:00000000:00000000 With a different one line fix to the lib it seems fine: $ extras/volume_id/vol_id /dev/sda7 ID_FS_UUID_ENC=847bf627:97a28f2a:37e21246:25b446b1 -- [gutsy] partitions no longer detected as RAID components after repairing degraded RAID 1 mirror https://bugs.launchpad.net/bugs/133773 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
