Bug#693674: Wheezy DI-b3 amd64 GRUB overlooks Win7
Thanks for your reply -- for some reason it didn't arrive here as email,
but I found it tonight while looking in the debian-boot list archives.
On Mon, 19 Nov 2012 11:00:49 +0000, Brian Potkin wrote:
: On Mon 19 Nov 2012 at 02:09:47 -0500, Lou Poppler wrote:
:
: > Comments/Problems: This machine started with Win7 installation occupying
: > the entire disk. I resized the windows partition to 1/2 of the disk,
: > and installed wheezy into the new partitions [ /boot and / plus swap ],
: > which I created using manual partitioning in the installer.
: > When we got to the install GRUB phase, I see this message:
: > "[!] Install the GRUB boot loader on a hard disk
: > It seems that this new installation is the only operating system on this
: > computer. If so, it should be safe to install the GRUB boot loader to
: > the master boot record of your first hard drive."
:
: Bug#650819 maybe. Should be fixed in beta-4.
:
: > This is not what I want -- I want to set this up as dual-boot, win7/wheezy.
: > I said no to installing GRUB, and finished the install with no boot loader
: > changes. This should be a simple case for the installer to get right.
: > The manual for beta D-I doesn't steer me to any way to solve this, other
: > than to see the GRUB manual.
:
: Did you get that advice from section 6.3.6.1? I'd agree it is less
: helpful than intended.
Yes, exactly. The mention of black arts also makes me hesitant to interfere
when the automatic process gets it wrong. The GRUB ecosystem seems more
complicated, the more I try to understand it, with the various scripts
which probe and update and install, but aren't really discussed in the
mainline grub documentation sources, such as they are. Perhaps in section
6.3.6.2 where it says "See the grub manual for complete information."
there could be some hyperlink[s].
: > So now I'm trying to become enough of a GRUB
: > expert to be able to create a manual boot loader configuration that will
: > maybe result in a working dual boot.
:
: It's a pity you declined to install GRUB. At least you should have got a
: bootable system from which to attempt to get the missing entry into the
: GRUB menu.
It's too bad the ISO doesn't provide a way to boot into the completed
installation, without overwriting the disk's MBR. I would be more
confident to experiment with GRUB configurations and probing if I could
see what it was trying to install before I commit to it. I don't want
to lose the ability to boot the existing Win7 system on my wife's computer.
: You could consider a reinstall. Then boot into the new system and run
:
: update-grub
:
: as root.
:
: Alternatively, you could boot the netinst ISO in Rescue mode. From there
: you can reinstall GRUB and get a shell to use 'update-grub'.
I see that the beta-4 version is available today. I'll grab that, and try
it out to see if it will work automatically.
--
Don't anthropomorphize computers. They don't like it.
Reply to: