This did not work but I'm not clear why. It might have been be messing
up the grub install.
--
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 manag
Hey there kids, this bug still appears to be relevant for 16.04. My
/dev/sda died today and I'm prepping to replace the disk. I note that
the answer here https://askubuntu.com/a/798213/185653 notes the missing
file and it's still missing.
I haven't tried a reboot as I'm waiting for the monthly che
Is this bug report abandoned?
And why the bug is assigned to Dimitri John Ledkov? He is obviously
incompetent. In comment number 18 he even claimed that photographs and
screenshots aren't acceptable in bug reports even though Ubuntu's
website clearly states otherwise.
--
You received this bug no
It seems that this is still somehow broken with Xubuntu 17.04
I just tried mdadm within Xubuntu 17.04 in Virtualbox using the following setup:
1 virtual disk containing the OS.
2 virtual disks running as a RAID 1.
Whenever I disconnect one of the RAID disks, Xubuntu cannot boot.
I wrote the scrip
This is still broken in Xenial with mdadm 3.3-2ubuntu7.2
--
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 t
>From Ubuntu's own documentation
https://wiki.ubuntu.com/DebuggingKernelBoot:
> If you are unable to capture a log file, a digital photo will work
just as well.
Hopefully someone competent will see these messages at some point.
--
You received this bug notification because you are a member of U
> File a new bug report with text logs not photographs /
screenshots.
And this is a perfect example why Ubuntu is a piece of garbage. Someone
reports a serious issue with Ubuntu, but the whole bug gets dismissed,
because the reports are in a "wrong" format.
How do you even get early boot logs
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
> 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?
The first screenshot clearly shows that the boot fails before password is even
asked.
The second screenshot shows that
On 5 April 2017 at 07:28, Eero <1635...@bugs.launchpad.net> wrote:
> I just made a fresh install from ubuntu-16.04.2-server-amd64.iso,
> updated everything, and tested to boot without one disk. It failed. See
> the attachment for my RAID configuration.
>
> https://imgur.com/a/RApJS
>
Please open n
I just made a fresh install from ubuntu-16.04.2-server-amd64.iso,
updated everything, and tested to boot without one disk. It failed. See
the attachment for my RAID configuration.
https://imgur.com/a/RApJS
** Attachment added: "partitioning.png"
https://bugs.launchpad.net/ubuntu/+source/mdadm
This bug was fixed in the package mdadm - 3.3-2ubuntu7.2
---
mdadm (3.3-2ubuntu7.2) xenial; urgency=medium
* Backport initramfs changes from 3.4-4, to improve reliability of
booting with degraded arrays. LP: #1635049
* debian/initramfs/hook:
- Fix UUID= grep for configure
I have also validated the proposed package on my reproducer sandbox, and it
worked correctly.
Still awaiting feedback from customer with ppc64le system, as soon as I hear
back I will let you know.
-Adam
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
retested without ppa, and just with proposed using 3.3-2ubuntu7.2.
** Tags removed: verification-needed
** Tags added: verification-done
--
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:
I can do that. However, I am not sure if that is necessary since this is a
sync from bileti ppa, and thus it is identical binaries.
On 1 Mar 2017 22:31, "Brian Murray" wrote:
Was the "check again using the proper proposed repository package" made?
** Tags removed: verification-done
** Tags add
Was the "check again using the proper proposed repository package" made?
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1635049
Ti
** Tags removed: verification-needed
** Tags added: verification-done
--
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
Hi Lukasz and Dragan, I just received confirmation from a customer that
the propsed package also fixed the issue on their ibm power environment
as well.
This was using the ca-train-ppa-service ppa however, so I'll check again
using the proper proposed repository package.
--
You received this bu
I accepted the package from the queue to -proposed but since it was a
sync I couldn't do it through the proper tooling (I think I need to get
educated how to do it properly for synces?). Anyway, this means that
there was no auto-release message. Please install the package from
xenial-proposed, test
PPA located at:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2500
Fixes my degraded raid boot issues. System boots up fine after this PPA
is applied.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Proposing the following fix:
mdadm (3.3-2ubuntu7.2) xenial; urgency=medium
* Backport initramfs changes from 3.4-4, to improve reliability of
booting with degraded arrays. LP: #1635049
* debian/initramfs/hook:
- Fix UUID= grep for configured RAIDs to be case insensitive.
- Drop C
** Description changed:
[Impact]
- * Systems fail to boot in certain status of mdadm arrays, requiring
+ * Systems fail to boot in certain status of mdadm arrays, requiring
manual recovery / array assembly
- * Backport of boot logic from yakkety
+ * Backport of boot logic from yakket
** Description changed:
+ [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-sy
Will there be any backport patch for Ubuntu 16.04.2?
Just tested this out yesterday and Ubuntu 16.04.2 with latest update
still could not boot secondary drive.
My test was done on Linux mdadm RAID1 with LVM. (/dev/md0 for /boot xfs,
and /dev/md1 for LVM with /root xfs and swap).
--
You received
** Changed in: mdadm (Ubuntu)
Milestone: None => ubuntu-17.02
--
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
Dimitri - Do you have any plans to get this fixed in Xenial?
--
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
** Changed in: mdadm (Ubuntu)
Importance: Undecided => High
** Changed in: mdadm (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/163
** Changed in: mdadm (Debian)
Status: Unknown => Fix Released
--
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 t
This is fixed in 16.10 and Zesty, but I'm leaving the task open so the
bug doesn't disappear from some LP searches.
** Bug watch added: Debian Bug tracker #784070
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784070
** Also affects: mdadm (Debian) via
http://bugs.debian.org/cgi-bin/bugre
** Tags added: regression-release xenial
--
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.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mdadm (Ubuntu)
Status: New => Confirmed
--
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
31 matches
Mail list logo
