From: Eric Sandeen <sandeen@sandeen.net>
To: xfs@oss.sgi.com
Subject: Re: grub fails boot after update
Date: Thu, 03 Jul 2008 09:49:29 -0500 [thread overview]
Message-ID: <486CE6F9.7000003@sandeen.net> (raw)
In-Reply-To: <20080703044755.GA13630@jdc.jasonjgw.net>
Jason White wrote:
> 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?
No idea. Does anyone use grub2? My impression is that each distro is
currently just maintaining a fork of grub(1). If grub2 is using more
than "sync and hope" I'd be pleasantly surprised. :)
> 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.
Yep, this might be some of the "magic" I talked about w.r.t. behavior of
different grub incantations.
-Eric
next prev parent reply other threads:[~2008-07-03 14:48 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
2008-07-03 14:49 ` Eric Sandeen [this message]
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=486CE6F9.7000003@sandeen.net \
--to=sandeen@sandeen.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 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.