Comment 9 for bug 186147

i had the same problem (with a copy of hardy from end of jan 08) and try now with alpha4.

however: this bug left the system with a blank boot partition and it could not boot other systems still present. this is ok for alpha software and i know how to recover.

the important issue here is, that this bug reveals that the installation process is not secure. it can leave the system in a state which it does not boot what was before (and still is) on the disk (eg. other Linux, windows). even if this bug is fixed, it would be worthwhile to rethink the order of the installation process: removing/blanking the /boot disk partition should come last, when a new boot partition is ready as an image to be written (it will not likely be possible to make this a database transaction 'commit' with a single action), thus reducing the possibility that the boot partition is blanked but not written with the new boot information, independent what the cause of interrupting the installation process.