Try to fix a broken ReiserFS / Data Recovering?

Try to fix a broken ReiserFS / Data Recovering?

[Lars Wolff]

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?

- 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

Re: Try to fix a broken ReiserFS / Data Recovering?

[Vladimir V. Saveliev]

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
> 

RE: Try to fix a broken ReiserFS / Data Recovering?

[Masthan, Dudekula (STSD)]

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 <vitaly@namesys.com>.	 

BUGS
 
	Please report bugs to the ReiserFS developers <reiserfs-dev@namesys.com>, 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:vs@namesys.com] 
Sent: Monday, June 19, 2006 5:58 PM
To: Lars Wolff
Cc: reiserfs-list@namesys.com
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
> 

Re: Try to fix a broken ReiserFS / Data Recovering?

[Lars Wolff]

Hi Vladimir!

Thanks for your Reply!!!

>> _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.

i did i as explained here:
http://martian.org/marty/2003/09/05/reiserfs-filesystem-recovery

- dd_rescue finished
- i set up a loop device with the image
- then i start reiserfsck --check, it breaks up with rebuild-tree not 
finished
- then i start reiserfsck with --rebuild-tree
- and now its at pass 3 (and in pass 2 i saw the most importatn 
directory's and files i need)

i am still wating and have always a look on the screen ;)

further infos in a few minutes

thanks & take care!
Lars

Re: Try to fix a broken ReiserFS / Data Recovering?

[Clemens Eisserer]

I had this problem too with older SuSE versions (7.? - 8.?), its a
shame that nobody found this bug for such a long time.

I too saw the same behaviour you described, but for me it has always
helped to just re-install grub. Boot up with a rescue-cd and simply
re-install grub or use yast to do so.

But maybe your problem is different and its quite unlikly to work now
that reiserfschk boild out :-/

lg Clemens

2006/6/19, Lars Wolff <support@sipex.de>:
> Hi Vladimir!
>
> Thanks for your Reply!!!
>
> >> _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.
>
> i did i as explained here:
> http://martian.org/marty/2003/09/05/reiserfs-filesystem-recovery
>
> - dd_rescue finished
> - i set up a loop device with the image
> - then i start reiserfsck --check, it breaks up with rebuild-tree not
> finished
> - then i start reiserfsck with --rebuild-tree
> - and now its at pass 3 (and in pass 2 i saw the most importatn
> directory's and files i need)
>
> i am still wating and have always a look on the screen ;)
>
> further infos in a few minutes
>
> thanks & take care!
> Lars
>
>

Re: Try to fix a broken ReiserFS / Data Recovering?

[Lars Wolff]

Hi List, hi Vladimir!

>>> _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.
> 
> i did i as explained here:
> http://martian.org/marty/2003/09/05/reiserfs-filesystem-recovery

Yesterday night reiserfsck finished up "clear" and i could mount the 
dd_rescue_imag on a loopdevice and at least to the filesystem :))))

I took the whole night to copy all data, but i alreade found everthing, 
i also got some files in "lost+found" and have to check this manually.

Do Somebody now a easy way to work with the lost+found files? 
(XXXXX_yyyyy X=inode right?)

Lars

Re: Try to fix a broken ReiserFS / Data Recovering?

[Vladimir V. Saveliev]

Hello

On Tue, 2006-06-20 at 12:14 +0200, Lars Wolff wrote:
> Hi List, hi Vladimir!
> 
> >>> _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.
> > 
> > i did i as explained here:
> > http://martian.org/marty/2003/09/05/reiserfs-filesystem-recovery
> 
> Yesterday night reiserfsck finished up "clear" and i could mount the 
> dd_rescue_imag on a loopdevice and at least to the filesystem :))))
> 
> I took the whole night to copy all data, but i alreade found everthing, 
> i also got some files in "lost+found" and have to check this manually.
> 
> Do Somebody now a easy way to work with the lost+found files? 
> (XXXXX_yyyyy X=inode right?)
> 

Real names of files of directories which got into lost+found are lost.
Instead XXXXX_yyyyy are generated. XXXXX is inode number of a directory
in which file was created. yyyyy is inode number of file.

If XXXXX_yyyyy is a directory - files below (if any) have their normal
names.
For each of XXXXX_yyyyy you may try to find a directory with inode
number XXXXX (find -inum XXXXX). If such directory exists - it is
possible that XXXXX_yyyyy belongs to it.

And, use file(1) for binary files.

> Lars
>