[Bug 1171945] Re: Nested RAID levels aren't started after reboot

2014-08-14 Thread tarantoga
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 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.launchpad.net/ubuntu/+source/mdadm/+bug/1171945/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1171945] Re: Nested RAID levels aren't started after reboot

2014-08-13 Thread tarantoga
** 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.net/bugs/1171945

Title:
  Nested RAID levels aren't started after reboot

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1171945] Re: Nested RAID levels aren't started after reboot

2014-08-13 Thread tarantoga
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.

So I added a new rule for virtual devices to the existing udev rules in
Trusty. I created /etc/udev/rules.d/85-mdadm.rules with this single line
rule:

SUBSYSTEM=="block", ACTION=="add|change",
ENV{ID_FS_TYPE}=="linux_raid_member", DEVPATH=="*/virtual/*",
RUN+="/sbin/mdadm --incremental $tempnode"

This rule (plus the existing ones) assemble my nested raid during boot
or any time later, but might not work for the root filesystem unless a
initramfs-tools/hooks script is created (not tested).

-- 
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.launchpad.net/ubuntu/+source/mdadm/+bug/1171945/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs