Your message dated Tue, 10 Aug 2010 17:33:33 +0100
with message-id <20100810163332.gt12...@riva.ucam.org>
and subject line Re: Bug#548648: grub-pc jumps straight to rescue and prints 
error: no such disk / file not found
has caused the Debian Bug report #548648,
regarding grub-pc misdetects md RAID layout and fails to initialize
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.)


-- 
548648: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-pc
Version: 1.97~beta3-1
Justification: renders package unusable
Severity: grave

Hi,

I've upgraded from lenny to sid and tried to chainload, but sadly the new
version won't do anything useful for me. This is what it prints:

  Booting 'Chainload into GRUB 2'

root  (hd0,1)
 Filesystem type is ext2fs, partition type 0xfd
kernel  /boot/grub/core.img
   [Multiboot-kludge, loadaddr=0x100000, text-and-data=0x7aa4, bss=0x0, entry=0
x10027c]

Welcome to GRUB!

Entering rescue mode...
error: no such disk
grub rescue> 

>From there I can't even run 'help'. This sounds a bit like #502949 but
that's long been archived.

For reference, I have had a manual setup in the old menu.lst:

default         1
fallback        0
[...]
title Microsoft Windows
root (hd0,0)
makeactive
chainloader +1

title Debian GNU/Linux amd64
root (hd0,1)
kernel /boot/vmlinuz root=/dev/md0 reboot=warm resume=/dev/md1 
raid=noautodetect md=0,/dev/sda2,/dev/sdb2 md=1,/dev/sda5,/dev/sdb5 
md=2,/dev/sda6,/dev/sdb6

title Debian GNU/Linux i386
root (hd0,2)
kernel /boot/vmlinuz root=/dev/md0 reboot=warm resume=/dev/md1 
raid=noautodetect md=0,/dev/sda3,/dev/sdb3 md=1,/dev/sda5,/dev/sdb5 
md=2,/dev/sda6,/dev/sdb6

[...]

title           Chainload into GRUB 2
root            (hd0,1)
kernel          /boot/grub/core.img

[...]

I've tried to refresh it just in case:

