From: Harold Martin <cocoadev@earthlink.net>
To: linux-kernel@vger.kernel.org
Subject: Mounting /dev/md0 as root in 2.6.0-test7
Date: Sun, 19 Oct 2003 09:58:52 -0700 [thread overview]
Message-ID: <1066582732.1108.5.camel@localhost> (raw)
First, is it possible to mount an md device as root (superblock is
present)?
If not then the rest of this doesn't really matter...
If so, I can't get it to work :(
I pass root=/dev/md0 to the kernl, but I get the "Kernel panic: VFS:
Unable to mount root fs on md0" error.
My setup:
kernel 2.6.0-test7
One drive on each of my two IDE channels (i810 chipset)
RAID 0, set up with raidtools
Using devfs
My FS type (ext2 and ext3), partition type (DOS), and RAID-0 support are
all compiled in (not as modules).
What else do I need to do to be able to mount /dev/md0 as root?
Thanks for your help,
Harold
next reply other threads:[~2003-10-19 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 16:58 Harold Martin [this message]
2003-10-19 18:16 ` Mounting /dev/md0 as root in 2.6.0-test7 Michael Buesch
2003-10-20 8:23 ` Helge Hafting
-- strict thread matches above, loose matches on Subject: below --
2003-10-19 18:53 John Mock
2003-10-19 19:12 ` Andre Tomt
2003-10-19 20:48 John Mock
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=1066582732.1108.5.camel@localhost \
--to=cocoadev@earthlink.net \
--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;
as well as URLs for NNTP newsgroup(s).