Bug#693674: Wheezy DI-b3 amd64 GRUB overlooks Win7
On Tue 27 Nov 2012 at 22:27:36 -0500, Lou Poppler wrote: On Thu, 22 Nov 2012, Brian Potkin wrote: On Thu 22 Nov 2012 at 01:37:02 -0500, Lou Poppler wrote: 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. It works for me. It worked for me too. The installation completed, and GRUB installed OK, dual-booting works. Good. I grabbed the installer logfiles from the unsuccessful beta-3 install, and from today's successful beta-4 install. If anyone wants any part of them, I can supply it. I have another issue with the new install, display problems, but I assume you might want me to start a new bug number for this ? There has been mention in recent weeks of some display problems(#605076 and #690586 are two such reports), not all necessarily related to each other. Your issue may be unconnected with them too. I'd suggest a search of the List archive and a new bug report if necessary. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693674: Wheezy DI-b3 amd64 GRUB overlooks Win7
On Thu, 22 Nov 2012, Brian Potkin wrote: On Thu 22 Nov 2012 at 01:37:02 -0500, Lou Poppler wrote: 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. It works for me. It worked for me too. The installation completed, and GRUB installed OK, dual-booting works. I grabbed the installer logfiles from the unsuccessful beta-3 install, and from today's successful beta-4 install. If anyone wants any part of them, I can supply it. I have another issue with the new install, display problems, but I assume you might want me to start a new bug number for this ? Thanks, Lou -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693674: Wheezy DI-b3 amd64 GRUB overlooks Win7
On Thu 22 Nov 2012 at 01:37:02 -0500, Lou Poppler wrote: 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. Strange. mail.msen.com accepted the mail from my server. On Mon, 19 Nov 2012 11:00:49 +, Brian Potkin wrote: : : 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]. I am not sure that would really help in general. In this case it would not have because the bug lay with d-i and not any of the GRUB scripts. : : 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. It does. You decline the offer to install GRUB to /dev/sda by answering 'No' and specifying where GRUB should go. 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. It works for me. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 +, 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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693674: Wheezy DI-b3 amd64 GRUB overlooks Win7
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. 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. 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'. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693674: Wheezy DI-b3 amd64 GRUB overlooks Win7
Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta3/amd64/iso-cd/debian-wheezy-DI-b3-amd64-netinst.iso Date: November 19, 2012, 01:00 UTC Machine: Dell Optiplex 770 Processor: dual Core3 intel Memory: Partitions: SCSI3 (0,0,0) (sda) - 250.1 GB ATA WDC WD2500AAKX-0 #1 Primary 125.1 GB B ntfs #2 Primary5.0 GB ext4 #3 Primary 100.0 GB ext4 #4 Primary 20.0 GB swap Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[E] 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. 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. 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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
