Re: Filesystem errors

Re: Filesystem errors

[Robert Brockway]

On Tue, 16 Jul 2002, Brian Marr wrote:

> Can anyone help interpret these logs ? They have just started appearing on my 
> Suse 8.0 system. I have made some tentative exploration with reiserfsck 
> --check. The results were
> reiserfsck......check started on Mon
> Replaying journal
> 0 transactions replayed
> checking S+tree..../1(of 2 ) / 1(of 164)/ 51(of 166)
> pass_through_tree: Unable to read block 52842 block on device 0x3
> 
> The system is working but something is obviously wrong. Also the xserver is 
> taking ages to start.

Hi Brian.  I'd look at backing up the data on that drive _now_.  Not
wanting to scare you but I'd be suspecting a hardware fault which will get
worse.  How old is the drive?

Cheers,
	-Rob
 
> Brian Marr
> 
> (snip)==========
> VFS: Disk change detected on device sr(11,0)
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=487003, 
> sector=422736
> end_request: I/O error, dev 03:02 (hda), sector 422736
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=487003, 
> sector=422736
> end_request: I/O error, dev 03:02 (hda), sec
> 
> 
> (snip)======
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=474244, 
> sector=409984
> end_request: I/O error, dev 03:02 (hda), sector 409984
> vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data 
> of [96126 168017 0x0 SD]
> 

-- 
-- Robert Brockway B.Sc. email: robert@timetraveller.org  ICQ: 104781119
   Linux counter project ID #16440 (http://counter.li.org)
   avon: up 4 days, 13:52,  2 users,  load average: 0.00, 0.00, 0.00
   "The earth is but one country and mankind its citizens" -Baha'u'llah

Re: Filesystem errors

[Hans Reiser]

Brian Marr wrote:

>Can anyone help interpret these logs ? They have just started appearing on my 
>Suse 8.0 system. I have made some tentative exploration with reiserfsck 
>--check. The results were
>reiserfsck......check started on Mon
>Replaying journal
>0 transactions replayed
>checking S+tree..../1(of 2 ) / 1(of 164)/ 51(of 166)
>pass_through_tree: Unable to read block 52842 block on device 0x3
>
>The system is working but something is obviously wrong. Also the xserver is 
>taking ages to start.
>
>Brian Marr
>
>(snip)==========
>VFS: Disk change detected on device sr(11,0)
>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=487003, 
>sector=422736
>end_request: I/O error, dev 03:02 (hda), sector 422736
>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=487003, 
>sector=422736
>end_request: I/O error, dev 03:02 (hda), sec
>
>
>(snip)======
>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=474244, 
>sector=409984
>end_request: I/O error, dev 03:02 (hda), sector 409984
>vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data 
>of [96126 168017 0x0 SD]
>
>
>  
>
did you fdisk without a reboot before mkreiserfsing?

-- 
Hans

Re: Filesystem errors

[Hans Reiser]

Brian Marr wrote:

>Can anyone help interpret these logs ? They have just started appearing on my 
>Suse 8.0 system. I have made some tentative exploration with reiserfsck 
>--check. The results were
>reiserfsck......check started on Mon
>Replaying journal
>0 transactions replayed
>checking S+tree..../1(of 2 ) / 1(of 164)/ 51(of 166)
>pass_through_tree: Unable to read block 52842 block on device 0x3
>
>The system is working but something is obviously wrong. Also the xserver is 
>taking ages to start.
>
>Brian Marr
>
>(snip)==========
>VFS: Disk change detected on device sr(11,0)
>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=487003, 
>sector=422736
>end_request: I/O error, dev 03:02 (hda), sector 422736
>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=487003, 
>sector=422736
>end_request: I/O error, dev 03:02 (hda), sec
>
>
>(snip)======
>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
>hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=474244, 
>sector=409984
>end_request: I/O error, dev 03:02 (hda), sector 409984
>vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data 
>of [96126 168017 0x0 SD]
>
>
>  
>
did you fdisk without a reboot before mkreiserfsing?   If yes, see FAQ.

-- 
Hans

Filesystem errors

[Brian Marr]

Can anyone help interpret these logs ? They have just started appearing on my 
Suse 8.0 system. I have made some tentative exploration with reiserfsck 
--check. The results were
reiserfsck......check started on Mon
Replaying journal
0 transactions replayed
checking S+tree..../1(of 2 ) / 1(of 164)/ 51(of 166)
pass_through_tree: Unable to read block 52842 block on device 0x3

