From: Chris Worley <cworley@symbionsys.com>
To: evilninja <evilninja@gmx.net>
Cc: reiserfs-list@namesys.com
Subject: Re: SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine
Date: Mon, 27 Sep 2004 16:40:02 -0600 [thread overview]
Message-ID: <1096324801.9096.41.camel@xserver.local.net> (raw)
In-Reply-To: <41589155.1050405@gmx.net>
On Mon, 2004-09-27 at 16:16, evilninja wrote:
> ah, now this is funny. dd doesn't care about the filesystem and can't even
> read the device.
> this does not seem like a (reiser-)fs issue, more like a
> corrupted partition table / device
I agree that it's not a reiser issue... but, how did it get mounted in
the first place?
> (if the data on
> /dev/mapper/system-lvol0 is not (!) important, you could play around with
I find the root partition an invaluable part of the system. So, I'm not
going to destroy it on purpose. I'm not quite sure how to boot without
a root partition ;)
I'm really looking for a non-destructive way to test/repair whatever has
happened. The partitioning seems fine (an ext3 boot directory of a few
MB, an 8GB swap, and the root partition):
Device Boot Start End Blocks Id System
/dev/hda1 * 1 5 40131 83 Linux
/dev/hda2 6 979 7823655 82 Linux swap
/dev/hda3 980 30515 237247920 8e Linux LVM
Chris
next prev parent reply other threads:[~2004-09-27 22:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 3:20 SUSE 9.1 with ReiserFS: / won't fsck, but is otherwise fine Chris Worley
2004-09-24 7:17 ` Vitaly Fertman
2004-09-24 13:20 ` Chris Worley
2004-09-24 13:30 ` Hendrik Visage
2004-09-24 13:56 ` Chris Worley
2004-09-24 14:32 ` Hendrik Visage
2004-09-24 14:58 ` Chris Worley
2004-09-27 14:44 ` Vitaly Fertman
2004-09-27 16:06 ` Chris Worley
2004-09-27 22:16 ` evilninja
2004-09-27 22:40 ` Chris Worley [this message]
2004-09-29 0:38 ` evilninja
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=1096324801.9096.41.camel@xserver.local.net \
--to=cworley@symbionsys.com \
--cc=evilninja@gmx.net \
--cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.