From: Arthur Othieno <arthurothieno@gmx.net>
To: Ray Olszewski <ray@comarre.com>
Cc: Alan Womack <arwbackup@worldnet.att.net>, linux-newbie@vger.kernel.org
Subject: Re: e2fs hosed?
Date: Tue, 15 Oct 2002 09:36:06 +0100 [thread overview]
Message-ID: <3DABD376.4010005@gmx.net> (raw)
In-Reply-To: 5.1.0.14.1.20021014231926.0211e170@celine
Ray Olszewski wrote:
> e2fsck checks ext2 filesystems, not drives. /dev/hdb is NOT a
> filesystem; it is a drive. The drive contains partitions; according to
> your (I presume) fdisk output, partitions /dev/hdb1 and /dev/hdb2
> contain ext2 filesystems.
>
> The message you get in response to "e2fsck -b 131073 /dev/hdb" is simply
> correct -- that device does NOT itself contain an ext2 filesystem.
>
> So ... try "e2fsck /dev/hdb1" and "e2fsck /dev/hdb2".
>
> As to your comment about hdb2 ... sorry, but I can't comment
> intelligently on a problem described as "major issues".
>
>
> At 10:45 PM 10/14/02 -0700, Alan Womack wrote:
>
>> [root@Webby root]# e2fsck -b 131073 /dev/hdb
>> e2fsck 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09
>> e2fsck: Bad magic number in super-block while trying to open /dev/hdb
>>
>> The superblock could not be read or does not describe a correct ext2
>> filesystem. If the device is valid and it really contains an ext2
>> filesystem (and not swap or ufs or something else), then the superblock
>> is corrupt, and you might try running e2fsck with an alternate
>> superblock:
>> e2fsck -b 8193 <device>
>>
As Ray has given most of the intelligent advice above, maybe I can contribute just a little bit more:
>> I've tried quite a few different superblocks, but I need a command to
>> tell me what my block size is. I might be sending it searching in the
>> wrong location. The partition table seems fine:
The command that will tell you the block size of the filesystem you're trying to e2fsck is `mke2fs -n /dev/hdbx'
(substitute the x with the appropriate number). You should see the appropriate results in the head of the output.
Now that you have the block size, you may want to do a `mke2fs -b XXXX
-n /dev/hdbx' (where XXXX is the block size) to get an even more
accurate reporting of the location of the backup superblocks, not that
it wasn't there first time round when you did the `mke2fs -n /dev/hdbx'
With the locations of the backup superblocks, you may now do
`e2fsck -b XXXX /dev/hdbx' (where XXXX is/are the location(s) of the
backup superblock(s)
>> Disk /dev/hdb: 255 heads, 63 sectors, 525 cylinders
>> Units = cylinders of 16065 * 512 bytes
>>
>> Device Boot Start End Blocks Id System
>> /dev/hdb1 1 11 88326 83 Linux
>> /dev/hdb2 12 470 3686917+ 83 Linux
>> /dev/hdb3 471 503 265072+ 82 Linux swap
>>
>> /dev/hdb1 is fine
>> /dev/hdb2 has major issues..
>
>
>
>
>
>
> --
> -------------------------------------------"Never tell me the
> odds!"--------
> Ray Olszewski -- Han Solo
> Palo Alto, California, USA ray@comarre.com
> -------------------------------------------------------------------------------
HTH
Arthur
------
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2002-10-15 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 5:45 e2fs hosed? Alan Womack
2002-10-15 6:24 ` Ray Olszewski
2002-10-15 8:36 ` Arthur Othieno [this message]
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=3DABD376.4010005@gmx.net \
--to=arthurothieno@gmx.net \
--cc=arwbackup@worldnet.att.net \
--cc=linux-newbie@vger.kernel.org \
--cc=ray@comarre.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