Description of Problem: I've just experienced data loss attempting to do an installation while preserving pre-existing RAID partitions. The problem seems to be that Disk Druid doesn't assign raid device numbers in a way that matches the kernel's notion of existing raid devices. In fact, it appears to assign raid devices at random. It's not the order in which RAID devices are created, for example, which makes it even harder to make sure it's going to do The Right Thing (TM). In my case, the installer ended up formatting my 160GB RAID 5 ext3 filesystem as a RAID5 swap device, just because the installer decided to assign to the swap partition the md number that the kernel had already assigned to the ext3 filesystem. Oops :-) Steps to Reproduce: 1. Create a few RAID devices in one installation 2. Do another installation, but create the raid devices in a different order, but mark some partitions to not be formatted Actual Results: The preserved partitions aren't the same, and the raid devices aren't assigned as Disk Druid said they would. Expected Results: The partitions I asked to have preserved shouldn't have been touched. Ideally, Disk Druid should read the md device numbers from the kernel to assign them. Additional Information: For reference, here's how I partitioned the disks: for f in hda hdc hde hdg; do { echo rm 1; echo rm 2; echo rm 3; echo rm 4; echo mkpart primary ext3 0 32 echo mkpart extended 32 58644 echo mkpart logical ext3 32 4887 echo mkpart logical linux-swap 4887 5146 echo mkpart logical ext3 5146 58644 echo p; echo q; } | parted /tmp/$f for d in 1 5 6 7; do echo t; echo $d; echo fd; done; echo w; } | fdisk /tmp/$f done In disk druid, I'd create the devices in the order below. Nevertheless, the md numbers were assigned as shown after `->'. hd[aceg]1: RAID 1 /boot -> md3 hd[aceg]6: RAID 5 swap -> md2 hd[aceg]7: RAID 5 /l -> md0 hd[ae]5: RAID 1 / -> md1 hd[cg]5: RAID 1 /l/root -> md4
What tree was this with?
This is because we don't properly handle using previous RAID setups on a fresh install.
Dupe of (several?) other bugs. Will be addressed in a future release.
Deferring to future release.
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.