mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@broadpark.no>
To: "Cress, Andrew R" <andrew.r.cress@intel.com>
Cc: linux-kernel@vger.kernel.org, neilb@cse.unsw.edu.au
Subject: Re: 2.5.34 unable to mount root FIXED in bk6
Date: Sun, 15 Sep 2002 21:41:46 +0200	[thread overview]
Message-ID: <3D84E27A.D1BFA4E3@broadpark.no> (raw)
In-Reply-To: <A5974D8E5F98D511BB910002A50A66470580D1AE@hdsmsx103.hd.intel.com>

I use modules only for seldom-used stuff
like floppy & scanner.  The RAID is compiled-in.
It works in 2.5.33, and works again in 2.5.34-bk6,
where some raid fixes related to partitioning problems
went in.

Helge Hafting


"Cress, Andrew R" wrote:
> 
> Helge,
> 
> You've probably already checked this, but is  CONFIG_BLK_DEV_MD=y ?
> It won't work if you have a root mirror and this is a configured as a
> module.
> 
> Andy Cress
> 
> -----Original Message-----
> From: Helge Hafting [mailto:helge.hafting@broadpark.no]
> Sent: Thursday, September 12, 2002 1:24 PM
> To: Linux Kernel Mailing List
> Subject: 2.5.34 unable to mount root fs on 09:00 (smp,raid1,devfs,scsi)
> 
> 2.5.33 works. 2.5.34 and 2.5.34-bk3 won't mount the
> root fs.  The root fs is on /dev/md/1, composed
> of 2 partitions on different scsi disks.
> 
> The RAID-1 setup is autodetected, so it don't look
> like a hardware or scsi problem.  Everything seems normal
> until the root mount fail and the kernel hangs.  Not
> even sysrq works after that.
> 
> Helge Hafting
> -

      parent reply	other threads:[~2002-09-15 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13 21:02 2.5.34 unable to mount root fs on 09:00 (smp,raid1,devfs,scsi ) Cress, Andrew R
2002-09-13 21:37 ` Gregoire Favre
2002-09-15 19:41 ` 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=3D84E27A.D1BFA4E3@broadpark.no \
    --to=helge.hafting@broadpark.no \
    --cc=andrew.r.cress@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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®