Comment 105 for bug 120375

The new behavior present in Intrepid, following my series of patches,
results in the following message being printed to the console after 30
seconds of waiting for a complete array...

| There appears to be one or more degraded RAID devices, and your root device
| may depend on the RAID devices being online. One or more of the
following RAID
| devices are degraded:
| md0 : inactive sda1[0](S)
| 1020032 blocks

[See attached screenshot]

You can configure your RAID to boot even if degraded by running
`dpkg-reconfigure mdadm`, or, you can simply edit the file:
/etc/initramfs-tools/conf.d/mdadm by hand, and set BOOT_DEGRADED=true.
 They have the same effect.

Additionally, you can set or override this on the kernel boot line by
entering the grub menu and using any of the following:
 * bootdegraded
 * bootdegraded=1, bootdegraded=true, bootdegraded=on, bootdegraded=yes

If BOOT_DEGRADED=true, it will continue to boot automatically in the
event of a degraded RAID event.

If those are set to false, the following prompt will appear, and wait
15 seconds for you to hit 'y' or 'n', at which point it will default
to 'n':

| ** WARNING: The root filesystem was found on a degraded RAID array! **
|
| The system may have suffered a hardware fault, such as a disk drive failure.
| You may attempt to start the system anyway, or stop now and attempt manual
| recovery operations.
|
| If you choose to boot the degraded RAID, the system may start normally, but
| performance may be degraded, and a further hardware fault could result in
| permanent data loss.
|
| If you abort now, you will be provided with a recovery shell.
| Do you wish to boot the degraded RAID? [y/N]:

[See attached screenshot]

This interactive selection is a one time deal. It does not affect the
configuration as written to file.

These changes involve too much code (grub, mdadm, initramfs-tools),
too many new 'features', and are not security-critical enough to be
_automatically_ published to Hardy LTS.

That said, we do have documented process for providing Stable Release
Updates, and Backports to previous releases. Please follow the
procedures specified in:
 * https://wiki.ubuntu.com/StableReleaseUpdates
 * https://help.ubuntu.com/community/UbuntuBackports

This bug, "[Bug 120375] Re: cannot boot raid1 with only one disk", is
solved, and I'm un-subscribing from it.

If you have separate or additional issues, please open new bugs.

Thanks,
:-Dustin