From: Jeff Mahoney <jeffm@suse.com>
To: Shawn Starr <spstarr@sh0n.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.6-pre3 breaks ReiserFS mount on boot
Date: Tue, 19 Jun 2001 01:06:34 -0400 [thread overview]
Message-ID: <20010619010633.G8295@fury.csh.rit.edu> (raw)
In-Reply-To: <Pine.LNX.4.30.0106182320510.2168-100000@coredump.sh0n.net> <Pine.LNX.4.30.0106182355500.118-100000@coredump.sh0n.net>
In-Reply-To: <Pine.LNX.4.30.0106182355500.118-100000@coredump.sh0n.net>; from spstarr@sh0n.net on Mon, Jun 18, 2001 at 11:57:16PM -0400
On Mon, Jun 18, 2001 at 11:57:16PM -0400, Shawn Starr wrote:
>
> read_super_block: can't find a reiserfs filesystem on dev 03:42
> read_old_super_block: try to find super block in old location
> read_old_super_block: can't find a reiserfs filesystem on dev 03:42
> Kernel Panic: VFS: Unable to mount root fs on 03:42
>
> my super block broke somewhere?
Out of curiousity, what device are you trying to boot from? 03:42, at least
according to linux/Documentation/devices.txt, corresponds to /dev/hda42.
Is that really the disk you're trying to mount? I'm not familiar with how
some IDE RAID controllers present disks, but it was the first thing I
noticed.
-Jeff
--
Jeff Mahoney
jeffm@suse.com
jeffm@csh.rit.edu
next prev parent reply other threads:[~2001-06-19 5:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-18 21:12 Why can't I flush /dev/ram0? Kelledin Tane
2001-06-18 21:23 ` Richard B. Johnson
2001-06-18 21:41 ` Kelledin Tane
2001-06-18 21:55 ` Jan Rekorajski
2001-06-19 1:37 ` Kelledin Tane
2001-06-19 2:58 ` Linux 2.4.6-pre3 breaks ReiserFS mount on boot Shawn Starr
2001-06-19 3:14 ` Olivier Galibert
2001-06-19 3:23 ` Shawn Starr
2001-06-19 3:57 ` Shawn Starr
2001-06-19 4:59 ` Chris Mason
2001-06-19 5:06 ` Jeff Mahoney [this message]
2001-06-19 5:31 ` Neil Brown
2001-06-19 5:37 ` Jeff Mahoney
2001-06-25 13:40 ` Shawn Starr
2001-06-19 8:12 ` Justin Guyett
2001-06-19 9:33 ` Alan Cox
2001-06-19 15:13 ` Chris Mason
2001-06-19 15:35 ` David Ford
2001-06-19 3:32 ` Chris Mason
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=20010619010633.G8295@fury.csh.rit.edu \
--to=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spstarr@sh0n.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
all inboxes | Powered by JetHome®