All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten <maarten@ultratux.net>
To: linux-raid@vger.kernel.org
Subject: Re: lilo boot problems
Date: Tue, 31 Aug 2004 02:22:23 +0200	[thread overview]
Message-ID: <200408310222.24563.maarten@ultratux.net> (raw)
In-Reply-To: <20040830082625.GA9916@apartia.fr>

On Monday 30 August 2004 10:26, Louis-David Mitterrand wrote:
> On Sat, Aug 28, 2004 at 12:44:55AM +0200, maarten wrote:
> > On Friday 27 August 2004 15:04, Laurent CARON wrote:
> > > maarten wrote:

>
> > > you have to reconstruct your array first.
> >
> > Eeh...  You're joking, right ?
> > The array holds no data as yet so it is possible, but several things seem
> > too odd about this advice.  First, there is nothing wrong with this
> > array, it was created by mdadm with all the right options. Second, this
> > being linux (not windows) I can hardly believe one has to solve problems
> > by no other means than starting all over ("reinstall windows") if the
> > only error is due to the bootmanager interacting with the kernel
> > (remember, this error doesn't occur with other, earlier, kernels).
> >
> > Anyway, I chose to work around it by installing grub (and it works fine).
>
> By "reconstruct" I think Laurent meant "synchronize". In effect,
> degraded arrays would produce that error with lilo with certain versions
> of kernel 2.6.x

Ah, okay.  This would make sense, yes.  But it creates a catch-22 situation 
because I can't add the missing drive to the array when I have booted off 
that single drive, and I can't boot off the array due to this lilo error.
Not that that can't be fixed...

Maarten


      reply	other threads:[~2004-08-31  0:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25 12:58 lilo boot problems maarten
2004-08-27 13:04 ` Laurent CARON
2004-08-27 22:44   ` maarten
2004-08-28  6:37     ` Laurent CARON
2004-08-30  8:26     ` Louis-David Mitterrand
2004-08-31  0:22       ` Maarten [this message]

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=200408310222.24563.maarten@ultratux.net \
    --to=maarten@ultratux.net \
    --cc=linux-raid@vger.kernel.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.