Your message dated Mon, 31 Aug 2009 10:01:57 +0200
with message-id <1251705717.3791.9.ca...@fz.local>
and subject line Re: Bug#544377: grub-common: broke grub1 install?
has caused the Debian Bug report #544377,
regarding grub-common: broke grub1 install?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
544377: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-common
Version: 1.97~beta1-1
Severity: critical
Somehow, it appears that upgrading grub-common to 1.97~beta1-1 has
caused my system to stop booting. I'm running an up-to-date sid system
(as of tonight) on a thinkpad x200s; grub1 was installed as the
bootloader.
grub-legacy 0.97-56 and grub-common 1.97~beta1-1 are the only grub
packages installed, with the dummy grub packaged marked 'rc'.
After dist-upgrading and rebooting, grub just hangs. The BIOS finishes
loading, and I get a blinking cursor.. but no grub menu. I don't get
any errors from grub either, so it looks like it's not even getting to
stage2. I last rebooted 10 days ago, and grub worked fine then. The
last reboot was a kernel upgrade (2.6.31-rcsomething), and neither grub
nor the MBR have been touched since then (other than routine package
upgrades via dist-upgrade).
I will boot from grub on a usb stick for the next few days and try and
leave everything as-is; if you don't ask me for additional info, I'll
go ahead and fix booting on the machine.
--- End Message ---
--- Begin Message ---
severity 544377 important
thanks
Am Sonntag, den 30.08.2009, 23:54 -0400 schrieb Andres Salomon:
> Package: grub-common
> Version: 1.97~beta1-1
> Severity: critical
>
> Somehow, it appears that upgrading grub-common to 1.97~beta1-1 has
> caused my system to stop booting. I'm running an up-to-date sid system
> (as of tonight) on a thinkpad x200s; grub1 was installed as the
> bootloader.
>
> grub-legacy 0.97-56 and grub-common 1.97~beta1-1 are the only grub
> packages installed, with the dummy grub packaged marked 'rc'.
>
> After dist-upgrading and rebooting, grub just hangs. The BIOS finishes
> loading, and I get a blinking cursor.. but no grub menu. I don't get
> any errors from grub either, so it looks like it's not even getting to
> stage2. I last rebooted 10 days ago, and grub worked fine then. The
> last reboot was a kernel upgrade (2.6.31-rcsomething), and neither grub
> nor the MBR have been touched since then (other than routine package
> upgrades via dist-upgrade).
>
> I will boot from grub on a usb stick for the next few days and try and
> leave everything as-is; if you don't ask me for additional info, I'll
> go ahead and fix booting on the machine.
>
That's completely impossible that updating grub-common breaks
grub-legacy, assuming you didn't do anything yourself.
The only thing grub-common does in the preinst is removing old files
from /etc/grub.d/ if you're upgrading from a version earlier then
1.96+20090521-1. These files are only relevant for update-grub from
grub2 which isn't in grub-common but in grub-pc and the other grub-*
packages.
There are no other maintainer scripts at all (i,e,
postinst,postrm,prerm)
There isn't even at all a program or script included in grub-common
which could overwrite your MBR.
grub-setup and grub-install are also in grub-pc and the other grub-*
packages.
Something else must have broken it.
And with `up-to-date sid system' I assume you upgraded from yesterdays
sid version 1.96+20090829-1?
If so then that's even more impossible because there aren't at all any
changes which could cause this.
GRUB Legacy is old and buggy don't use it anymore.
--- End Message ---
