mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: oliver.kowalke@t-online.de (Oliver Kowalke)
To: <linux-kernel@vger.kernel.org>
Subject: kernel 2.4.0 + software RAID causes problems
Date: Sun, 7 Jan 2001 12:27:52 +0100	[thread overview]
Message-ID: <001101c0789c$e006d7b0$0201a8c0@p3x2nt> (raw)

Hi,

on my machine (x86) I've debian2.2r2 with kernel 2.2.16 + raidtools 0.9
running. No problems. Yesterday I installed kern 2.4.0 with the same
configuration like 2.2.16. I added following to the boot params:

root=/dev/md0 md=0,/dev/hde1,/dev/hdg1

If I boot 2.4.0 I can see following:

...
<init of raid>
raid:0 md-size is 249728 blocks
raid0: conf->smallest->size is 249728 blocks
raid0: nb_zone is 1
raid0: blocking 8 bytes for hash
md: updating md0 RAID superblock on device                <<<------
<...>
... autorun DONE
md: loading md0
... md0 already autodetected -use raid=noautodetect
<...>
Parallelizing fsck version 1.18
fsck.ext2: No such file or directory while trying to open /dev/md0 (null):
The superblock could not be read or does not describe a correct ext2
filesystem.


The filessystem is clean because I can mount it with kernel 2.2.16 without
problems. Maybe kernel 2.4.0 does the wrong in updating the RAIS superblock
on md0.
Please help!

with regards,
Oliver



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-01-07 11:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-07 11:27 Oliver Kowalke [this message]
     [not found] <001b01c0789c$f10398f0$0201a8c0@p3x2nt>
2001-01-07 11:45 ` Neil Brown
  -- strict thread matches above, loose matches on Subject: below --
2001-01-07 10:02 Oliver Kowalke

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='001101c0789c$e006d7b0$0201a8c0@p3x2nt' \
    --to=oliver.kowalke@t-online.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®