*** This bug is a duplicate of bug 191119 ***
https://bugs.launchpad.net/bugs/191119
Attempted to recreate this failure and was unable to do so.
Following as closely as I could to Alvin's description, I had a system
running Karmic with a root partition and a second data partition. I
moved all data from the data partition to a safe location. I added two
disks and using mdadm created a 3 disk software RAID 5 array, mounted
that, and moved my data onto the newly created array.
I rebooted to verify the array was intact after a reboot and autostart,
and verified that the test data was still present.
I then did a Lucid Install to this system, installing to the first partition on
sda (again, recreating Alvin's description step by step).
Of note, partman did NOT indicate that my existing RAID partitions were ext4,
in fact, it showed nothing for their type.
Lucid install completed successfully, and afterwards I was able to
rebuild the array, configure my new Lucid install to automount that
array and was able to verify that my original data (which lived on the
array throughout this new install process) was still there and viable.
The only thing I saw of note was that, on rebuilding the array after the
Lucid install, mdadm showed the array started in a degraded state with
the first two partitions as active, and the third as a spare in a
rebuilding state. Once the rebuild was complete, everything seemed just
fine.
So unable to confirm, and unable to recreate on my end.
--
Non-selected Raid Array Corruption from Installer
https://bugs.launchpad.net/bugs/568183
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.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
