[10:13] <ari-tczew> M-o-M has been not refreshed since 1 week :-/ "Generated at 2014-07-06 03:45:43 UTC."
[11:35] <loa> Hello. Why bootdegraded=true option was deleted from ubuntu 14.04?
[11:40] <bekks> loa: Because a degraded RAID will still boot. :)
[11:40] <loa> bekks, it is not.
[11:41] <loa> boot only one time *
[11:41] <loa> if reboot again i always droped into initramfs
[11:41] <bekks> So whats the exact error when it isnt booting? And lets take this to #ubuntu
[11:43] <loa> bekks, it boots only one, if i reboot again i recieve this https://dl.dropboxusercontent.com/u/25725476/screenshot-2014.07.13-15%3A42%3A50.png
[11:43] <loa> bekks, i don't uderstand for what reason this done.
[11:43] <loa> maybe for possibility to do last backups...
[11:44] <loa> i found this https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1279741
[11:44] <loa> not i if to be true) another man from ubuntu.
[11:44] <bekks> loa: If you dont have backups at that point, its too late most likely ;)
[11:45] <loa> bekks, my point to do gateway wchich will work as far as possible)
[11:45] <bekks> I didnt get that sentence.
[11:45] <loa> data is not what i am worring about.
[11:45] <loa> i want degraded raid to boot ok.
[11:45] <loa> i don't want that initramfs thing.
[11:46] <loa> Under 12.04 all work as expected, that what i am talking about.
[11:46] <bekks> The device is busy, as the message states. So better use rootdelay=
[11:47] <loa> it even asking me at install "Do you want to boot degraded raid?"
[11:48] <loa> bekks, what rootdelay exectly do?
[11:48] <loa> i need to pass number of seconds to it?
[11:49] <loa> bekks, https://dl.dropboxusercontent.com/u/25725476/screenshot-2014.07.13-15%3A49%3A46.png
[11:50] <loa> bekks, do you read this? https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1279741
[11:50] <loa> i am about this part: We should attempt starting arrays with --no-degraded a few times, and after a timeout assemble them with --run, and if we don't have enough drives to start the array only then fall through to initramfs recovery shell.
[13:36] <mapreri> pitti: I'm wondering if we should bother ourself with a merge like this: http://paste.debian.net/109461/ or it's better to sync it (I think the letter)
[13:49] <xnox> loa: it was removed, because it was generating false positive, e.g. a non-degraded array was marked randomly as degraded even if it wasn't.
[13:50] <xnox> loa: we do start them with no-degraded via udev scan/trigger, and if that fails start degraded, or else fall to udev.
[13:50] <loa> xnox, can't understand what problem that array get marked as degraded.
[13:51] <xnox> loa: if there is something not working as expected, please open a new bug.
[13:51] <loa> xnox, i can't understnad if it is expacted or not.
[13:51] <loa> xnox, can i describe again what i do and what happened?
[13:51] <xnox> loa: e.g. in 12.04, with RAID1 with both drives always present, a few boots would come up into initramfs and fail to boot claiming that a drive is missing.... even though it isn't.
[13:52] <xnox> which is a big problem for remote machines with no console access.
[13:52] <loa> xnox, strange now i recieve totally another results.
[13:52] <loa> for example i have ubuntu 14.04
[13:53] <loa> i create raid 1 and remove one drive.
[13:53] <xnox> it will boot degraded.
[13:53] <loa> only one time.
[13:53] <loa> if i reboot again it fallbacks to initramfs busybox
[13:53] <loa> is it as expected?
[13:53] <xnox> that's wrong, can you please open a bug report against mdadm about that?
[13:53] <xnox> with $ ubuntu-bug mdadm
[13:53] <xnox> if possible?
[13:54] <loa> i will try.
[13:57] <loa> xnox, problem that i am emulating this situation using virtualbox
[13:57] <loa> maybe it is problem.
[13:57] <loa> i will recieve real hardware on next week.
[13:58] <loa> xnox, now i see that it is unstable. Sometimes it boots ok, but sometimes it drops into initramfs
[13:59] <loa> maybe it is problem of virtualbox not ubuntu.
[14:16] <michagogo> .whois bdmurray bdmurray
[14:16] <michagogo> gah, wrong key -_-
[15:41] <loa> xnox, https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1341312