public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: jason <jason@lacan.dabney.caltech.edu>, linux-kernel@vger.kernel.org
Subject: Re: kernel panic with 2.4.x and reiserfs
Date: Fri, 27 Apr 2001 10:24:10 -0400	[thread overview]
Message-ID: <217780000.988381450@tiny> (raw)
In-Reply-To: <Pine.LNX.4.10.10104270104010.7570-100000@lacan.dabney.caltech.edu>



On Friday, April 27, 2001 02:40:50 AM -0700 jason
<jason@lacan.dabney.caltech.edu> wrote:

[ ouch ]

> 
> reiserfs_read_super: can't find reiserfs filesystem on dev 03:01
> Invalid session # or type of track
> Kernel panic: VFS: Unable to mount root fs on 03:01
> 
>   In case it's any help, I'm running Debian "sid" under kernel 2.4.3. hda
> is a Western Digital WD400 (UDMA 100) while hdc is a Maxtor 36.5 GB. I
> have a 900 Mhz Athlon on an Abit KT7A, the latter containing the South
> Bridge VIA VT82C686B and a North Bridge VIA VT8363A.
>   Any info on how I could possibly retrieve data from my disk (hda) would
> be greatly appreciated...
> 

Looks like you've hit the pot-luck of VIA problems, and elevator bugs
(2.4.1).  When the last crash hit, did you recycle with the power button or
the reset button?

Step one, if you can, get a backup of the raw device.  This will make
everything easier if there are problems in step 3.  

Step two, grab the latest reiserfsprogs from
ftp.reiserfs.org/pub/reiserfsprogs.

Step three, reiserfsck --rebuild-sb ; reiserfsck --rebuild-tree

Drop me a line if there are any questions.

-chris


  reply	other threads:[~2001-04-27 14:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-27  9:40 kernel panic with 2.4.x and reiserfs jason
2001-04-27 14:24 ` Chris Mason [this message]
2001-04-27 15:33 ` Tony Hoyle
2001-04-27 16:08   ` Chris Mason
2001-04-28  3:22   ` david

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=217780000.988381450@tiny \
    --to=mason@suse.com \
    --cc=jason@lacan.dabney.caltech.edu \
    --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