Comment 10 for bug 191119

Logic 101:
There is nothing in this report that would even remotely suggest that it's a GRUB problem. By your logic, it could be anything that writes directly to the hard drive, not just GRUB. While it's true that the absence of evidence is not evidence of absence, the absence of evidence *should* tell you to concentrate your effort on the evidence you *do* have. Following your logic, we should also create a separate bug report because it's possible that invaders from Mars, who have cunningly hidden themselves from us thus far, came down and corrupted the original reporter's RAID array right when he was installing Ubuntu. There's no evidence of that (just just there's no evidence it was a GRUB problem), but it *is* technically possible.

Also, there is plenty of evidence to suggest it *isn't* GRUB. As I mentioned in my emails several times:

1. GRUB only writes in the first few kilobytes of the disk, which is safely out of the way of the data. Any other GRUB stuff is written to a file system.
2. I've replicated the problem, and simply wiping the left over file system fixes it. If it were a GRUB problem, the problem would continue.

Additionally, if this issue were a separate GRUB problem:

3. Ubuntu 8.04 used GRUB version 1, which was extremely mature and well vetted by that point.
4. It would affect ALL distributions that use that version of GRUB, and ALL installs where the user has a RAID drive, and EVERY time the user installs GRUB. This is clearly not the case.
5. The installer actually installs GRUB on ALL of your hard drives (since it doesn't know which one will be active; some other OSs change the active drive at boot), so if that were true, ALL drives would have been corrupted. The reporter clearly stated that only one RAID drive was affected, and he just had to start in degraded mode and resync.

Please, stay in school. If you're not in school, go back.