From: Jason White <jason@jasonjgw.net>
To: xfs@oss.sgi.com
Subject: Re: grub fails boot after update
Date: Thu, 3 Jul 2008 14:47:55 +1000 [thread overview]
Message-ID: <20080703044755.GA13630@jdc.jasonjgw.net> (raw)
In-Reply-To: <486C4D7E.8060608@sandeen.net>
On Wed, Jul 02, 2008 at 10:54:38PM -0500, Eric Sandeen wrote:
> This really is grub that is busted, but I'd still just suggest using
> ext3 to (mostly) work around the breakage for the foreseeable future.
>
> The other option is to teach grub to always do its io via the filesystem
> not the block device while the fs is mounted (IIRC there are various &
> sundry non-intuitive commands which actually nudge grub towards or away
> from this desired behavior... --with-stage2=/path is one I think,
> skipping the "verification" phase (i.e. trying to read the block dev
> while mounted) is another)
Does grub 2 (still in development when last I checked) improve on this
situation?
I managed to get Grub 1 installed on machines with XFS root file systems by
running the install from within the grub "shell" environment rather than using
grub-install. Maybe this skips the checks that attempt to read the block
device directly. I also recall that grub-install failed.
next prev parent reply other threads:[~2008-07-03 4:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 15:15 grub fails boot after update Jan Engelhardt
2008-07-01 15:55 ` Christoph Hellwig
2008-07-03 3:54 ` Eric Sandeen
2008-07-03 4:47 ` Jason White [this message]
2008-07-03 14:49 ` Eric Sandeen
2008-07-05 20:11 ` Martin Steigerwald
-- strict thread matches above, loose matches on Subject: below --
2008-07-05 20:11 Martin Steigerwald
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=20080703044755.GA13630@jdc.jasonjgw.net \
--to=jason@jasonjgw.net \
--cc=xfs@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox