Your message dated Sun, 11 Aug 2013 12:25:11 +0100
with message-id <[email protected]>
and subject line Re: Bug#707653: grub2-common: After Grub 2.00-14 upgrade,
system failed to boot (rescue, old grub 1.99 still in mbr)
has caused the Debian Bug report #707653,
regarding grub2-common: After Grub 2.00-14 upgrade, system failed to boot
(rescue, old grub 1.99 still in mbr)
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 [email protected]
immediately.)
--
707653: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707653
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: grub2-common
Version: 2.00-14
Severity: critical
Justification: breaks the whole system
Hi,
after upgrading grub from version 1.99-27.1 -> 2.00-14 [1] the system
was not able to boot.
On reboot the grub rescue>' prompt was displayed.
After
# grub rescue> set prefix=(hdX,>)/boot/grub/grub2
# grub rescue> insmod normal
# grub rescue> normal
the normal grub prompt was back, and there was still version 1.99-27
installed.
After another reboot i did:
# grub rescue> set root=(hdX,Y)/boot
# grub rescue> set prefix=(hdX,>)/boot/grub/grub2
# grub rescue> insmod part_msdos
# grub rescue> insmod ext2
# grub rescue> insmod linux
# grub rescue> linux /boot/vmlinuz-3.8-1-amd64 root=/dev/sdaX
# grub rescue> initrd /boot/initrd.img-3.8-1-amd64
# grub rescue> boot
so I was able to start the system.
After normal system start, I ran:
# grub-install /dev/sda
# update-grub
afterwards the system booted normally, grub was welcoming me now
with version 2.00.
It seems to me, that the grub-install, or whatever mechanism is used
internally to write the new grub, was not run on upgrade.
Regards,
Michael
[1] Grub related packages which got updated, no other grub packages installed.
- grub-common:amd64 1.99-27.1 -> 2.00-14
- grub-pc:amd64 1.99-27.1 -> 2.00-14
- grub-pc-bin:amd64 1.99-27.1 -> 2.00-14
- grub2-common:amd64 1.99-27.1 -> 2.00-14
-- System Information:
Debian Release: jessie/sid
APT prefers mike
APT policy: (700, 'mike'), (500, 'unstable'), (102, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.8-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages grub2-common depends on:
ii dpkg 1.16.10
ii grub-common 2.00-14
ii install-info 5.1.dfsg.1-3
grub2-common recommends no packages.
grub2-common suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, May 10, 2013 at 11:01:26AM +0200, Michael Musenbrock wrote:
> On Fri, May 10, 2013 at 09:06, Colin Watson wrote:
> > On Fri, May 10, 2013 at 08:44:57AM +0200, Michael Musenbrock wrote:
> > > Colin Watson wrote:
> > > > On Fri, May 10, 2013 at 12:46:19AM +0200, Michael Musenbrock wrote:
> > > > > It seems to me, that the grub-install, or whatever mechanism is used
> > > > > internally to write the new grub, was not run on upgrade.
> > > > [snip]
> > > > Could you please run:
> > > >
> > > > /usr/share/reportbug/handle_bugscript /usr/share/bug/grub-pc-bin/script
> > > > grub.out
> > > >
> > > > ... and attach the grub.out file created by that command, as well as the
> > > > output of 'sudo debconf-show grub-pc'?
> > >
> > > I've attached those files.
> >
> > Please answer "n" to the LVM question - answering "y" and then failing
> > to provide correct su authentication means that it gives me incomplete
> > output. (The script is a bit flaky now that I look at it.)
>
> And here we go again.
>
> yfji, I ran the script as root on the first run, so definitely no su auth
> failure, but missing lvm command errors instead, which seems to mess up
> the output as well.
Thanks. (I've made the script more robust for my next upload.)
I'm afraid this seems to be user error (or possibly an error in the way
your system was originally installed, which is certainly possible but
rather hard for the grub-pc package to recover from). The configuration
stored in debconf for grub-pc thinks that your boot loader resides on
/dev/disk/by-id/ata-ST3250620NS_9QE327VR, i.e. /dev/sdb, while your
original report indicates that you needed to write the boot loader to
/dev/sda. Unfortunately there is no way for the GRUB packaging to know
which device your system boots from; it is not reliably /dev/sda on BIOS
systems, for instance. In fact it's even possible that it varies from
boot to boot.
My usual advice on multiple-disk BIOS systems is to install the boot
loader to the master boot record of all fixed disks that are present.
In this case that would appear to be /dev/sda, /dev/sdb, and /dev/sdc.
You can cause this to happen for all future upgrades by running
"dpkg-reconfigure grub-pc" and selecting the MBR of each fixed disk.
Regards,
--
Colin Watson [[email protected]]
--- End Message ---
