[root@trk]:(~)# fsck /dev/hda1                                                                                                                               fsck 1.36 (05-Feb-2005)
reiserfsck 3.6.19 (2003 www.namesys.com)

*************************************************************
** If you are using the latest reiserfsprogs and  it fails **
** please  email bug reports to reiserfs-list@namesys.com, **
** providing  as  much  information  as  possible --  your **
** hardware,  kernel,  patches,  settings,  all reiserfsck **
** messages  (including version),  the reiserfsck logfile, **
** check  the  syslog file  for  any  related information. **
** If you would like advice on using this program, support **
** is available  for $25 at  www.namesys.com/support.html. **
*************************************************************

Will read-only check consistency of the filesystem on /dev/hda1
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Mon Sep  4 21:32:36 2006
###########
Replaying journal..
Reiserfs journal '/dev/hda1' in blocks [18..8211]: 0 transactions replayed
Checking internal tree../ 46 (of  62)/  1 (of 170)bad_leaf: block 7831560, items 0 and 1: The wrong order of items: [85206 85025 0x2ba2d001 IND (1)], [85230 85863 0x1 IND (1)]                                                                                                                              /  3 (of 170)
The problem has occurred looks like a hardware problem. If you have
bad blocks, we advise you to get a new hard drive, because once you
get one bad block  that the disk  drive internals  cannot hide from
your sight,the chances of getting more are generally said to become
much higher  (precise statistics are unknown to us), and  this disk
drive is probably not expensive enough  for you to you to risk your
time and  data on it.  If you don't want to follow that follow that
advice then  if you have just a few bad blocks,  try writing to the
bad blocks  and see if the drive remaps  the bad blocks (that means
it takes a block  it has  in reserve  and allocates  it for use for
of that block number).  If it cannot remap the block,  use badblock
option (-B) with  reiserfs utils to handle this block correctly.

bread: Cannot read the block (7889390): (Input/output error).

Warning... fsck.reiserfs for device /dev/hda1 exited with signal 6.
[root@trk]:(~)#