We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Sorry no-one dealt with your issue. Unfortunately, Feisty is no longer
supported, can you reproduce this is a supported version of Ubuntu,
preferably Jaunty? Thank you.
** Changed in: mdadm (Ubuntu)
Status: New => Incomplete
--
mdadm + dm-raid: overrides previous devices due to good homeh
After further investigation today, and discussion with colleague, it is
possible that this has been caused by creating the array manually using the
mdadm command, then subsequently, when rebooted detects and starts the array.
However, when adding the new drive and growing the array, it reads in t
Also worth mentioning (not explicitly mentioned above), it is a default
configuration, including mdadm.conf:
[EMAIL PROTECTED]:~# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD
