public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: Mike <maneman@gmx.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Pierre Rousselet <pierre.rousselet@wanadoo.fr>
Subject: Re: Oops: UMOUNTING in 2.4.17 / Ext2 Partitions destroyed (3x)
Date: Mon, 31 Dec 2001 00:18:22 -0700	[thread overview]
Message-ID: <20011231001822.C12868@lynx.no> (raw)
In-Reply-To: <3C2F2948.DB59646A@gmx.net> <3C2F3455.6050209@wanadoo.fr> <3C2F47F2.BB7BFBDA@gmx.net>
In-Reply-To: <3C2F47F2.BB7BFBDA@gmx.net>; from maneman@gmx.net on Sun, Dec 30, 2001 at 05:59:30PM +0100

On Dec 30, 2001  17:59 +0100, Mike wrote:
> I tried 'e2fsck -f /dev/hdb3' and it returned:
> "Filesystem has unsupported Read-Only features while trying to open
> /dev/hdb3.

Try "tune2fs -l /dev/hdb3" or "debugfs -h /dev/hdb3" (both do the same
thing - spit out the ext2 filesystem superblock data.  What version of
e2fsck are you using?

> The SuperBlock could not be read or does not describe a correct ext2
> filesystem.
> ....If it /is/ ext2 then the Sb is corrupt, run 'e2fsck -b 8193 <device>'"
> 
> So I do 'e2fsck -b 8193 <device>' and it says: "Bad magic number in SB
> while trying to open /dev/hdb3"

You are better off trying "e2fsck -B 4096 -b 32768 /dev/hdb3" instead.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2001-12-31  7:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-30 14:48 Oops: UMOUNTING in 2.4.17 / Ext2 Partitions destroyed (3x) Mike
     [not found] ` <3C2F2C1B.2000100@free.fr>
2001-12-30 15:52   ` Mike
     [not found]     ` <3C2F481F.3070607@free.fr>
2001-12-30 17:06       ` Mike
     [not found] ` <3C2F3455.6050209@wanadoo.fr>
2001-12-30 16:59   ` Mike
2001-12-31  7:18     ` Andreas Dilger [this message]
2001-12-31 19:36       ` Mike

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=20011231001822.C12868@lynx.no \
    --to=adilger@turbolabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maneman@gmx.net \
    --cc=pierre.rousselet@wanadoo.fr \
    /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