March 24, 201412 yr I have a serious problem with my array and am asking for advice or assistance from the experts here. And no, stupidly, I did not capture any syslogs. I had a relatively new (just a few weeks) drive red ball while saving a video file. Being fairly confident that the drive was OK, I stopped the array, unassigned/reassigned the drive, restarted the array and the instant rebuild started a second drive redballed! I ran reiserfsck --check on the second drive and it told me that the super block was corrupted and I should run reiserfsck --rebuild-sb. I did some research and found this thread: http://lime-technology.com/forum/index.php?topic=1483 I followed the instructions and the process appeared to complete although it issued no messages. I then reran reiserfsck --check with the following result: reiserfsck --check started at Mon Mar 24 17:39:56 2014 ########### Replaying journal: Done. Reiserfs journal '/dev/sdh' in blocks [18..8211]: 0 transactions replayed Zero bit found in on-disk bitmap after the last valid bit. Checking internal tree.. Bad root block 0. (--rebuild-tree did not complete) I am curious about the last line concerning --rebuild-tree since I did not run it with that option. Should I? The second failed drive is a 3TB which was almost completely full. I would really like to recover as much from it as possible. The first drive probably only had a few hundred GB on it and I am resigned that there is probably no way to recover data from it since a parity rebuild had started. Is my worst case scenario doing a "new configuration" without either of these drives? Thanks in advance for any help.
March 25, 201412 yr I hope you did not try and rebuild the super block on /dev/sdh? If so you have almost certainly corrupted your file system and destroyed the partition table on the disk as it should have been on /dev/sdh1 (i.e. the first partition and not the whole drive). It may be possible to reover from this - I am not sure. You will need to wait for someone more knowledgeable to chime in.
March 25, 201412 yr Author I hope you did not try and rebuild the super block on /dev/sdh? If so you have almost certainly corrupted your file system and destroyed the partition table on the disk as it should have been on /dev/sdh1 (i.e. the first partition and not the whole drive). It may be possible to reover from this - I am not sure. You will need to wait for someone more knowledgeable to chime in. Doh! I did not pick up on the difference and did run the super block rebuild on /dev/sdh. Am I screwed on recovering any data from this drive?
March 25, 201412 yr I hope you did not try and rebuild the super block on /dev/sdh? If so you have almost certainly corrupted your file system and destroyed the partition table on the disk as it should have been on /dev/sdh1 (i.e. the first partition and not the whole drive). It may be possible to reover from this - I am not sure. You will need to wait for someone more knowledgeable to chime in. Doh! I did not pick up on the difference and did run the super block rebuild on /dev/sdh. Am I screwed on recovering any data from this drive? I am sure I have seen threads that talk about recovering from this as other people have made the same mistake! However there we're some steps involved in locating where the first partition started and resetting the partition table that I cannot remember the details of.
March 25, 201412 yr Author Thanks itimpi. You have given me hope all is not lost with this drive. I am cloning the drive and wading through search results now.
Archived
This topic is now archived and is closed to further replies.