Good catch, it appears this is caused by this:
dmraid (1.0.0.rc14-2ubuntu9) intrepid; urgency=low
* debian/control: dmraid and dmraid-udeb should depend on dmsetup and
dmsetup-udeb respecitvely, to ensure UUID symlinks are correctly
created.
* debian/patches/07_isw-raid10-nested.dpatch: Re-add this patch as a user
is not able to make use of his RAID array without it. Yes its known
to break other RAID configurations, however there have been no Ubuntu
bugs filed about this issue. (LP: #276095)
** Changed in: dmraid (Ubuntu)
Importance: Undecided => Medium
Status: New => Triaged
** Tags added: regression
** Tags added: regression-release
** Tags removed: regression
--
Raidset stays inactive due to wrong # of devices
https://bugs.launchpad.net/bugs/292302
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
