From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oleg Drokin Subject: Re: RE : RE : some troubles with mounting reiserfs Date: Fri, 2 May 2003 12:05:03 +0400 Message-ID: <20030502080502.GC20656@namesys.com> References: <20030429054044.GI1231@namesys.com> <000101c3100a$d9356b60$0832a8c0@dell8100> Mime-Version: 1.0 Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com Content-Disposition: inline In-Reply-To: <000101c3100a$d9356b60$0832a8c0@dell8100> List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Serge Rodrigues Cc: reiserfs-list@namesys.com 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