From: Oleg Drokin <green@namesys.com>
To: Cookie-Monster <cookie.monster@starfall.de>
Cc: reiserfs-list@namesys.com
Subject: Re: Problem with my HDD
Date: Thu, 30 May 2002 09:21:55 +0400 [thread overview]
Message-ID: <20020530092155.D3922@namesys.com> (raw)
In-Reply-To: <10512850437.20020529194929@starfall.de>
Hello!
On Wed, May 29, 2002 at 07:49:29PM +0200, Cookie-Monster wrote:
> I hope you can help me. I formated on of my Server-HDDs with ReiserFS
> version, which has been distributed in SuSE Linux 7.3. Sorry, but I
> don't know the version, cause I'm know running SuSE Linux 8.0.
> My Problem is, that the HDD cannot be mounted anymore:
> 1. fileserver:/ # mount /dev/sda1 /ftp/apps/
> 2. mount: Not a directory
> Bad root block 4294967295. (--rebuild-tree did not complete)
Well, so you in fact run reiserfsck --rebuild-tree before.
What caused you to run it for the first time?
> The check goes on til there are 171398 (more than 60%) blocks left then it hangs
> up for a while before continueing. From this point on it continues
> very slow only. From 150xxx it continues fast til 13039.
> At this point the program quits without saying anything and the HDD is
> hung up. The old version of reiserfsck, in the SuSe Linux 7.3 Edition
> gave out a lot of "Block could not be read" or something like this and
> the HDD hung up.
what does 'dmesg' output says after this?
If you have read errors, then namesys can help you only based
on http://namesys.com/support.html terms.
> I really need the data! Is there any possibilty of deleating the
> unreadable blocks and rebuuilding the tree then? When this works, I
This is possible, but all the data that was contained in these blocks would be
lost.
> p.s.: The HDD is a IBM DRHS36V (36GB U2W-SCSI) if that is important.
Hm, I thought that only IBM DTLA-307040 and IC40... were subject to quick
death.
Bye,
Oleg
next prev parent reply other threads:[~2002-05-30 5:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 17:49 Problem with my HDD Cookie-Monster
2002-05-29 17:53 ` Anders Widman
2002-05-29 21:19 ` Kuba Ober
2002-05-29 23:45 ` Robert Brockway
2002-05-30 0:09 ` Re[2]: " Anders Widman
2002-05-30 5:17 ` Oleg Drokin
2002-05-31 5:15 ` Billy Transue
2002-05-31 8:29 ` Oleg Drokin
2002-05-30 5:14 ` Oleg Drokin
2002-05-30 5:49 ` Robert Brockway
2002-05-30 11:35 ` Re[2]: " Cookie-Monster
2002-05-30 11:58 ` Cookie-Monster
2002-05-30 13:35 ` Re[3]: " Anders Widman
2002-05-30 13:39 ` Re[2]: " Chris Mason
2002-05-30 13:59 ` Robert Brockway
2002-05-30 5:21 ` Oleg Drokin [this message]
[not found] ` <781752530.20020530134323@starfall.de>
[not found] ` <20020530155353.B1060@namesys.com>
2002-06-02 18:02 ` Cookie-Monster
-- strict thread matches above, loose matches on Subject: below --
2002-05-31 16:28 Dieter Nützel
2002-05-31 18:49 ` Billy Transue
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=20020530092155.D3922@namesys.com \
--to=green@namesys.com \
--cc=cookie.monster@starfall.de \
--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.