Am Montag, den 21.06.2010, 00:27 +0200 schrieb Paul Menzel: > Am Sonntag, den 20.06.2010, 22:41 +0100 schrieb Colin Watson: > > On Sat, Jun 19, 2010 at 11:13:45AM +0200, Paul Menzel wrote: > > > Am Freitag, den 18.06.2010, 13:18 +0100 schrieb Colin Watson: > > > > On Wed, Jun 16, 2010 at 09:16:16PM +0200, Paul Menzel wrote: > > > > > Now the message »Welcome to GRUB!« is shown and the machine reboots > > > > > immediately. I tried to press Shift but could not get into the command > > > > > line. > > […] > > > When GRUB boots, its boot sector first loads its "core image", which is > > usually embedded in the gap between the boot sector and the first > > partition on the same disk as the boot sector. This core image then > > figures out where to find /boot/grub, and loads grub.cfg from it as well > > as more GRUB modules. > > > > The thing that tends to go wrong here is that the core image must be > > from the same version of GRUB as any modules it loads. /boot/grub/*.mod > > are updated only by grub-install, so this normally works OK. However, > > for various reasons (deliberate or accidental) some people install GRUB > > to multiple disks. In this case, grub-install might update > > /boot/grub/*.mod along with the core image on one disk, but your BIOS > > might actually be booting from a different disk. The effect of this > > will be that you'll have an old core image and new modules, which will > > probably blow up in any number of possible ways. > > > > (Quite often, this problem lies dormant for a while because GRUB happens > > not to change in a way that causes incompatibility between the core > > image and modules. There was such a change on 2010-06-10 upstream, > > though, and so suddenly lots of people had serious problems brought to > > their attention all in one go. It's not really the fault of any recent > > change, but rather an ongoing problem.) > > > > There are a few things that strike me as suspicious about your setup. > > Firstly, you have /boot on /dev/md0, which is presumably a RAID device > > assembled from partitions on multiple disks, yet there's only one device > > in /boot/grub/device.map according to your original report. Then, in > > your most recent message to this bug, you seem to have edited > > /boot/grub/device.map to include both /dev/hda and /dev/sda, which seems > > a little surprising. What disks do you really have in your system? > > > > Your original report says "debconf information excluded", which is a > > shame since there's a vital piece of information there. What does > > 'debconf-show grub-pc | grep install_devices' say? > > I am sorry. I could not boot the system/access the Ext4 partition back > then (remember the PS in my second message). So I used reportbug on a > different system and thought excluding debconf information would exclude > all system specific information and I did not bother to check when I > composed the message. :( > > I am including the reportbug information in this message now. I am sorry > for the inconvenience.
I ran `sudo grub-install /dev/sda` and the system boots correctly now.
But I do not know why `sudo update-grub` did not work. Probably what you
explained above.
(Two more question below.)
> -- Package-specific info:
>
> *********************** BEGIN /proc/mounts
> /dev/disk/by-uuid/582643ad-cb1e-4a01-bca4-5c8ad8562447 / ext4
> rw,relatime,errors=remount-ro,barrier=1,data=ordered 0 0
> *********************** END /proc/mounts
>
> *********************** BEGIN /boot/grub/device.map
> (hd0) /dev/hda
Where does this come from? `blkid` only lists `/dev/sda[15]`. Is it the
CD/DVD drive?
> (hd1) /dev/sda
> *********************** END /boot/grub/device.map
>
> *********************** BEGIN /boot/grub/grub.cfg
> #
> # DO NOT EDIT THIS FILE
> #
> # It is automatically generated by grub-mkconfig using templates
> # from /etc/grub.d and settings from /etc/default/grub
> #
>
> ### BEGIN /etc/grub.d/00_header ###
> if [ -s $prefix/grubenv ]; then
> load_env
> fi
> set default="0"
> if [ "${prev_saved_entry}" ]; then
> set saved_entry="${prev_saved_entry}"
> save_env saved_entry
> set prev_saved_entry=
> save_env prev_saved_entry
> set boot_once=true
> fi
>
> function savedefault {
> if [ -z "${boot_once}" ]; then
> saved_entry="${chosen}"
> save_env saved_entry
> fi
> }
> if terminal_input console ; then true ; else
> # For backward compatibility with versions of terminal.mod that don't
> # understand terminal_input
> terminal console
> fi
> if terminal_output console ; then true ; else
> # For backward compatibility with versions of terminal.mod that don't
> # understand terminal_output
> terminal console
> fi
> set timeout=1
> ### END /etc/grub.d/00_header ###
>
> ### BEGIN /etc/grub.d/05_debian_theme ###
> set menu_color_normal=cyan/blue
> set menu_color_highlight=white/blue
> ### END /etc/grub.d/05_debian_theme ###
>
> ### BEGIN /etc/grub.d/10_linux ###
> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686' --class debian --class
> gnu-linux --class gnu --class os {
> insmod part_msdos
> insmod ext2
> set root='(hd1,msdos1)'
> search --no-floppy --fs-uuid --set 582643ad-cb1e-4a01-bca4-5c8ad8562447
> echo 'Loading Linux 2.6.32-5-686 ...'
> linux /boot/vmlinuz-2.6.32-5-686
> root=UUID=582643ad-cb1e-4a01-bca4-5c8ad8562447 ro parport=0
> init=/sbin/bootchartd quiet
> echo 'Loading initial ramdisk ...'
> initrd /boot/initrd.img-2.6.32-5-686
> }
> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-686 (recovery mode)' --class
> debian --class gnu-linux --class gnu --class os {
> insmod part_msdos
> insmod ext2
> set root='(hd1,msdos1)'
> search --no-floppy --fs-uuid --set 582643ad-cb1e-4a01-bca4-5c8ad8562447
> echo 'Loading Linux 2.6.32-5-686 ...'
> linux /boot/vmlinuz-2.6.32-5-686
> root=UUID=582643ad-cb1e-4a01-bca4-5c8ad8562447 ro single
> echo 'Loading initial ramdisk ...'
> initrd /boot/initrd.img-2.6.32-5-686
> }
> ### END /etc/grub.d/10_linux ###
>
> ### BEGIN /etc/grub.d/30_os-prober ###
> ### END /etc/grub.d/30_os-prober ###
>
> ### BEGIN /etc/grub.d/40_custom ###
> # This file provides an easy way to add custom menu entries. Simply type the
> # menu entries you want to add after this comment. Be careful not to change
> # the 'exec tail' line above.
> ### END /etc/grub.d/40_custom ###
>
> ### BEGIN /etc/grub.d/41_custom ###
> if [ -f $prefix/custom.cfg ]; then
> source $prefix/custom.cfg;
> fi
> ### END /etc/grub.d/41_custom ###
> *********************** END /boot/grub/grub.cfg
>
> -- System Information:
> Debian Release: squeeze/sid
> APT prefers unstable
> APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> Architecture: i386 (i686)
>
> Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages grub-pc depends on:
> ii debconf [debconf-2.0] 1.5.32 Debian configuration management
> sy
> ii grub-common 1.98+20100617-1 GRand Unified Bootloader,
> version
> ii libc6 2.11.2-1 Embedded GNU C Library: Shared
> lib
> ii libdevmapper1.02.1 2:1.02.48-2 The Linux Kernel Device Mapper
> use
> ii ucf 3.0025 Update Configuration File:
> preserv
>
> grub-pc recommends no packages.
>
> Versions of packages grub-pc suggests:
> ii desktop-base 5.0.5 common files for the Debian
> Deskto
>
> -- debconf information:
> grub-pc/kopt_extracted: false
> grub2/kfreebsd_cmdline:
> * grub-pc/install_devices: (hd0)
> grub-pc/postrm_purge_boot_grub: false
> * grub2/linux_cmdline:
> grub-pc/install_devices_empty: false
> grub2/kfreebsd_cmdline_default: quiet
> * grub2/linux_cmdline_default: parport=0 init=/sbin/bootchartd quiet
> grub-pc/chainload_from_menu.lst: true
> grub-pc/mixed_legacy_and_grub2: true
I do not know, how to interpret the debconf information. But GRUB Legacy
was never installed on this system.
Thanks,
Paul
signature.asc
Description: This is a digitally signed message part
