Yipee Posted February 25, 2017 Share Posted February 25, 2017 Hi Guys, I precleared disk5 then rebuild the array, parity show valid and finding 0 errors but now my disk5 is unmountable. I had some file corruption on disk6 before which I already corrected with file system check so not sure if that cause any issue. Attached is the log file. Any help and suggestions would be appreciated. tower-diagnostics-20170224-1921.zip Quote Link to comment
JorgeB Posted February 25, 2017 Share Posted February 25, 2017 You need to check filesystem on disk5:https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_ReiserFS_using_unRAID_v5_or_later Quote Link to comment
Yipee Posted February 26, 2017 Author Share Posted February 26, 2017 Ran check files system on disk5 then with rebuild tree option two times but both seem to be stuck at the same spot and didn't finished. My array maybe corrupted that's why it didn't rebuild disk5 correctly. What should be my approach? Thanks for the help. tower-diagnostics-20170226-1313.zip Quote Link to comment
JorgeB Posted February 27, 2017 Share Posted February 27, 2017 Post the output of reiserfsck Quote Link to comment
Yipee Posted February 27, 2017 Author Share Posted February 27, 2017 Here's the log: Not available 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/md5) tree Will put log info to 'stdout' Replaying journal: Replaying journal: Done. Reiserfs journal '/dev/md5' in blocks [18..8211]: 0 transactions replayed ########### reiserfsck --rebuild-tree started at Mon Feb 27 10:08:58 2017 ########### Pass 0: Loading on-disk bitmap .. ok, 201797007 blocks marked used Zero bit found in on-disk bitmap after the last valid bit. Fixed. ####### Pass 0 ####### init_source_bitmap: Bitmap 6082 (of 32768 bits) is wrong - mark all blocks [199294976 - 199327744] as used init_source_bitmap: Bitmap 6083 (of 32768 bits) is wrong - mark all blocks [199327744 - 199360512] as used init_source_bitmap: Bitmap 6084 (of 32768 bits) is wrong - mark all blocks [199360512 - 199393280] as used init_source_bitmap: Bitmap 6085 (of 32768 bits) is wrong - mark all blocks [199393280 - 199426048] as used init_source_bitmap: Bitmap 6086 (of 32768 bits) is wrong - mark all blocks [199426048 - 199458816] as used init_source_bitmap: Bitmap 6087 (of 32768 bits) is wrong - mark all blocks [199458816 - 199491584] as used init_source_bitmap: Bitmap 6088 (of 32768 bits) is wrong - mark all blocks [199491584 - 199524352] as used . . . . . init_source_bitmap: Bitmap 11153 (of 32768 bits) is wrong - mark all blocks [365461504 - 365494272] as used init_source_bitmap: Bitmap 11154 (of 32768 bits) is wrong - mark all blocks [365494272 - 365527040] as used init_source_bitmap: Bitmap 11155 (of 32768 bits) is wrong - mark all blocks [365527040 - 365559808] as used init_source_bitmap: Bitmap 11156 (of 32768 bits) is wrong - mark all blocks [365559808 - 365592576] as used init_source_bitmap: Bitmap 11157 (of 32768 bits) is wrong - mark all blocks [365592576 - 365625344] as used init_source_bitmap: Bitmap 11158 (of 32768 bits) is wrong - mark all blocks [365625344 - 365658112] as used init_source_bitmap: Bitmap 11159 (of 32768 bits) is wrong - mark all blocks [365658112 - 365690880] as used init_source_bitmap: Bitmap 11160 (of 32768 bits) is wrong - mark all blocks [365690880 - 365723648] as used init_source_bitmap: Bitmap 11161 (of 32768 bits) is wrong - mark Skipping 19389 blocks (super block, journal, bitmaps) 366265249 blocks will be read 0%....20%....40%....60%... Quote Link to comment
JorgeB Posted February 27, 2017 Share Posted February 27, 2017 (edited) There's no error so can't guess the problem, try running reiserfsck on another computer and/or with unRAID v6.2.4 as it includes an earlier release of reiser-progs, use a trial key on another PC if you don't have another server available. Edited February 27, 2017 by johnnie.black Quote Link to comment
Yipee Posted February 27, 2017 Author Share Posted February 27, 2017 Is downgrading to unRAID v6.2.4 from v6.3.2 a simple process? Can you point me in the right direction? Quote Link to comment
JorgeB Posted February 27, 2017 Share Posted February 27, 2017 Downgrade itself is very easy, just replace the 3 bz* files with those from v6.2.4 and reboot, if you use dockers and/or VMs some additional steps my be needed for them to work (or upgrade again after running reiserfsck) Quote Link to comment
Yipee Posted February 28, 2017 Author Share Posted February 28, 2017 Johnnie.black, you are the man! Thank you. I got it working again. I suspect I my array still has some file corruptions. What's the best way to check this? Quote Link to comment
JorgeB Posted February 28, 2017 Share Posted February 28, 2017 If all disks are reiser run reiserfsck --check on all of them, if any corruptions are found use the option mentioned by the reiserfsck output. Quote Link to comment
Recommended Posts
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.