Comment 32 for bug 278176

You can change the timeout if you have unusual hardware that needs longer, so I don't think we're going to change the default since it works for the vast majority of machines. There are also other bugs already about how mdadm handles degraded activation, so I'm closing that task too. If there is particular hardware that seems to take longer than it should to scan that may be a driver problem, we might look into that. Please attach /var/log/kern.log.