> Why rebuilding /sbin/mdadm & /sbin/mdmon? Both are provided in the
standard package.
The versions in the old standard package are not able to handle 'BIOS
RAID' (aka 'fakeraid') metadata. And therefore booting such volumes
relies on the old and crufty dmraid tools.
--
You received this bug
Since I've upgraded to 13.10, my raid5 on the intel software raid
doesn't mount with the dmraid. I use an older 3.8 kernel I was using on
my 13.04.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1241086
Continues to not work for me. But at the initramfs prompt I'm able to manually
mount
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/1054948
Title:
Re: Brian Candler
Thanks for that. Why rebuilding /sbin/mdadm /sbin/mdmon? Both are
provided in the standard package.
Also I'd expect for you to revert initramfs-tools scripts which
generate, filter and replace a different mdadm.conf file into initramfs.
--
You received this bug notification
In comment #9, xnox says:
(b) grab upstream mdadm.udev rules and drop them into
/etc/udev/rules.d/ with same file name as the one in /lib/udev/rules.d/
Taking upstream as git://neil.brown.name/mdadm, it contains two udev
rules. Combining them in a way which matches the Ubuntu ones, I get the
As an experiment, I did the following:
* rebuild /sbin/mdadm and /sbin/mdmon from source, install in /sbin
* vi /usr/share/initramfs-tools/hooks/mdadm
- add copy_exec /sbin/mdmon /sbin
* vi /lib/udev/rules.d/64-md-raid.rules
-
Aside: also just tried booting from 13.10beta2 ISO in rescue mode.
It is still not using mdadm. It sees /dev/mapper/isw_XX_Volume0
but not /dev/mapper/isw_XX_Volume0p1.
As a result it did not offer this as a root filesystem for the rescue
shell; and I couldn't see how to rescan
I am just wondering if mdadm will add support for promise metadata - as
it would be required by AMD RAID controllers ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054948
Title:
dmraid broken for
Ah. Forgot to mention more related to this bug.
I am using a 990FX chipet and have connected two 3TB drives to the RAID
controller.
I am using Ubuntu 12.10 and if I now create a RAID on those 3TB drives, it does
not matter if it only has a size of 2TB or 1TB, it isn't recognized by dmraid
at
But wouldn't that simply only imply that dmraid and mdadm are not supposed to
co-exist? I'm a bit puzzled about this change. As far as I understand this, the
auto-assemble rules have been removed just to guarantee the function of dmraid
- temporarily or not.
Automated installation procedure
On 24 September 2012 11:09, Jan Kleinsorge jan.kleinso...@gmail.com wrote:
But wouldn't that simply only imply that dmraid and mdadm are not supposed to
co-exist? I'm a bit puzzled about this change. As far as I understand this,
the auto-assemble rules have been removed just to guarantee the
If co-existence of dmraid and mdadm would be just an incremental step
for later versions, exclusive-or would at least a step forward for mdadm
and I would be happy to test that (isms root + shutdown).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On 24 September 2012 15:46, Jan Kleinsorge jan.kleinso...@gmail.com wrote:
If co-existence of dmraid and mdadm would be just an incremental step
for later versions, exclusive-or would at least a step forward for mdadm
and I would be happy to test that (isms root + shutdown).
Ok. I will ping
Great.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054948
Title:
dmraid broken for large drives
To manage notifications about this bug go to:
How does one migrate from dmraid to mdadm when using IMSM?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054948
Title:
dmraid broken for large drives
To manage notifications about this bug go to:
For new installations, mdadm should be the default. Migration is not
necessary, dmraid could be post-installed. As dmraid isn't under
development anymore and drive capacities and the kind of platform won't
go away, this will sooner rather than later become a widespread critical
issue.
--
You
The problem was that after upgrading mdadm, previously working systems
with dmraid fail to boot due to fighting over isms raid drives with
mdadm. There are still many formats supported by dmraid that are not
supported by mdadm, somehow we need to make two co-exist happily.
--
You received this
hence the later upload of disabling auto-assembly of isms drives in
mdadm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054948
Title:
dmraid broken for large drives
To manage notifications about
Just for reference, with disable auto-assembly you mean the changes in mdadm
3.2.5-1ubuntu0.2 (#1030292)?
Would one be required to set up custom udev rules or which package version
contains rules for mdadm auto-assembly?
--
You received this bug notification because you are a member of Ubuntu
the 1030292 removed incremental udev rules based auto assembly of
external metadata raid arryas, isms and ddf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054948
Title:
dmraid broken for large
within the mdadm package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054948
Title:
dmraid broken for large drives
To manage notifications about this bug go to:
21 matches
Mail list logo
