From: Stephan von Krawczynski <skraw@ithnet.com>
To: Chris Mason <mason@suse.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.22-pre3 and reiserfs boot problem
Date: Sun, 6 Jul 2003 23:24:35 +0200 [thread overview]
Message-ID: <20030706232435.5e752f37.skraw@ithnet.com> (raw)
In-Reply-To: <1057515223.20904.1315.camel@tiny.suse.com>
On 06 Jul 2003 14:13:44 -0400
Chris Mason <mason@suse.com> wrote:
> On Sun, 2003-07-06 at 12:34, Stephan von Krawczynski wrote:
> > Hello,
> >
> > I just tried 2.4.22-pre3 and found out I cannot boot my test box any more.
> > It halts at:
> >
> > reiserfs: found format "3.6" with standard journal
> >
> > on a partition located on aic7xxx based hd.
> >
> > Booting the box with pre2 works perfectly well.
> > Anything I should try? What information is needed?
>
> Same config here (reiserfs 3.6.x, aic7xxx drive), works without
> problems. Is reiserfs or aic7xxx compiled as a module in your setup?
> If so did you remember to install the new modules and mkinitrd (if
> required).
Hello Chris,
no, there is no modules involved here. The problem arises not on my root
partition (which happens to be reiserfs, too), that seems to be ok. Problems
seem to come up on sda4, a simple data partition.
> Is reiserfs on your root drive? If not can you please boot into single
> user mode, enable sysrq, try the mount again and get the decoded output
> from sysrq-p and sysrq-t if it hangs.
>
> -chris
I am going to try with single user tomorrow morning.
Regards,
Stephan
next prev parent reply other threads:[~2003-07-06 21:10 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-06 16:34 2.4.22-pre3 and reiserfs boot problem Stephan von Krawczynski
2003-07-06 18:13 ` Chris Mason
2003-07-06 21:24 ` Stephan von Krawczynski [this message]
2003-07-07 10:06 ` Stephan von Krawczynski
2003-07-09 12:01 ` Stephan von Krawczynski
2003-07-09 13:36 ` Chris Mason
2003-07-09 13:48 ` Oleg Drokin
2003-07-09 13:58 ` Stephan von Krawczynski
2003-07-09 14:11 ` Oleg Drokin
2003-07-09 14:25 ` Stephan von Krawczynski
2003-07-09 17:18 ` Marcelo Tosatti
2003-07-10 11:21 ` Stephan von Krawczynski
2003-07-10 11:54 ` Marcelo Tosatti
2003-07-10 12:20 ` Stephan von Krawczynski
2003-07-10 12:00 ` Stephan von Krawczynski
[not found] ` <20030709154015.GJ150921@niksula.cs.hut.fi>
2003-07-09 16:36 ` Stephan von Krawczynski
2003-07-09 14:01 ` Vincent Touquet
2003-07-09 14:20 ` Stephan von Krawczynski
-- strict thread matches above, loose matches on Subject: below --
2003-07-10 14:20 Carl-Daniel Hailfinger
2003-07-10 14:38 ` Stephan von Krawczynski
2003-07-10 14:44 ` Carl-Daniel Hailfinger
2003-07-10 15:12 ` Stephan von Krawczynski
2003-07-10 15:30 ` Anders Karlsson
2003-07-10 15:39 ` Carl-Daniel Hailfinger
2003-07-10 19:06 ` Anders Karlsson
2003-07-10 15:49 "Peter Lojkin"
2003-07-10 16:06 ` Stephan von Krawczynski
2003-07-10 17:55 ` Marcelo Tosatti
2003-07-10 17:57 ` Marcelo Tosatti
[not found] <E19ae9K-000Nas-00.ia6432-inbox-ru@f7.mail.ru>
2003-07-10 17:12 ` Stephan von Krawczynski
2003-07-10 18:01 ` Marcelo Tosatti
2003-07-11 13:15 ` Chris Mason
2003-07-11 13:27 ` Stephan von Krawczynski
2003-07-11 13:48 ` Chris Mason
2003-07-11 13:38 ` Stephan von Krawczynski
2003-07-11 13:51 ` Chris Mason
2003-07-11 15:15 ` Marcelo Tosatti
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=20030706232435.5e752f37.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
/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