From: Brandon Evans <maillists@hosttuls.com>
To: schmidt@naa.net, Linux-raid maillist <linux-raid@vger.kernel.org>
Subject: Re: Kernal Panic when booting redhat. Raid devices mount fine underKnoppix
Date: Fri, 12 Dec 2003 09:46:19 -0800 [thread overview]
Message-ID: <3FD9FEEB.7040006@hosttuls.com> (raw)
In-Reply-To: <3FD99121.9000702@ratnet.stw.uni-erlangen.de>
Norman Schmidt wrote:
> Brandon Evans schrieb:
For the record, the error I was getting was:
EXT3-fs: unable to read superblock
mount:error 22 mounting ext3
> Are you sure that the partition type is not set to fd?
Yes, they are all set to fd.
> Then the problem might be the older mechanism of RedHAT to start the raids.
>
> Which bootloader do you use? I use lilo for my servers, that works with
> root on raid1.
Thanks for all the info. It will come in handy.
I was finally able to get the / partition to boot by switching the fs
type from ext3 to ext2.
I was able to boot in ext2, I switched the fs back to ext3, rebooted,
and now everything works fine.
I'm curious as to what happened there, but that question is for another
list.
--
Thanks,
Brandon E.
prev parent reply other threads:[~2003-12-12 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 23:03 Kernal Panic when booting redhat. Raid devices mount fine under Knoppix Brandon Evans
2003-12-11 1:03 ` Raid array not clean (its barely used and a few weeks old.. how can i find out what went wrong?) James R Bamford
2003-12-11 1:49 ` Guy
2003-12-12 0:07 ` James R Bamford
2003-12-12 2:27 ` Guy
[not found] ` <3FD822D4.2030501@ratnet.stw.uni-erlangen.de>
2003-12-11 22:16 ` Kernal Panic when booting redhat. Raid devices mount fine underKnoppix Brandon Evans
2003-12-11 23:26 ` Dan Egli
[not found] ` <3FD99121.9000702@ratnet.stw.uni-erlangen.de>
2003-12-12 17:46 ` Brandon Evans [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=3FD9FEEB.7040006@hosttuls.com \
--to=maillists@hosttuls.com \
--cc=linux-raid@vger.kernel.org \
--cc=schmidt@naa.net \
/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).