[6.3.2] drive issue


Recommended Posts

HI ,

 

got a reiserfs drive that became unformatted in my tv server

did a reiserfsck --check on the disk and it told me that it could be solved with --rebuild-tree

but at 15% this stops with a segmentation error.....

so did all the obvious things as memory checks and so on but it won't finish the rebuild

 

root@R2D2:~# reiserfsck --rebuild-tree /dev/sdg1
reiserfsck 3.6.25

*************************************************************
** Do not  run  the  program  with  --rebuild-tree  unless **
** something is broken and MAKE A BACKUP  before using it. **
** If you have bad sectors on a drive  it is usually a bad **
** idea to continue using it. Then you probably should get **
** a working hard drive, copy the file system from the bad **
** drive  to the good one -- dd_rescue is  a good tool for **
** that -- and only then run this program.                 **
*************************************************************

Will rebuild the filesystem (/dev/sdg1) tree
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
Replaying journal: Done.
Reiserfs journal '/dev/sdg1' in blocks [18..8211]: 0 transactions replayed
###########
reiserfsck --rebuild-tree started at Thu Mar  9 20:41:59 2017
###########

Pass 0:
####### Pass 0 #######
Loading on-disk bitmap .. ok, 241399810 blocks marked used
Skipping 15663 blocks (super block, journal, bitmaps) 241384147 blocks will be read
0%...Segmentation fault                              left 207493688, 22914 /sec
root@R2D2:~#

 

 

so now i am stuck with a root block error

 


root@R2D2:~# reiserfsck --check /dev/sdg1
reiserfsck 3.6.25

Will read-only check consistency of the filesystem on /dev/sdg1
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 Thu Mar  9 20:38:22 2017
###########
Replaying journal: Done.
Reiserfs journal '/dev/sdg1' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..

Bad root block 0. (--rebuild-tree did not complete)

Aborted
root@R2D2:~#

 

is there a way around this?

I tried moving the drive to my movieraid server but it hangs at the same point ....

 

so it is disk specific i guess...

would like to get to solve the root block error so that i can mount it readable and get the data from it ....

is there a way to do so ?

 

i know the data is still there as i did a test with easus data recovery and it finds everything ,,,,,

but there has to be a way around this bad root block thing.... it is reiserfsck that sets it when you do a --rebuild-tree

so surely it should be solvable?

 

got another disk on my movieraid server which refused to delete some files

so again ran check it tells me to run rebuild-tree anf again segmentation fault but this time at nearly the end of the check

so now i have 2 disks which are having the root block issue ....

 

this is crazy ... is there a known issue with the current reiserfsck program on our unraids?

 

 

Edited by sacretagent
update
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.