On 10 April 2017 at 16:57, Eero <1635...@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 Bugs, which is subscribed to Ubuntu. 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
