Bug#564928: the mbr needs updating
Hmm, I seem to remember reading that with a direct EFI boot you lose out on all accellerated video (which of course is no use whatsoever!). If that is no longer the case, I guess I'm just seriously out of date with GRUB knowledge, and when I get some spare time i'll browse the documentation and have a play around! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#564928: the mbr needs updating
forcemerge 564928 554790 thanks Am Freitag, den 15.01.2010, 10:56 +0100 schrieb Vincent Fourmond: > severity 564928 important > thanks > > Hello, [...] > > OK, I understand the problem. I had changed the device (from IDE to > SATA using an adapter). Is there any way to detect that at postinst ? > Could somehow grub find out that a drive has changed its interface ? > (it can happen also if you change the SATA or IDE port, I believe, not > only in the tight corner case of changing the whole interface !). > > I've downgraded the severity to important, since it only happens in > very special cases. However, when that happens, it is guaranteed to be > a real pain... (especially since I only had old Knoppix versions that > would not recognize my SATA driver or my network card... Rather > delicate, I'd say). > > Thanks for the reply, > > Vincent Solution is to use /dev/disk/by-id. Then udev handles it for us. Good that Colin submitted now a patch for this, just hadn't yet time to look at it in detail. > PS: upon submission of the bug, I got a message saying that I didn't > have posting right the the pkg-grub mailing list. This should be > disabled, as bug reports definitely should arrive there, even from > unsubscribed addresses. Strange, because debbugs should be whitelisted and if the list didn't get your report I wouldn't have seen it. Anyway already reported as #563763 and also as #564536 against tech-ctte. -- Felix Zielcke Proud Debian Maintainer and GNU GRUB developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#564928: the mbr needs updating
Am Freitag, den 15.01.2010, 10:58 + schrieb Dennis 123321: > @Felix > > You said to run `sudo dpkg-reconfigure grub-pc' as the proper fix; Can > I get this to install to a partition instead? I have a Macbook Pro 13" > (5,5) and using legacy BIOS emulation boot /dev/sda3 (which contains > grub-pc manually installed)/ > Running your command, I only get the choice of /dev/sda which is not > appropriate for the Macbook partition scheme. GRUB 2 supports EFI so at least if you have an Intel Macbook it can load it directly (and can also boot Mac OS X). And then you won't have this problem at all. Else if you insist on using the BIOS version, you have to use something like (not at all tested) `echo SET grub-pc/install_devices /dev/sda3 | sudo debconf-communicate' or just clear the device from grub-pc/install_devices. But then it can happen that grub-mkconfig generates a grub.cfg which your installed GRUB doestn't like. -- Felix Zielcke Proud Debian Maintainer and GNU GRUB developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#564928: the mbr needs updating
@Felix You said to run `sudo dpkg-reconfigure grub-pc' as the proper fix; Can I get this to install to a partition instead? I have a Macbook Pro 13" (5,5) and using legacy BIOS emulation boot /dev/sda3 (which contains grub-pc manually installed)/ Running your command, I only get the choice of /dev/sda which is not appropriate for the Macbook partition scheme. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#564928: the mbr needs updating
severity 564928 important thanks Hello, On Fri, Jan 15, 2010 at 10:33 AM, Felix Zielcke wrote: > Am Mittwoch, den 13.01.2010, 14:08 + schrieb Dennis 123321: >> I had this issue this morning. It is caused by the installation of the >> new grub not updating the actual mbr, and only the files in >> /boot/grub/ >> >> It is a simple fix; >> as root, execute something like this after you install the new package >> for grub-pc. (changing the destination for your drive, this was __my >> exact command__ for my computer): >> >> # grub-install --no-floppy --recheck --force /dev/sda3 >> >> a more generic command may look like: >> >> # grub-install /dev/sda >> >> now, reboot, and it should boot perfectly. >> If you install the new grub-pc and forget to update the boot sector, >> you can chroot in and do it that way (thats what I did). > > The proper fix is to run `sudo dpkg-reconfigure grub-pc' and select the > device (or just all) in the debconf prompt for it, from which you boot. > Else grub-install gets run on the wrong the device and then this can > happen. > Only grub-install touches /boot/grub. The package postinst just runs it > if a device is stored in grub-pc/install_devices. > > @Vincent: > You're report shows grub-pc/install_devices has /dev/hda stored. > I assume that's not (anymore?) the device you boot from, else that > shouldn't happen. OK, I understand the problem. I had changed the device (from IDE to SATA using an adapter). Is there any way to detect that at postinst ? Could somehow grub find out that a drive has changed its interface ? (it can happen also if you change the SATA or IDE port, I believe, not only in the tight corner case of changing the whole interface !). I've downgraded the severity to important, since it only happens in very special cases. However, when that happens, it is guaranteed to be a real pain... (especially since I only had old Knoppix versions that would not recognize my SATA driver or my network card... Rather delicate, I'd say). Thanks for the reply, Vincent PS: upon submission of the bug, I got a message saying that I didn't have posting right the the pkg-grub mailing list. This should be disabled, as bug reports definitely should arrive there, even from unsubscribed addresses. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#564928: the mbr needs updating
Am Mittwoch, den 13.01.2010, 14:08 + schrieb Dennis 123321: > I had this issue this morning. It is caused by the installation of the > new grub not updating the actual mbr, and only the files in > /boot/grub/ > > It is a simple fix; > as root, execute something like this after you install the new package > for grub-pc. (changing the destination for your drive, this was __my > exact command__ for my computer): > > # grub-install --no-floppy --recheck --force /dev/sda3 > > a more generic command may look like: > > # grub-install /dev/sda > > now, reboot, and it should boot perfectly. > If you install the new grub-pc and forget to update the boot sector, > you can chroot in and do it that way (thats what I did). The proper fix is to run `sudo dpkg-reconfigure grub-pc' and select the device (or just all) in the debconf prompt for it, from which you boot. Else grub-install gets run on the wrong the device and then this can happen. Only grub-install touches /boot/grub. The package postinst just runs it if a device is stored in grub-pc/install_devices. @Vincent: You're report shows grub-pc/install_devices has /dev/hda stored. I assume that's not (anymore?) the device you boot from, else that shouldn't happen. Probable this should be merged with #554790 -- Felix Zielcke Proud Debian Maintainer and GNU GRUB developer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#564928: the mbr needs updating
I had this issue this morning. It is caused by the installation of the new grub not updating the actual mbr, and only the files in /boot/grub/ It is a simple fix; as root, execute something like this after you install the new package for grub-pc. (changing the destination for your drive, this was __my exact command__ for my computer): # grub-install --no-floppy --recheck --force /dev/sda3 a more generic command may look like: # grub-install /dev/sda now, reboot, and it should boot perfectly. If you install the new grub-pc and forget to update the boot sector, you can chroot in and do it that way (thats what I did). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