The system is working but something is obviously wrong. Also the xserver is 
taking ages to start.

Brian Marr

(snip)==========
VFS: Disk change detected on device sr(11,0)
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=487003, 
sector=422736
end_request: I/O error, dev 03:02 (hda), sector 422736
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=487003, 
sector=422736
end_request: I/O error, dev 03:02 (hda), sec


(snip)======
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=474244, 
sector=409984
end_request: I/O error, dev 03:02 (hda), sector 409984
vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data 
of [96126 168017 0x0 SD]

Re: Filesystem errors

[Brian Marr]

What reiserfsck paramaters should I try ? Do I have to do --rebuild-tree ?
Brian Marr

On Monday 15 July 2002 15:36, you wrote:
> Brian Marr wrote:
> >Can anyone help interpret these logs ? They have just started appearing on
> > my Suse 8.0 system. I have made some tentative exploration with
> > reiserfsck --check. The results were
> >reiserfsck......check started on Mon
> >Replaying journal
> >0 transactions replayed
> >checking S+tree..../1(of 2 ) / 1(of 164)/ 51(of 166)
> >pass_through_tree: Unable to read block 52842 block on device 0x3
> >
> >The system is working but something is obviously wrong. Also the xserver
> > is taking ages to start.
>
> Probably you have bad blocks on your reiserfs partition. And because of
> this your xserver starts so slowly. Kernel trying to reread a block and
> can't do it, because it is bad.
>
> >Brian Marr
> >
> >(snip)==========
> >VFS: Disk change detected on device sr(11,0)
> >hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=487003,
> >sector=422736
> >end_request: I/O error, dev 03:02 (hda), sector 422736
> >hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=487003,
> >sector=422736
> >end_request: I/O error, dev 03:02 (hda), sec
> >
> >
> >(snip)======
> >hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=474244,
> >sector=409984
> >end_request: I/O error, dev 03:02 (hda), sector 409984
> >vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat
> > data of [96126 168017 0x0 SD]

Re: Filesystem errors

[Brian Marr]

I have looked at the FAQ. I have not touched fdisk.
I am thinking of backing up the partition, reformatting and copying back the 
data. I had to do this on another drive recently.
Brian Marr

Current useage
Filesystem            Size  Used Avail Use% Mounted on
/dev/hda2              14G  2.5G   11G  17% /

On Monday 15 July 2002 15:47, you wrote:
> Brian Marr wrote:
> >What reiserfsck paramaters should I try ? Do I have to do --rebuild-tree ?
> >Brian Marr
> >
> >On Monday 15 July 2002 15:36, you wrote:
> >>Brian Marr wrote:
> >>>Can anyone help interpret these logs ? They have just started appearing
> >>> on my Suse 8.0 system. I have made some tentative exploration with
> >>> reiserfsck --check. The results were
> >>>reiserfsck......check started on Mon
> >>>Replaying journal
> >>>0 transactions replayed
> >>>checking S+tree..../1(of 2 ) / 1(of 164)/ 51(of 166)
> >>>pass_through_tree: Unable to read block 52842 block on device 0x3
> >>>
> >>>The system is working but something is obviously wrong. Also the xserver
> >>>is taking ages to start.
> >>
> >>Probably you have bad blocks on your reiserfs partition. And because of
> >>this your xserver starts so slowly. Kernel trying to reread a block and
> >>can't do it, because it is bad.
>
> Please, read on www.namesys.com about this problem. Right now I may
> suggest you to try to kill old xserver binary and copy it again.
>
> >>>Brian Marr
> >>>
> >>>(snip)==========
> >>>VFS: Disk change detected on device sr(11,0)
> >>>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >>>hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=487003,
> >>>sector=422736
> >>>end_request: I/O error, dev 03:02 (hda), sector 422736
> >>>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >>>hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=487003,
> >>>sector=422736
> >>>end_request: I/O error, dev 03:02 (hda), sec
> >>>
> >>>
> >>>(snip)======
> >>>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >>>hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=474244,
> >>>sector=409984
> >>>end_request: I/O error, dev 03:02 (hda), sector 409984
> >>>vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat
> >>>data of [96126 168017 0x0 SD]

Re: Filesystem errors

[Oleg Drokin]

Hello!

