Hi,
The following paragraph is snippet of reiserfsck man page.
AN EXAMPLE OF USING reiserfsck
1. You think something may be wrong with a reiserfs partition on
/dev/hda1 or you would just like to perform a periodic disk check.
2. Run reiserfsck --check --logfile check.log /dev/hda1. If reiserfsck
--check exits with status 0 it means no errors were discovered.
3. If reiserfsck --check exits with status 1 (and reports about fixable
corruptions) it means that you should run reiserfsck --fix-fixable --logfile
fixable.log /dev/hda1.
4. If reiserfsck --check exits with status 2 (and reports about fatal
corruptions) it means that you need to run reiserfsck --rebuild-tree. If
reiserfsck --check fails in some way you should also run reiserfsck
--rebuild-tree, but we also encourage you to submit this as a bug report.
5. Before running reiserfsck --rebuild-tree, please make a backup of
the whole partition before proceeding. Then run reiserfsck --rebuild-tree
--logfile rebuild.log /dev/hda1.
6. If the reiserfsck --rebuild-tree step fails or does not recover what
you expected, please submit this as a bug report. Try to provide as much
information as possible including your platform and Linux kernel version. We
will try to help solve the problem.
EXIT CODES
reiserfsck uses the following exit codes:
0 - No errors.
1 - File system errors corrected.
2 - Reboot is needed.
4 - File system fatal errors left uncorrected,
reiserfsck --rebuild-tree needs to be launched.
6 - File system fixable errors left uncorrected,
reiserfsck --fix-fixable needs to be launched.
8 - Operational error.
16 - Usage or syntax error.
AUTHOR
This version of reiserfsck has been written by Vitaly Fertman <[EMAIL
PROTECTED]>.
BUGS
Please report bugs to the ReiserFS developers <[EMAIL PROTECTED]>,
providing as much information as possible--your hardware, kernel, patches,
settings, all printed messages, the logfile; check the syslog file for any
related information.
TODO
Faster recovering, signal handling.
>From the fourth point What I understood is, failure of " reiserfsck --check "
> with error code other than 1 and 2 is a bug. Is it correct ?
And the last table tells that reiserfsck still not hadling signals. Is it
correct ?
Regards,
Masthan
-----Original Message-----
From: Vladimir V. Saveliev [mailto:[EMAIL PROTECTED]
Sent: Monday, June 19, 2006 5:58 PM
To: Lars Wolff
Cc: [email protected]
Subject: Re: Try to fix a broken ReiserFS / Data Recovering?
Hello
On Mon, 2006-06-19 at 11:28 +0200, Lars Wolff wrote:
> Hi there,
>
> i am very new to this list, i just signed up today, because i got some
> problems with a broken ReiserFS since yesterday.
>
> _The problem_
> Yesterday my Router/Server (Suse Linux 8.1, 40GB IDE HDD with
> ReiserFS) hang up. After a reboot it only starts to "load stage2 of
> Grub", which fails and ends up in the grub minimal bash.
>
> _What i do to resolve the problem_
> I downloaded the Suse Live-CD 9.1 and did a clean boot from it. I Try
> to mount the volume, what end up with "Falscher Dateisystemtyp,
> ungültige Optionen, der »Superblock« von /dev/hdb2 ist beschädigt oder
> es sind zu viele Dateisysteme eingehängt" (=corrupt superblock)
>
> Then I tried reiserFs Check wich ends up in: Bad root block 0.
> (--rebuild-tree did not complete).
>
> Ok, i followed the instructions in the following "bad block info text"
> and did a reiserFs -B badblocksfile --rebuild-tree. Wich aborts and
> said "badblock in ....".
>
> Right now i am doing a complete Backup image with dd_rescue, after
> this i would like to run /sbin/badblocks, as explained in the Faq
> (http://www.namesys.com/bad-block-handling.html) and run then reiserfs
> -B again.
>
> _My Questions_
> - Am i right in doing these actions to try to resolve the problem of
> my harddisk, and HOPEFULLY to recover the Data?
>
after dd_rescue completes - please run reiserfsck (3.6.19, without any options
but filename) on backup image and let us know what it says.
> - Is there anything i should try/do else?
>
> - Do you now somebody/any company, wich do a real data-recovering von
> ReiserFS Disk? Its only 40GB but there are some data on it wich are
> very important. (don't ask after the backups, they broke last week on
> the extern hdd! :(( )
>
> Hopefully you guys can help me,
> thanks a lot!!!! :)
>
> Lars
>
