From: Oleg Drokin <green@namesys.com>
To: Serge Rodrigues <serge@onpoi.net>
Cc: reiserfs-list@namesys.com
Subject: Re: RE : RE : some troubles with mounting reiserfs
Date: Fri, 2 May 2003 12:05:03 +0400 [thread overview]
Message-ID: <20030502080502.GC20656@namesys.com> (raw)
In-Reply-To: <000101c3100a$d9356b60$0832a8c0@dell8100>
Hello!
On Thu, May 01, 2003 at 07:55:22PM +0200, Serge Rodrigues wrote:
> > ReiserFS version 3.6.25
> > hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=142082111,
> > sector=142082048
> > end_request: I/O error, dev 03:41 (hdb), sector 142082048
> > hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=147587135,
> > sector=147587072
> > end_request: I/O error, dev 03:41 (hdb), sector 147587072
> > sh-2029: reiserfs read_bitmaps: bitmap block (#17760256) reading
> failed
> > reiserfs_read_super: unable to read bitmap
> >>These are sure sign of something cannot be read from your disk.
> >>Though I am not sure why badblocks outputs no info.
> >>How about running badblocks without specifying start offset and device
> size?
> After a very very very long badblocks -n -s -b 4096 /dev/hdb1, it found
> some badblocks. What I need to do for recover my HDD if any solution
> exist ?
Well, you can read reiserfs-list archives for a solution that are posted there from
time to time, or you can go to http://www.namesys.com/support.html and
use our paid services if you prefer to get direct instructions from us.
Bye,
Oleg
prev parent reply other threads:[~2003-05-02 8:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-27 10:25 some troubles with mounting reiserfs Serge Rodrigues
2003-04-28 5:38 ` Oleg Drokin
2003-04-28 19:33 ` RE : " Serge Rodrigues
2003-04-29 5:40 ` Oleg Drokin
2003-05-01 17:55 ` RE : " Serge Rodrigues
2003-05-01 17:59 ` Anders Widman
2003-05-02 8:05 ` Oleg Drokin [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=20030502080502.GC20656@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=serge@onpoi.net \
/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.