[Bug 1060417] Re: mdadm BOOT_DEGRADED setting is ignored

[yct]

Okay. Things are a bit confusing in the cloud.

The new Grub 2 is not being used, and the cloud loader reads
/boot/grub/menu.lst entries directly (you can't use update-grub to
regenerate menu.lst anymore, as the new way is the grub.cfg file, which
however is not used in the cloud).

So all this confused me a bit and I also wasn't running update-initramfs
to reflect my changes in /etc/initramfs-tools/conf.d/mdadm.

The root of my issue was that I was creating a RAID5 array (without the
--force option), which automatically puts the array into "degraded,
rebuilding" state, which then fails to reboot (in the cloud) due to the
BOOT_DEGRADED defaulting to "false" (in /etc/initramfs-
tools/conf.d/mdadm).

Please close this bug, but hopefully this helps others.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1060417

Title:
  mdadm BOOT_DEGRADED setting is ignored

Status in “initramfs-tools” package in Ubuntu:
  New

Bug description:
  The file:

  /usr/share/initramfs-tools/scripts/mdadm-functions

  is supossed to check for:

  BOOT_DEGRADED="true"

  in file:

  /etc/initramfs-tools/conf.d/mdadm

  (also as per
  https://help.ubuntu.com/community/Installation/SoftwareRAID)

  however, it instead checks for it in the file:

  /conf/conf.d/mdadm

  which doesn't exit.

  Additionally, BOOT_DEGRADED should default to "true" and not "false",
  at least for the Cloud Server images, otherwise on a RAID failure, you
  are left with an unbootable production system, which kind of defies
  the point of having the RAID in the first place.

  Thanks,
  J.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1060417/+subscriptions