From: "Ville Holma" <ville.holma@pp.htv.fi>
To: <linux-kernel@vger.kernel.org>
Subject: Re: a way to restore my hd ?
Date: Sun, 22 Apr 2001 21:17:05 +0300 [thread overview]
Message-ID: <000701c0cb58$70373240$6786f3d5@pp.htv.fi> (raw)
In-Reply-To: <E14r6WZ-0004XM-00@the-village.bc.nu>
Thank You everybody who helped me solve the problem. I found a working
back-up of the superblock at -b 32768 and was able to save all of my
important work from the harddrive. The filesystem was however badly
corrupted and lots of other files were truncated after e2fsck had finished.
So I ended up just re-installing my linux distribution but didn't loose any
valuable work. Lucky me.
So, again, Thank You all for the great help I received. You know who you
are.
Ville
> > The memory I had was however somehow corrupt and after I got my new
system
> > booted up and used it a little it became shaky and then locked hard and
I
> > could do nothing but reset it. I suppose this was caused by the
> > malfunctioning memory but I can't be sure, I know there has been
problems
> > with the via chipset also.
>
> Nod
>
> > debian:~# e2fsck /dev/hdb7
> > e2fsck 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
> > Corruption found in superblock. (frags_per_group = 2147516416).
>
> Try e2fsck -b 8193 /dev/hdb7
>
> (and 16384, 32768)
>
> This is a backup copy of the superblock.
>
next prev parent reply other threads:[~2001-04-22 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-21 15:52 a way to restore my hd ? Ville Holma
2001-04-21 16:40 ` Karsten Keil
2001-04-21 18:27 ` Steve Bromwich
2001-04-21 22:30 ` Guest section DW
2001-04-21 23:10 ` Alan Cox
2001-04-22 18:17 ` Ville Holma [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-21 16:09 Ville Holma
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='000701c0cb58$70373240$6786f3d5@pp.htv.fi' \
--to=ville.holma@pp.htv.fi \
--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 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.