March 19, 201610 yr Author You can copy over lan to another computer or search for the unassigned devices plugin. How do you copy over lan if the drive can't be mounted? What would I used to find the files?
March 20, 201610 yr Community Expert Wasn’t the disk being mounted read only? If it doesn’t mount you have to run reiserfsck and rebuild the superblock.
March 20, 201610 yr Author Wasn’t the disk being mounted read only? If it doesn’t mount you have to run reiserfsck and rebuild the superblock. Now it won't mount at all. Guess i'll have to try that.
March 20, 201610 yr Author It says superblock seems to be correct. Maybe I need to try rebuild tree again?
March 20, 201610 yr Community Expert Try, and if it complains again, rebuild superblock and then run with rebuild-tree. Reiserfsck is usually very good at doing its thing, it can recover most data from very bad situations.
March 20, 201610 yr Author Try, and if it complains again, rebuild superblock and then run with rebuild-tree. In the GUI, under disk1 settings, for file system type it says Unmountable - No file system (32) Is that a different type of error, or should I proceed accordingly?
March 20, 201610 yr Author I get this error on reiserfsck --check /dev/md1 reiserfsck --check started at Sat Mar 19 17:15:42 2016 ########### Replaying journal: Done. Reiserfs journal '/dev/md1' 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) When trying to rebuild superblock I get this: sudo reiserfsck --rebuild-sb /dev/md1 reiserfsck 3.6.24 Will check superblock and rebuild it if needed Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Reiserfs super block in block 16 on 0x901 of format 3.6 with standard journal Count of blocks on the device: 732566624 Number of bitmaps: 22357 Blocksize: 4096 Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 0 Root block: 0 Filesystem is NOT clean Tree height: 0 Hash function used to sort names: "r5" Objectid map size 748, max 972 Journal parameters: Device [0x0] Magic [0x6980fdb3] Size 8193 blocks (including 1 for journal header) (first block 18) Max transaction length 1024 blocks Max batch size 900 blocks Max commit age 30 Blocks reserved by journal: 0 Fs state field: 0x3: FATAL corruptions exist. some corruptions exist. sb_version: 2 inode generation number: 3153944 UUID: 31134732-ccbc-466d-bec7-2eb8d7baa2bd LABEL: Set flags in SB: ATTRIBUTES CLEAN Mount count: 131 Maximum mount count: 30 Last fsck run: Thu Aug 22 06:57:34 2013 Check interval in days: 180 Super block seems to be correct
March 20, 201610 yr Community Expert Bad root block 0. (--rebuild-tree did not complete) This usually means you have to run again with --rebuild-tree, don't forget that you have to start the array in maintenance mode.
March 20, 201610 yr Author Bad root block 0. (--rebuild-tree did not complete) This usually means you have to run again with --rebuild-tree, don't forget that you have to start the array in maintenance mode. Trying rebuild tree again.
March 20, 201610 yr Author Rebuild tree finally completed this time without problems. Disk has mounted. Hopefully good to go!
March 20, 201610 yr And this is why I've stuck with RFS on my array disks.. the tools are just so darn good.
Archived
This topic is now archived and is closed to further replies.