% sudo grub-install --grub-setup=/bin/true /dev/md0
Installation finished. No error reported.                         
This is the contents of the device map /boot/grub/device.map.
Check if this is correct or not. If any of the lines is incorrect,
fix it and re-run the script `grub-install'.

(hd0)   /dev/sda
(hd1)   /dev/sdb

But there's no difference. I tried to add --modules="ext2 raid mdraid ntfs"
to make sure it has all the drivers, to no avail

Please help. TIA.

-- Package-specific info:

*********************** BEGIN /proc/mounts
/dev/root / ext3 rw,relatime,errors=remount-ro,data=writeback 0 0
/dev/md2 /home ext3 rw,relatime,errors=continue,data=writeback 0 0
/dev/sda1 /win ntfs 
ro,noexec,relatime,uid=1000,gid=1000,umask=022,nls=utf8,errors=continue,mft_zone_multiplier=1
 0 0
/dev/sdb1 /win2 fuseblk 
ro,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
 0 0
/dev/sda7 /bla1 vfat 
rw,noexec,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=cp852,iocharset=iso8859-2,showexec
 0 0
/dev/sdb7 /bla2 fuseblk 
rw,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
 0 0
/dev/sda8 /bla3 fuseblk 
rw,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
 0 0
/dev/sdb8 /bla4 ext3 rw,noexec,relatime,errors=continue,data=writeback 0 0
*********************** END /proc/mounts

*********************** BEGIN /boot/grub/device.map
(hd0)   /dev/sda
(hd1)   /dev/sdb
*********************** END /boot/grub/device.map

*********************** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
set default=0
insmod raid
insmod mdraid
insmod ext2
set root=(md0)
search --no-floppy --fs-uuid --set 7e6cdce7-8136-41f0-8a66-997b89ea00fe
if loadfont /usr/share/grub/unicode.pf2 ; then
  set gfxmode=640x480
  insmod gfxterm
  insmod vbe
  if terminal_output gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
  fi
fi
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod raid
insmod mdraid
insmod ext2
set root=(md0)
search --no-floppy --fs-uuid --set 7e6cdce7-8136-41f0-8a66-997b89ea00fe
insmod png
if background_image /boot/grub/moreblue-orbit-grub.png ; then
  set color_normal=black/black
  set color_highlight=magenta/black
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, Linux 2.6.30.4" {
        insmod raid
        insmod mdraid
        insmod ext2
        set root=(md0)
        search --no-floppy --fs-uuid --set 7e6cdce7-8136-41f0-8a66-997b89ea00fe
        linux   /boot/vmlinuz-2.6.30.4 root=/dev/md0 ro root=/dev/md0 
reboot=warm resume=/dev/md1 
}
menuentry "Debian GNU/Linux, Linux 2.6.30.4 (recovery mode)" {
        insmod raid
        insmod mdraid
        insmod ext2
        set root=(md0)
        search --no-floppy --fs-uuid --set 7e6cdce7-8136-41f0-8a66-997b89ea00fe
        linux   /boot/vmlinuz-2.6.30.4 root=/dev/md0 ro single root=/dev/md0 
reboot=warm resume=/dev/md1
}
menuentry "Debian GNU/Linux, Linux 2.6.30" {
        insmod raid
        insmod mdraid
        insmod ext2
        set root=(md0)
        search --no-floppy --fs-uuid --set 7e6cdce7-8136-41f0-8a66-997b89ea00fe
        linux   /boot/vmlinuz-2.6.30 root=/dev/md0 ro root=/dev/md0 reboot=warm 
resume=/dev/md1 
}
menuentry "Debian GNU/Linux, Linux 2.6.30 (recovery mode)" {
        insmod raid
        insmod mdraid
        insmod ext2
        set root=(md0)
        search --no-floppy --fs-uuid --set 7e6cdce7-8136-41f0-8a66-997b89ea00fe
        linux   /boot/vmlinuz-2.6.30 root=/dev/md0 ro single root=/dev/md0 
reboot=warm resume=/dev/md1
}
menuentry "Debian GNU/Linux, Linux 2.6.27.19" {
        insmod raid
        insmod mdraid
        insmod ext2
        set root=(md0)
        search --no-floppy --fs-uuid --set 7e6cdce7-8136-41f0-8a66-997b89ea00fe
        linux   /boot/vmlinuz-2.6.27.19 root=/dev/md0 ro root=/dev/md0 
reboot=warm resume=/dev/md1 
}
menuentry "Debian GNU/Linux, Linux 2.6.27.19 (recovery mode)" {
        insmod raid
        insmod mdraid
        insmod ext2
        set root=(md0)
        search --no-floppy --fs-uuid --set 7e6cdce7-8136-41f0-8a66-997b89ea00fe
        linux   /boot/vmlinuz-2.6.27.19 root=/dev/md0 ro single root=/dev/md0 
reboot=warm resume=/dev/md1
}
menuentry "Debian GNU/Linux, Linux 2.6.27.7" {
        insmod raid
        insmod mdraid
        insmod ext2
        set root=(md0)
        search --no-floppy --fs-uuid --set 7e6cdce7-8136-41f0-8a66-997b89ea00fe
        linux   /boot/vmlinuz-2.6.27.7 root=/dev/md0 ro root=/dev/md0 
reboot=warm resume=/dev/md1 
}
menuentry "Debian GNU/Linux, Linux 2.6.27.7 (recovery mode)" {
        insmod raid
        insmod mdraid
        insmod ext2
        set root=(md0)
        search --no-floppy --fs-uuid --set 7e6cdce7-8136-41f0-8a66-997b89ea00fe
        linux   /boot/vmlinuz-2.6.27.7 root=/dev/md0 ro single root=/dev/md0 
reboot=warm resume=/dev/md1
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
        linux   /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
        linux   /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Microsoft Windows XP Professional (on /dev/sda1)" {
        insmod ntfs
        set root=(hd0,1)
        search --no-floppy --fs-uuid --set 1460509560508002
        drivemap -s (hd0) ${root}
        chainloader +1
}
### 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 ###
*********************** END /boot/grub/grub.cfg

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30.4 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=hr_HR, LC_CTYPE=hr_HR (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/dash

Versions of packages grub-pc depends on:
ii  debconf [debconf-2.0]       1.5.27       Debian configuration management sy
ii  grub-common                 1.97~beta3-1 GRand Unified Bootloader, version 
ii  libc6                       2.9-26       GNU C Library: Shared libraries
ii  ucf                         3.0022       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
ii  genisoimage                   9:1.1.9-1  Creates ISO-9660 CD-ROM filesystem

-- debconf information:
  grub2/kfreebsd_cmdline:
* grub2/linux_cmdline: root=/dev/md0 reboot=warm resume=/dev/md1
* grub-pc/chainload_from_menu.lst: true
  grub-pc/kopt_extracted: true
  grub-pc/install_devices:
  grub-pc/postrm_purge_boot_grub: false
  grub2/kfreebsd_cmdline_default: quiet
* grub2/linux_cmdline_default:

-- 
     2. That which causes joy or happiness.



--- End Message ---
--- Begin Message ---
Source: grub2
Source-Version: 1.98+20100804-1

On Wed, Aug 04, 2010 at 06:17:34PM +0200, Josip Rodin wrote:
> On Wed, Aug 04, 2010 at 02:53:22PM +0100, Colin Watson wrote:
> > This all sounds awfully like the problems with array numbering which I
> > fixed recently.  Are you in a position to re-test with grub-pc
> > 1.98+20100804-1 from unstable?
> 
> Sorry, no, in the meantime I had removed my extra i386 partition.
> Feel free to close if you think it's fixed, it can always be reopened later.

OK, fair enough, and as you say.  Closing for now.

Thanks,

-- 
Colin Watson                                       [cjwat...@debian.org]


--- End Message ---

Reply via email to