Feisty is not supported anymore.
** Changed in: mdadm (Ubuntu)
Status: New => Invalid
--
Wrong RAID UUID on PATA RAID5 partitions after Feisty Upgrade
https://bugs.launchpad.net/bugs/107080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've opened up another bug for my other troubles, as they might not be
entirely related to the UUID problem:
https://bugs.launchpad.net/ubuntu/+bug/110304
--
Wrong RAID UUID on PATA RAID5 partitions after Feisty Upgrade
https://bugs.launchpad.net/bugs/107080
You received this bug notification be
As far as I know the UUID in mdadm.conf is the Device UUID for md0 which
is used in /etc/fstab to mount the drive. The UUID reported by mdadm
--examine is the UUID of the RAID Partition which must be the same for
all Members of a raid.
Could you please attach a copy of
/etc/mdadm/mdadm.conf
This also happened to me. I managed to start it by changing the UUID in
mdadm.conf to what was reported by mdadm --examine. I still have issues
though, hard crashes etc.
--
Wrong RAID UUID on PATA RAID5 partitions after Feisty Upgrade
https://bugs.launchpad.net/bugs/107080
You received this bug n
I succede in recovering my Partition. It's not clearly stated in the
manual, but you can recreate a RAID which Superblocks are messed up.
The most important part is to store the RAID Informations of each
partion at a safe place:
$ sudo mdadm --examine /dev/* // where * is every member of your
