---
> From: "Roy Sigurd Karlsbakk"
> To: "Roy Sigurd Karlsbakk"
> Sent: Thursday, 15 September, 2016 05:22:49
> Subject: Re: [Bug 1171945] Re: Nested RAID levels aren't started after reboot
> Give me some time - I have a test VM somewhere to test this… It'
r, 2016 04:16:52
> Subject: [Bug 1171945] Re: Nested RAID levels aren't started after reboot
> I have not being able to test this on 16.04, but is this still happening
> on 16.04 and above?
>
> --
> You received this bug notification because you are subscribed to the bug
I have not being able to test this on 16.04, but is this still happening
on 16.04 and above?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Nested RAID levels aren't started after rebo
I guess the fix suggested is the proper fix. No idea why it's being
ignored like this. I reported it more than two years ago, it's in an LTS
and its fix is a single udev line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I'm running Lubuntu 14.04 and confirm the same issue.
Thank you for this work around worked treat, I've been searching for a solution
to this issue for weeks.
No News of a proper fix for mdadm?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The trusty tag was added, due user comments.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Nested RAID levels aren't started after reboot
To manage notifications about this bug go to
The trusty tag was added, due user comments.
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Nested RAID levels aren't started after reboot
To manage notificatio
This is affecting me on 14.04 64-bit. I thought I was crazy. The
workaround works but I was hoping to have a steady system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Nested RAID l
I have a hybrid nested RAID5 (3x 3TB + 2x 1.5TB (RAID0)) and this bug
affects me. The solution posted by tarantoga works for me. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Probably just a glitch in the matrix :P
Anyway - I think this should go in, even without it being in initrd. I
would guess very few use nested raids for their root…
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
I do not see a message like "The disk drive for /... is not ready yet or
not present" on my system. I'm using a "real" installation (no VM) of
14.04.1 on a spinning disk and I do not use lvm. I'm guessing that this
message appears because lvm has to wait for mdadm to assemble the raid.
--
You rec
Thank you for this.
Tested in a 14.04 VM, created two 3-drive raid-5s (md0 and md1) and a
raid-0 on top (md10), added them to mdadm.conf, added the udev rule, ran
update-initramfs -u, put a vg+lv on md10, put a filesystem on the lv,
filled up with some bogus data, rebooted, works. Unpacked the ini
** Attachment added: "/etc/udev/rules.d/85-mdadm.rules"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1171945/+attachment/4176464/+files/85-mdadm.rules
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
I am also affected by this regression.
It looks like Wheezy disables udev for md and uses an rc-script for assembling
at boot; therefore it will not automatically assemble arrays after boot.
Trusty assembles real devices during and after boot, but seems to ignore
virtual devices like /dev/md0.
The solution to this bug is to run Debian :P
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Nested RAID levels aren't started after reboot
To manage notifications about this bug go to
Please fix this bug, we have to do horrible things to work around this
problem!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Nested RAID levels aren't started after reboot
To manage
Still just as bad as earlier. Do any developers even read this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Nested RAID levels aren't started after reboot
To manage notifications a
Confirmed on current 14.04 as well. Isn't nested raids meant to be
supported on ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Nested RAID levels aren't started after reboot
T
perhaps we're disagreeing on top and bottom here. with a raid 0-1, with
raid-0 being the initial devices setup and a raid-1 set across those, I
name the latter the lower level.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
RoyK, how does that work? How does the top level raid assemble when the
lower level devices aren't present?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Nested RAID levels aren't st
What I'm seeing is that the top level assembles correctly, but the lower
one(s) do not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Nested RAID levels aren't started after reboot
T
I'm able to get the nested RAID to work by booting into recovery mode,
using the recovery menu to drop to a shell and running 'mdadm -As'
('mdadm --assemble --scan') then exiting the shell and selecting to
continue a normal boot. There does not seem to be a way to boot non-
interactively and have
Hello? Are bugs like this one ignored by Canonical etc?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Nested RAID levels aren't started after reboot
To manage notifications about thi
Can someone please explain where Precise and later versions assemble the
RAIDs? This test raid is not part of the root.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Nested RAID level
Just tried to reproduce bug on Debian Wheezy, and couldn't. Wheezy
assembles the nested raid without issues. Talked to xnox on #ubuntu-
bugs, and he told me to look into mdadm's udev rules. I did, and
compared it with the one in Wheezy, and the difference is pasted below.
If I change the first line
John, I think you may have a different problem that probably deserves a
new bug report -- RoyK's problem is specifically with nested md devices.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
T
anyone working on this one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Nested RAID levels aren't started after reboot
To manage notifications about this bug go to:
https://bugs.la
This also toasted my newly created raid-1 array the other day.
Details:
Ubuntu 12.04 64 bit
intel core i3 CPU
Two 2TB WDEARX20 green drives (SATA)
upon updating to 3.2.0-40-generic kernel, boot results in blank purple
screen and md0 array is degraded, ejected one of the drives.
If I choose 3.2
I seriously doubt this is related to CPU architecture. It works on Lucid
AMD64, but it's broken on Precise and later. I guess this is part of the
mdadm assembly, and AFAIK this is done in the startup scripts, but then,
I have no idea where…
--
You received this bug notification because you are a
All I found till now points to a problem with AMD64 CPUs
http://ubuntuforums.org/showthread.php?t=2140322
http://www.ubuntu-forum.de/artikel/61514/kernel-upgrade-3-2-0-39-generic-system-bootet-nicht-mehr.html
Although I use the generic 32bit kernel, I also have an AMD64
processor!
--
You receive
It crashed my RAID-1 on 2 SATA disks and ext4 FS, including filesystem damage.
It affected me after Kernel Update to Ubuntu 3.2.0-40-generic-pae (32bit)
(with 3.2.0.23 it worked fine)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
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/1171945
Title:
Nest
Also affecting my 3x2 8.0 GB RAID5+0 USB array in Ubuntu Server 12.10
64-bit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171945
Title:
Nested RAID levels aren't started after reboot
To manage n
33 matches
Mail list logo
