[Expired for mdadm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mdadm (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/332235
Ti
I concur, Clint.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/332235
Title:
RAID5 partitions disappear after initial reboot [old superblocks]
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
I suspect the two ARRAY definitions are rather confusing for mdadm.
Willow, your issue sounds very different, and is mostly a result of md's
"powerful" features which allow you to totally screw things up.
As such, and given that htis has gone so long without independent
confirmation, I am marking
Also "dmraid eats mdadm-managed raid in upgrading from 9.04 to 9.10" Bug
#442735
** Summary changed:
- RAID5 partitions disappear after initial reboot
+ RAID5 partitions disappear after initial reboot [old superblocks]
--
RAID5 partitions disappear after initial reboot [old superblocks]
https:
I've experienced a similar issue before.
I had a raid 6 array that I'd built with some disks, then, after it appeared to
be built okay, I grew it onto two more disks. Alas, the first set of devices
in the array were the partitions, the other two were, accidentally, the drives.
And somehow, the
# mdadm --version
mdadm - v2.6.7 - 6th June 2008
--
RAID5 partitions disappear after initial reboot
https://bugs.launchpad.net/bugs/332235
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
