Comment 13 for bug 560152

Hi, NickJ,

If I interpret Whoop correctly, his problem was that he tried to install Ubuntu to 2 separate machines while leaving his RAID /home partition alone on each. The end result was the installer goofed his install and gave him that "failed to remove conflicting files" message, but in both cases his /home RAID partition was undamaged. His end result was a botched install, on the first machine to sda1, and on the second machine to md0(?), but neither RAID /home directory had any problems.

Whoop, if this is not the case, please let me know.

In your case, NickJ, you also tried to install Ubuntu while leaving your RAID /home partition alone, but things diverge soon after that.

1. In your case, although you elected to not format or modify your RAID /home partition, the installer told you that the partition tables would be changed, anyway. Whoop makes no mention of this in his case. And he has screen shots of his install which also don't show anything abnormal.

2. In your case, the installer actually corrupted your RAID /home partition, despite you telling the installer not to touch it. This did not happen in Whoop's case.

This next part gets logically convoluted, but bear with me. You both started off with similar starting positions, and you both used similar procedures, but you had markedly different results. Therefore, there must be a different bug at play in your case. If you also received the "failed to remove conflicting files" error, it logically follows that you must have been blessed with two bugs. Lucky you!

Additionally, the results you mention in 1 and 2 above are cornerstones of the bugs I mentioned. See that first long email in bug 568183, which is currently a duplicate of bug 191119.

Long story short: it was likely *you* who fixed your second bug when you rebuilt your corrupted RAID arrays, and the fix to this bug fixed your remaining problem. BTW, how did you wind up recovering your RAID drives?