[Bug 1635049] Re: Boot fails with degraded mdadm raid

[Dimitri John Ledkov]

On 10 April 2017 at 16:57, Eero <1635049 at bugs.launchpad.net> wrote:
>> And your boot is waiting for you to unlock the encrypted volume...
>> only after which the volume groups will be detected.
>
> Why do you lie? You didn't even look what I reported?
>

File a new bug report with text logs.... not photographs / screenshots.

> The first screenshot clearly shows that the boot fails before password is even asked.
> The second screenshot shows that the password is asked when I attached the drive again.
>
> I've submitted a bug report regarding this to Ubuntu and Debian, but
> nobody seems to care. It's 2017 and RAID 1 doesn't work...
>
> https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1680448
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859691
>
>
> ** Bug watch added: Debian Bug tracker #859691
>    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859691
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1635049
>
> Title:
>   Boot fails with degraded mdadm raid
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1635049/+subscriptions


-- 
Regards,

Dimitri.

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

Title:
  Boot fails with degraded mdadm raid

Status in mdadm package in Ubuntu:
  Fix Released
Status in mdadm source package in Xenial:
  Fix Released
Status in mdadm package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Systems fail to boot in certain status of mdadm arrays, requiring
  manual recovery / array assembly

   * Backport of boot logic from yakkety

  [Test Case]

   * Install a system with RAID1 and two hard-drives and boot the system with array in-sync
   * Shutdown
   * Disconnect one of the drives and thus boot, unexpectedly, degraded
   * The boot should complete.
   * Shutdown, and boot again, expecting degraded state.
   * The boot should complete.
   * Shutdown, reconnect disconnected drive, and boot again.
   * The boot should complete, add the device to the array, the array should be resyncing, and results with system with array in-sync, just like at the beginning of the testcase.

  [Regression Potential]

   * Systems may continue to fail to boot degraded.

  [Other Info]

   * Original report

  mdadm does not attempt to start partial md devices (incremental
  assembly) during initramfs and can cause system to fail to initramfs
  prompt if rootfs on md.

  http://askubuntu.com/questions/789953/how-to-enable-degraded-raid1
  -boot-in-16-04lts

  Fixed in debian mdadm 3.4-2: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=784070

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1635049/+subscriptions