From: Edward Allcutt <emallcut@gleim.com>
To: grub-devel@gnu.org
Cc: 494589@bugs.debian.org
Subject: grub-setup fails with "error message = file not found"
Date: Wed, 13 Aug 2008 11:53:27 -0400 [thread overview]
Message-ID: <48A30377.2060707@gleim.com> (raw)
I initially reported this as Debian bug #494589 [0]
Felix Zielcke asked me to forward this report to this mailing list.
Reproduced with latest upstream SVN (rebuilt r1802 today).
Failing command:
grub-setup -vv --directory=/boot/grub --device-map=/boot/grub/device.map
'(hd0)' >grub-setup.log 2>&1
grub-setup.log is available at [1]
/boot/grub/core.img exists and was created normally by grub-install. I
looked at the parameters passed to grub-mkimage and it was using the
correct modules (ext2 gpt biosdisk). I've run sync and
unmounted/remounted /boot but that doesn't help.
grub-fstest seems to have no problem with reading from the filesystem:
# grub-fstest /dev/sda1 ls /grub/core.img
core.img
# grub-fstest /dev/sda1 blocklist /grub/core.img
655432+55,655487[0-414]
# grub-fstest /dev/sda1 cmp /grub/core.img /boot/grub/core.img; echo $?
0
/dev/sda is partitioned using GPT. /boot is a normal ext3 filesystem on
/dev/sda1.
I've made the MBR [2] and sda1 (about 38MB) [3] available.
Final note: this exact setup worked just fine when I installed this
system in mid-June. I can probably figure out the version of grub2 on
the install CD if that would help.
[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494589
[1] http://dev.teamgleim.com/~emallcut/grub2/grub-setup.log
[2] http://dev.teamgleim.com/~emallcut/grub2/sda.mbr.gz
[3] http://dev.teamgleim.com/~emallcut/grub2/sda1.gz
--
Edward Allcutt
next reply other threads:[~2008-08-13 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 15:53 Edward Allcutt [this message]
2008-08-13 16:44 ` grub-setup fails with "error message = file not found" Robert Millan
2008-08-13 17:04 ` Edward Allcutt
2008-08-13 17:28 ` Robert Millan
2008-08-13 19:12 ` Edward Allcutt
2008-08-13 17:03 ` Robert Millan
2008-08-13 17:54 ` Edward Allcutt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48A30377.2060707@gleim.com \
--to=emallcut@gleim.com \
--cc=494589@bugs.debian.org \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.