Bug#412355: grub2 tries to boot only OS with a wrong menu entry in grub.cfg

[Mahesh T. Pai]

Package: grub2
Version: 1.95-2
Severity: normal


This *may* be related to #390473

When I moved  a friend's system from grub to grub2,  there was a wrong
entry/stanza in  grub.cfg file, (wrong because there  was a mismatched
`}'  in there).   and it  was the  last entry  (outside the  ``### END
DEBIAN AUTOMAGIC KERNELS LIST'' line) in grub.cfg file.

Unfortunately,  grub2  tried  to  boot  the  OS  represented  in  this
particular  entry  instead of  booting  the  OSes  represented in  the
correct stanzas. There was no way of even getting a command line.

This is a problem I do  not want to reproduce*. But was solved between
2 and 3  AM, I fuzzily recall  that luckily, I had grub2  in the other
hard disk,  and setting that disk  as the primary boot  device gave me
access to  the command  line.  This created  add confusion  since this
meant grub2  recognised the  primary slave as  hda instead of  hdb (or
should it be `hd0 instead of hd1'?)

(*) You know  the difficulties when booting into  an OS which requires
    `chainloader+1' entries in grub.cfg.

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages grub2 depends on:
ii  debconf                     1.5.11       Debian configuration management sy
ii  libc6                       2.3.6.ds1-13 GNU C Library: Shared libraries
ii  liblzo1                     1.08-3       data compression library (old vers
ii  libncurses5                 5.5-5        Shared libraries for terminal hand

grub2 recommends no packages.

-- debconf information:
  grub2/numbering_scheme_transition: