On Sep 7, 2012, at 1:51 AM, Herbert Kaminski wrote:
Comments/Problems: 2. The installation did not detect the existing Lubuntu 10.04 and wanted to install grub into the master boot record (I did not allow that). 3. the grub installer was unable to install grub into any partition of the harddisk, encrypted or not. So I could not boot into wheezy.4. Manually editing the configuration of the existing grub-legacy in themaster boot record, I was able to boot into wheezy. So, grub seems to be the only problem of wheezy, at least for me.
I think this is the same as bug#684265, which I submitted a while back for a PowerPC install using Beta1.
See Bug#686471 for a workaround, if you've got a spare USB flash stick you can use to put the lilo bootloader on.
Quote from that bugreport...
Fortunately, the amd64 grub boot loader creation script did some self-checking, and noticed that there was only one OS in the setup it was about to write. It asked me if I wanted to write a MBR that I'd only have to re-do later to pick up the other OS's (if any). I decided to see if there were other options and answered "no". It then asked if I wanted to write the boot block to the partition I was installing to. I said "yes" but that failed for some reason (I don't remember the error message, and I don't think it was helpful even if I could remember.) So then I tried using lilo to a second USB stick. That worked and booted fine. If I booted without the USB stick, it booted to the previous default OS. "Cool!" that there's a workaround, but "Uncool!" that it's so roundabout! I'll be happy to supply the syslog file if you want to take a look.
RickPS: Is anybody working on this bug? It would be a shame if it got into beta2... I'd be happy to take a look and see if I could find anything, but I don't know where to look. Can somebody point me in the right direction? Thanks in advance!