/home totally hosed (long)

pete_bogg · 01-16-2005, 09:10 AM

I'm totally bummed...

My /home partition (reiserfs) has developed a bad block which will not let me get to my data. The following is the result of running reiserfsck on this partition:

Code:

root@slax:/# reiserfsck /dev/hde4
reiserfsck 3.6.18 (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/hde4
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 Sun Jan 16 09:43:05 2005
###########
Replaying journal..
Reiserfs journal '/dev/hde4' in blocks [18..8211]: 0 transactions replayed

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 (196608): (Input/output error).

Aborted
root@slax:/#

NOTE: I normally run Slackware 10 with kernel 2.4.26, but used Slax 4.2 in case there was something wrong with my / partition.

Here is the result of debugreiserfs -D:

Code:

root@slax:~# debugreiserfs -D /dev/hde4
debugreiserfs 3.6.18 (2003 www.namesys.com)


Filesystem state: consistent

Reiserfs super block in block 16 on 0x2104 of format 3.6 with standard journal
Count of blocks on the device: 979965
Number of bitmaps: 30
Blocksize: 4096
Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 839978
Root block: 45915
Filesystem marked as cleanly umounted
Tree height: 4
Hash function used to sort names: "r5"
Objectid map size 274, max 972
Journal parameters:
        Device [0x0]
        Magic [0x7ace460d]
        Size 8193 blocks (including 1 for journal header) (first block 18)
        Max transaction length 1024 blocks
        Max batch size 900 blocks
        Max commit age 30
Blocks reserved by journal: 0
Fs state field: 0x0:
sb_version: 2
inode generation number: 58592
UUID: 7cca7b96-8c0c-4533-83fa-f9457d6a8f52
LABEL:
Set flags in SB:
        ATTRIBUTES CLEAN

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 (196608): (Input/output error).

Aborted
root@slax:~#

Is there anything I can do to get to the 5 user directories on this /home drive?

Thankfully, I burned a cdrom with e-mail and gnucash files not to long ago. I have a full data backup on cdrom from several months ago, so all is not lost.

Please give me direction. Thanks.

keefaz · 01-16-2005, 09:37 AM

There is the option --rebuild-tree like
reiserfsck --rebuild-tree /dev/hde4

But read man reiserfsck before, especially the advices how to use it near the end

pete_bogg · 01-16-2005, 06:53 PM

keefaz,

I issued reiserfsck --rebuild-tree /dev/hde4 as suggested.

The results were similiar to the results above, the program aborts noting the bad block.

I'm at a loss. Is the bad block holding reiserfs critical information? Otherwise, I would assume that I should be able to read the users directories.

If I re-format and attempt to re-populate the data with old archives, I would assume that the problem will occur again.

Anyway, I am lost on what to do.

Ideas?

slackMeUp · 01-16-2005, 11:26 PM

Go to the drive manufacture's website and download their drive diagnostic utilities.. . . they boot from a disk and run tests on your hard drive... it will be your best bet when it comes to fixing bad blocks.

And as for the future of this drive... I would not use it in any production environment.

pete_bogg · 01-17-2005, 08:23 PM

slackMeUp .... You da MAN!! (or WOMAN, which ever the case.)

My harddrive is a IBM Deskstar. IBM turned support of these to Hitachi. Their diagnostic and repair tool did the trick.

Now, I can get to the user accounts and start archiving. Hopefully, I can get a new harddrive next payday.

slackMeUp · 01-17-2005, 09:59 PM

Nothing like a little DFT to get your blood flowing. . . hehe. Glad I could help.