Hi Timothy-
My apologies to you, on behalf of whoever closed this report as
"Invalid". That was clearly the wrong response, as they did not
understand your problem.
I could confirm the behavior you were seeing.
I have spent quite a bit of time addressing a number of RAID issues in
Intrepid, and I think this one should now be resolved.
There is now a debconf question within mdadm, which will set a value of
BOOT_DEGRADED=true|false in /etc/initramfs-tools/conf.d/mdadm.
If it's set to 'true', then the administrator wants to boot the system
even if an md-degraded event has occurred. This is desirable behavior
for some sysadmins who want their unattended, RAID-protected system to
boot no matter what.
If it's set to 'false', the initramfs will spend 30 seconds trying to
construct the md device, and if that fails, a meaningful error message
is printed, along with an interactive prompt asking if you would like to
boot your system on this degraded array [y/N]. The default is "no", and
it will time out if there is no response within 15 seconds. In which
case, you will be dropped to a busybox shell in the initramfs.
Would it be possible for you to test the new behavior in Intrepid?
I'm going to mark this bug as "Fix Released" for now. If you test it in
intrepid, and still see a problem, please respond here and we can reopen
it.
Thanks,
:-Dustin
** Changed in: mdadm (Ubuntu)
Status: Invalid => Fix Released
--
Critical Dapper bug: Missing secondary from software RAID1, no message or
warning
https://bugs.launchpad.net/bugs/58893
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
