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 RAID
(/dev/sda4 i.e.)
See above for examples. Then get the needed informations to create a new
RAID with exactly the old Layout.
1. Order of Drives
Number Major Minor RaidDevice State
this 1 3 65 1 active sync
Where Number is the Number of the Drive starting by zero. In my case,
/dev/sdc1 was the first member (Number = 0).
2. Raid Level
Raid Level : raid5
3. Layout
Layout : left-symmetric
4. ChunkSize
Chunk Size : 64K
With this information, I can recreate the RAID.
$ sudo mdadm /dev/md0 --stop // if it is running
$ sudo mdadm --create /dev/md0 --level=5 --raid-devices=4 /dev/hda1 /dev/hdb1
/dev/sda4 /dev/sdb1
Then it should start. You can watch the progress with
$ watch cat /proc/mdstat
After around an hour my RAID was recovered. All the data was still
accessible. Phew.
I will hope nobody else will step in this problem. BTW: With the last
kernel update (2.6.20.15-27) the naming scheme changed back to /dev/hd*
for PATA drives.
--
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 the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
