linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas -Balu- Walter <tw@itreff.de>
To: linux-raid@vger.kernel.org
Subject: Re: Woody, initrd, raid1, boot
Date: Tue, 18 Jun 2002 11:25:49 +0200	[thread overview]
Message-ID: <20020618112549.C14962@itreff.de> (raw)
In-Reply-To: <20020617185019.GB7974@unthought.net>; from jakob@unthought.net on Mon, Jun 17, 2002 at 08:50:19PM +0200

Thanks for CCing, Jakob - I am not subscribed to the list and was
thinking of checking the archives, but this way answering is easier (and
might not shuffle threads too much)

+ Jakob Oestergaard <jakob@unthought.net> [17.06.02 21:05]:
> On Mon, Jun 17, 2002 at 05:15:11PM +0200, Thomas -Balu- Walter wrote:
[...]
> >         md: md driver 0.90.0 MAX_MD...
> >         cramfs: wrong magic
> >         EXT3-FS: unable to read superblock
> >         EXT2-FS: unable to read superblock
> >         Kernel panic: VFS: Unable to mount root fs on 09:01
> 
> Since it's cramfs that complains, I suppose it's your initrd that is
> bad.

Hm - thats the default woody initrd of that kernel, however I have added
the raid module, created a new initrd and got the same message - but I
can mount the initrd manually (-t cramfs -o loop) and look whats inside,
and I can spawn the shell at boot and load the modules manually (they
get loaded automatically too, but still can not find the superblocks)

> Compile the RAID-1 into the kernel, forget about using modules.  That is
> the simple solution that I use - I am no initrd expert, and I have no
> intentions of becoming one  :)

No, that would be "the easy way" - I am not supposed to give up on this
8). 

If I am able to get it running this way, I don't have to bother with
updates or other things. I could just get a new default debian
kernel-image and the initrd would be built with the new modules, ...

+ Scott Bisker <scott@bisker.com> wrote:
> What you need to do is recreate your initrd to include the modules you
> need during boot.  The default mkinitrd /boot/initrd-2.4.18-686-raid1
> 2.4.18-686-raid1 will not suffice.
> 
> Try this.
> 
> mkinitrd --preload=raid1 --preload=xor /boot/initrd-2.4.18-686-raid1
> 2.4.18-686-raid1

The debian mkinitrd does not have --preload, the modules that should be
included go into /etc/mkinitrd/modules. I've added raid1 already, but
not xor? Perhaps this is the one to go for?
> 
> Not sure about on debian, but raidtools should have at least the
> following tools.
> 
> /sbin/arytst
> /sbin/detect_multipath
> /sbin/lsraid
> /sbin/raidreconf

The ones above do not exist. Woody's raidtools2 are 0.90.20010914-15

> /sbin/mkraid
> /sbin/raid0run
> /sbin/raidhotadd
> /sbin/raidhotgenerateerror
> /sbin/raidhotremove
> /sbin/raidsetfaulty
> /sbin/raidstart
> /sbin/raidstop

I have those. Do they have to be on the initrd too?

     Balu

  parent reply	other threads:[~2002-06-18  9:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-17 15:15 Woody, initrd, raid1, boot Thomas -Balu- Walter
2002-06-17 18:50 ` Jakob Oestergaard
2002-06-17 19:35   ` Scott Bisker
2002-06-18  9:25   ` Thomas -Balu- Walter [this message]
2002-06-18 17:19     ` Thomas -Balu- Walter

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=20020618112549.C14962@itreff.de \
    --to=tw@itreff.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).