Bad blocks on reiserfs
 

I have a hard drive that has recently developed some bad blocks. It's a reiserfs filesystem. I've tried using reiserfsck to check it and get the following results.


Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Thu Jan 25 11:34:50 2007
###########
Replaying journal..
Reiserfs journal '/dev/hdd1' 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 (6914048): (Input/output error).

Aborted

I've taken that block and put it in a flie called /root/blocks.log and used reiserfsck --fix-fixable -B /root/blocks.log and I get the following error.

reiserfsck --fix-fixable -B /root/blocks.log /dev/hdd1
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 check consistency of the filesystem on /dev/hdd1
and will fix what can be fixed without --rebuild-tree
Bad block list will contain only blocks specified in '/root/blocks.log' file
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
create_badblock_bitmap: block number (6914048) belongs to system reiserfs area. It cannot be relocated.

Does anyone know of a way I can get this drive mounted so I can recover at least some of the data off of it?

Thanks in advance.

--Aric

I will quote myself from another thread:
Obtain the block size for a reiserfs filesystem (look at the block size number):
Read the block size and use it in the next code.
To know if it has badblocks and save list to floppy:
To fix using that list of bad blocks:
To rebuild a reiserfs partition:
Following that order will check and mark the bad blocks, and rebuild the reiserfs tree, to keep using the FS.