Your message dated Fri, 28 Mar 2008 14:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#441080: fixed in grub 0.97-35
has caused the Debian Bug report #441080,
regarding grub-install shouldn't rely on /etc/mtab (via df) to find out the 
root partition
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.)


-- 
441080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441080
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: grub
Version: 0.97-29
Severity: normal

I was doing some partition handling on my laptop and due to that my root
partition got renumbered (hda6 -> hda5). When I rebooted Grub failed to
load so I started on a Debian CD in rescue mode.

When I wanted to re-run 'grub-install (hd0)' it failed with:
The file /boot/grub/stage1 not read correctly.

First the message is not correct english, it lacks a verb. And even then,
it's not clear what's wrong. Apparently it uses grub to extract the file
that he just put in place and verify that they are the same.

The underlying problem was that it wasn't able to extract the file because
find_device uses "df" to find out the partition associated to a given directory
and df in turn uses /etc/mtab.

In that case, since I was in an emergency shell, /etc/mtab wasn't properly
updated and furthermore it contained outdated information pointing to the
old name of the root filesystem.

I had /proc mounted and it should have used /proc/mounts to identify the
device before eventually falling back to something else like df.


For reference, here's the code that I'm referring to:

find_device () {
    # For now, this uses the program `df' to get the device name, but is
    # this really portable?
    tmp_fname=`df $1/ | sed -n 's%.*\(/dev/[^   ]*\).*%\1%p'`

[...]

# Get the root drive.
root_device=`find_device ${rootdir}`


Cheers,

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-1-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages grub depends on:
ii  libc6                     2.6.1-2        GNU C Library: Shared libraries
ii  libncurses5               5.6+20070825-1 Shared libraries for terminal hand

grub recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: grub
Source-Version: 0.97-35

We believe that the bug you reported is fixed in the latest version of
grub, which is due to be installed in the Debian FTP archive:

grub-disk_0.97-35_all.deb
  to pool/main/g/grub/grub-disk_0.97-35_all.deb
grub-doc_0.97-35_all.deb
  to pool/main/g/grub/grub-doc_0.97-35_all.deb
grub-legacy-doc_0.97-35_all.deb
  to pool/main/g/grub/grub-legacy-doc_0.97-35_all.deb
grub_0.97-35.diff.gz
  to pool/main/g/grub/grub_0.97-35.diff.gz
grub_0.97-35.dsc
  to pool/main/g/grub/grub_0.97-35.dsc
grub_0.97-35_amd64.deb
  to pool/main/g/grub/grub_0.97-35_amd64.deb
multiboot-doc_0.97-35_all.deb
  to pool/main/g/grub/multiboot-doc_0.97-35_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Robert Millan <[EMAIL PROTECTED]> (supplier of updated grub package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Fri, 28 Mar 2008 14:27:07 +0100
Source: grub
Binary: grub grub-disk grub-doc grub-legacy-doc multiboot-doc
Architecture: source amd64 all
Version: 0.97-35
Distribution: unstable
Urgency: low
Maintainer: Grub Maintainers <[EMAIL PROTECTED]>
Changed-By: Robert Millan <[EMAIL PROTECTED]>
Description: 
 grub       - GRand Unified Bootloader (Legacy version)
 grub-disk  - GRUB bootable disk image (dummy package)
 grub-doc   - Documentation for GRand Unified Bootloader (dummy package)
 grub-legacy-doc - Documentation for GRUB Legacy
 multiboot-doc - The Multiboot specification
Closes: 284790 301373 435708 441080 443897 450951 463274
Changes: 
 grub (0.97-35) unstable; urgency=low
 .
   * Upload to unstable.
 .
 grub (0.97-34) experimental; urgency=low
 .
   * patches/128gib_disk_limit.diff: Extend disk addressing up to 2 TiB.
     (Closes: #450951)
 .
 grub (0.97-33) experimental; urgency=low
 .
   * control (grub): Suggest multiboot-doc.
   * update-grub: Rewrite find_device() and convert() using grub-probe from
     grub-common package.  (Closes: #435708, #443897, #463274, #301373, #284790)
   * patches/use_grub-probe_in_grub-install.diff: Do the same for grub-install.
     (Closes: #441080)
Files: 
 b18b08fbea9f6cde0e5ebcbf70fba381 941 admin optional grub_0.97-35.dsc
 7e06aeeeea11d65d646dbe1cf332abb3 76780 admin optional grub_0.97-35.diff.gz
 db67a6b700f1b682f8bec6ba159a2c70 902882 admin optional grub_0.97-35_amd64.deb
 79efadb0dd46383954a5435b597b68a9 112944 admin optional 
grub-disk_0.97-35_all.deb
 8992e395b331699a0c608b3066e05ba1 112950 doc optional grub-doc_0.97-35_all.deb
 b7b36b164aa6dbeee7f3be3f2eba27d2 233994 doc optional 
grub-legacy-doc_0.97-35_all.deb
 59bec81423e4ba333f32175ee38258a5 158086 doc optional 
multiboot-doc_0.97-35_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH7P/VC19io6rUCv8RAskWAJ465APVT1M1GCVgI5gOYuu9Xg+I5gCffOJK
LLMix1+iIZCmu1GDtCqZ3Ww=
=0m8h
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to