Hi, I'm the ubuntu user that wrote the first post related to this in "ubuntuforuns". I can confirm that "...'blkid /dev/mdX' and 'mdadm --detail --scan' disagree about the UUIDs for my RAID arrays...". :-( I can also confirm that (in ubuntu) this problem is erratic: only happens once every few reboots and most of the times the machines start normally (?). In my case (as "unclepedro" already said) the "reboot" command usually solves the problem. I must also say that this hasn't happened again during the last two months (but I can't say why... since it's not a permanent problem, I can't be sure) I've also tried to solve this by "telling" fstab to mount the arrays from "/dev/mdX" instead of "UUID" but this hasn't worked. In the process, I found that fstab lists the raid arrays as the command "blkid". Does it make any sense to manually edit fstab to match the mdam UUIDs?
Since it seems you guys know more about the system than I do, please give me some advice as soon as you find an answer. Thanks, Rui Ruas -- 2.6.24-21 kernel update breaks mdadm raid 1 boot https://bugs.launchpad.net/bugs/290231 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
