Should be fixed by this upload: (I don't close this bug yet, since I
haven't really tested it yet):
Changes:
mdadm (2.6.2-1ubuntu1) gutsy; urgency=low
.
* Merge from debian unstable:
- various Debian and Ubuntu changes dropped in favour of the changes
outlined below.
.
* md activation:
- We now have a single udev rule for both the real system and the
initramfs, since doing things differently there will only result in bugs
and confusion.
- This rule runs "mdadm --assemble --scan --no-degraded", automatically
activating any non-degraded device as their components are detected.
- Drop the mdadm-raid init script, since this does the same thing.
- Also drop mdadm-startall which uses the mdadm-raid init script, and its
associated sgml file (thus dropping the build-dep on docbook-to-man)
- Simplify the configuration, since we always autostart all devices so do
not need to specify any required root devices, etc.
- Drop the deprecated mdrun entirely.
- Since udev autostarts arrays, much of the initramfs script can be
dropped.
.
* Install a new udev rule at 65 which runs vol_id on clean raid arrays.
This will cause lvm, etc. to be run (since there is vol_id information
present for the enclosed filesystem).
.
* Depend on initramfs-tools, specifically a version that doesn't ship
the mdrun script. This way we can clean out a lot of the upgrade handling
from the initramfs hook.
* Just get initramfs to load the modules for us
--
Root fs on LVM on mdadm fails to boot
https://bugs.launchpad.net/bugs/87745
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
