mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 471] New: Root on software raid don't boot on new 2.5 kernel since after 2.5.45
Date: Wed, 19 Mar 2003 11:14:45 +0100	[thread overview]
Message-ID: <3E784315.3060806@aitel.hist.no> (raw)
In-Reply-To: <779600000.1048059690@[10.10.2.4]>

Martin J. Bligh wrote:
> http://bugme.osdl.org/show_bug.cgi?id=471
> 
>            Summary: Root on software raid don't boot on new 2.5 kernel since
>                     after 2.5.45

Root on raid-1 works fine for me, with and without devfs.  My kernel has
no module support, everything is compiled in.  I don't use initrd.
I have used root-raid with every 2.5 kernel except for a few that had
raid bugs. (Affecting all raid, the root weren't special.)

Until recently the root raid always did an unclean shutdown, but this didn't
cause other trouble than a bootup resync.

> Problem Description:
>  The software raid setup I have boots on 2.4 but not on newer 2.5 kernels, i
> have everything need compiled in and the 2.5 kernel also rapports that it has
> found /dev/md2 but it rapports that is's unable to mount the root partition for
> this device. I have tried to pass /dev/md0 as the root but this hangs the
> kernel, is root on raid broaken in kernel 2.5 or am I doing something wrong?
> 
>  lilo:
>   image=/boot/vmlinuz-2.4.21-pre1
>         label=linux
>         root=/dev/md2
>         read-only
>         append=" devfs=mount"
> 
>   image=/boot/vmlinuz-2.5.65
>         label=linux25
>         root=/dev/md2
>         read-only
>         append=" devfs=mount"

Are you using devfs?  I expect the name of the raid device
to be something like /dev/md/2 instead of /dev/md2 in that case.

Helge Hafting


      reply	other threads:[~2003-03-19 10:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19  7:41 Martin J. Bligh
2003-03-19 10:14 ` Helge Hafting [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=3E784315.3060806@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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

all inboxes | Powered by JetHome®