On Tue, Jul 16, 2002 at 02:22:50AM +0930, Brian Marr wrote:

> What reiserfsck paramaters should I try ? Do I have to do --rebuild-tree ?

You hard drive is failing, so yuo should backup all the data to other
drive first, then you might want to revive your disk, or get it replaced
(which is even beter).
You better not to run reiserfsck or any other programs (besides tar or
some other backup tool) on this disk, because you might loose even more data
this way.

Bye,
    Oleg

Re: Filesystem errors

[Brian Marr]

Thanks for your comments. My system is still going under my watchful eye. I 
tried to copy the data using tar to a spare diskl
tar -cplf - -C /myhardrive . | tar -xpvf -
but this did not go far. I wonder if I could boot into rescue and do  a dd ?
I have not used this before.
Brian Marr




On Wednesday 17 July 2002 15:12, Oleg Drokin wrote:
> Hello!
>
> On Tue, Jul 16, 2002 at 02:22:50AM +0930, Brian Marr wrote:
> > What reiserfsck paramaters should I try ? Do I have to do --rebuild-tree
> > ?
>
> You hard drive is failing, so yuo should backup all the data to other
> drive first, then you might want to revive your disk, or get it replaced
> (which is even beter).
> You better not to run reiserfsck or any other programs (besides tar or
> some other backup tool) on this disk, because you might loose even more
> data this way.
>
> Bye,
>     Oleg

Re: Filesystem errors

[Oleg Drokin]

Hello!

On Wed, Jul 17, 2002 at 05:36:44PM +0930, Brian Marr wrote:

> Thanks for your comments. My system is still going under my watchful eye. I 
> tried to copy the data using tar to a spare diskl
> tar -cplf - -C /myhardrive . | tar -xpvf -
> but this did not go far. I wonder if I could boot into rescue and do  a dd ?
> I have not used this before.

use dd_rescue tool, conventional dd is not working very good with
broken hard disks.

Bye,
    Oleg

Re: Filesystem errors

[Kuba Ober]

> On Wed, Jul 17, 2002 at 05:36:44PM +0930, Brian Marr wrote:
> > Thanks for your comments. My system is still going under my watchful eye.
> > I tried to copy the data using tar to a spare diskl
> > tar -cplf - -C /myhardrive . | tar -xpvf -
> > but this did not go far. I wonder if I could boot into rescue and do  a
> > dd ? I have not used this before.
>
> use dd_rescue tool, conventional dd is not working very good with
> broken hard disks.

Better yet, buy sprinrite (www.grc.com). It's an absolutely great tool, and 
more than worth the money. Although it doesn't handle out-of-place (i.e. data 
moving) recovery on non-fat filesystems, it can diagnose your disk and try 
recovering in-place. It uses quite advanced data recovery methods. It goes 
about as far as you can go without taking the hard drive out and plugging it 
into specialized hardware.

Did I mention that spinrite was about 100kb in size and written in assembler?

Cheers, Kuba Ober

Re: Filesystem errors

[Oleg Drokin]

Hello!

On Wed, Jul 17, 2002 at 08:11:44AM -0400, Kuba Ober wrote:

> Did I mention that spinrite was about 100kb in size and written in assembler?

This is not an advantage by any means in my view. It only means it is
x86 specific, most probably requires dos/windows, and hard to debug.

Bye,
    Oleg

Re: Filesystem errors

[Kuba Ober]

On ¶roda 17 lipiec 2002 08:16 am, Oleg Drokin wrote:
> Hello!
>
> On Wed, Jul 17, 2002 at 08:11:44AM -0400, Kuba Ober wrote:
> > Did I mention that spinrite was about 100kb in size and written in
> > assembler?
>
> This is not an advantage by any means in my view. It only means it is
> x86 specific, most probably requires dos/windows, and hard to debug.

You're right, but the guy simply kept it in assembler since mid-80's.

And as far as I know him, and I know his coding style a little bit from 
disassembling the early spinrite II, his code is mostly more legible than 
poorly written C++.

And the program, believe it or not, does not require debugging as it is. I 
think that the current version works fine w/o any changes nor patches since 
about 3 years or so. He does one hell of a testing job, and he always bases 
on previous code that worked (most probably one of the reasons why it's still 
in assembler).

He is kind of assembly-maniac, but he has some windows utilities which are in 
assembler and do very cool things.

Cheers, Kuba Ober