sane behavior for wrong /etc/mdadm/mdadm.conf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
After upgraded to Edgy, my system took 3 minutes on boot before i can leave the initrd. After careful investigation of the scripts in the initrd, I found that there is a wrong UUID embedded in /etc/mdadm/mdadm. This caused the loop in /usr/share/
I guess there is a better way to do that. 180 seconds is too long. I guess no device would need more than 15 seconds to be activated. This long wait make people feel that they machine is actually frozen, since no progress bar is shown during the time. I know it doesn't want to print something to mess up usplash, but they added up (no progress + 180 seconds) gives an insane experience.
I do not agree this bug is a duplicate of bug 67299. I was aware of bug 67299 and bug 68888 when I reported it.
This bug concerns when the config is wrong. Bug 68888 is about when the config is correct but in an unexpected format. Bug 67299 is about when the whole disk is used for RAID.