April 23, 20206 yr I was having issues with some un deletable folders on one of my disks. So I did a filesystem check for reiserfs. The check suggested that a reiserfs --rebuild-tree be run. Just when the rebuild was about to begin there was a power outage. The machine did not shut down because of the UPS. But because power did not come back for a while I had no option but to power down the machine from the web UI, guessing thats better than an ungraceful shutdown. Now when the machine is powered up I have disk 1 greyed out with the message Unmountable : No File System I have a parity disk and the message next to it says parity is valid. EDIT: Without noticing the status of the array I copied some data to the server and this has indeed gone to some share which does not use cache disk Please please help! Edited April 23, 20206 yr by extremeaudio
April 23, 20206 yr Author I'm guessing I just have to treat the corrupt disk like a failed disk, let unraid format the disk and then let parity write / rebuild. Is that correct?
April 23, 20206 yr Community Expert 4 minutes ago, extremeaudio said: Is that correct? No, parity can't fix filesystem corruption, if you were in the middle of a --rebuild-tree you need to run it again.
April 23, 20206 yr Author Ok, but would it be better if I rebuild the data from parity and then run --rebuild-tree or do it right away? Thanks in advance. Edited April 23, 20206 yr by extremeaudio
April 23, 20206 yr Community Expert 13 minutes ago, extremeaudio said: let unraid format the disk DO NOT FORMAT!!!
April 23, 20206 yr Author So, just to confirm..at this stage I should: 1. stop the array 2. select the disk that was having a reiserfck check --rebuild-tree running on it 3. restart the check with the above parameter Correct?
April 23, 20206 yr Community Expert Start the array in maintenance mode and run reiserfsck --rebuild-tree on that disk.
April 24, 20206 yr Author Woe is me Cannot believe my misfortune. The reiserfsck build went through a pass 0 and was half way into pass 1 when my klutz of a wife trying to reboot the router to check a faulty internet connection somehow managed to pull the plug on the server :(( After restarting I'm at square one, one disk with file system error and a parity check running. What do i do ?? Stop the parity check and restart the reiserfsck rebuild ? Or let parity check complete ?
April 24, 20206 yr Community Expert If there are sync errors you'll need to run a correcting check, auto check is non correct, that can be done before or after the filsystem check.
April 24, 20206 yr Author Yes there are sync errors. So you mean i need to run the parity sync after the parity check completes and then get back to reiserfsck check. Please advise if this sounds correct.
April 24, 20206 yr Community Expert No, cancel current check (since it's non correct), start a correcting check, then run reiserfsck.
April 30, 20206 yr Author After around 4 days and 3 passes the reiserfsck --rebuild-tree process has stopped. Under Main it still shows no mountable filesystem Output as below: reiserfsck 3.6.27 ************************************************************* ** 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/md1) tree Will put log info to 'stdout' Replaying journal: Replaying journal: Done. Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed ########### reiserfsck --rebuild-tree started at Sun Apr 26 02:08:05 2020 ########### Pass 0: Loading on-disk bitmap .. ok, 1337701014 blocks marked used Skipping 67827 blocks (super block, journal, bitmaps) 1337633187 blocks will be read 0%....20%....40%....60%....80%....100% "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 1337633187 Leaves among those 1335754 - leaves all contents of which could not be saved and deleted 2 Objectids found 60573 Pass 1 (will try to insert 1335752 leaves): Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....100% Flushing..finished 1335752 leaves read 1335641 inserted 111 not inserted Pass 2: 0%....20%....40%....60%....80%....100% Flushing..finished Leaves inserted item by item 111 Pass 3 (semantic): Flushing..finished Files found: 53775 Directories found: 6790 Broken (of files/symlinks/others): 3 Pass 3a (looking for lost dir/files): Looking for lost directories: Flushing..finished Pass 4 - finished Deleted unreachable items 2144 Flushing..finished Syncing..finished ########### reiserfsck finished at Thu Apr 30 19:21:33 2020 ########### ####### Pass 0 ####### block 983788280: The number of items (6) is incorrect, should be (0) - corrected block 983788280: The free space (77) is incorrect, should be (4072) - corrected block 1243466290: The free space (1) is incorrect, should be (2000) - corrected pass0: vpf-10110: block 1243466290, item (0): Unknown item type found [134219776 134219776 0x8000800 ??? (15)] - deleted 60563 directory entries were hashed with "r5" hash. ####### Pass 1 ####### ####### Pass 2 ####### ####### Pass 3 ######### vpf-10680: The file [289584 289592] has the wrong block count in the StatData (13757840) - corrected to (1475656) vpf-10680: The file [277423 277424] has the wrong block count in the StatData (5858760) - corrected to (1676080) vpf-10680: The file [3818 3829] has the wrong block count in the StatData (13759984) - corrected to (13745456) vpf-10680: The file [281229 281238] has the wrong block count in the StatData (4586824) - corrected to (4586656) vpf-10680: The file [281485 281493] has the wrong block count in the StatData (9158152) - corrected to (9145000) vpf-10680: The file [281040 281071] has the wrong block count in the StatData (9169056) - corrected to (9162720) vpf-10680: The file [1392 1488] has the wrong block count in the StatData (3900632) - corrected to (3899720) vpf-10680: The file [277345 277349] has the wrong block count in the StatData (3883984) - corrected to (2965376) vpf-10680: The file [2744 2755] has the wrong block count in the StatData (22139656) - corrected to (22139632) vpf-10680: The file [283479 283492] has the wrong block count in the StatData (13746896) - corrected to (13712000) ####### Pass 3a (lost+found pass) ######### What next?
April 30, 20206 yr Author Woo Hoo!! Array started and all looks ok to my untrained eye. Love you for this man! diagnostics.zip
April 30, 20206 yr Community Expert 👍 Note that reiserfs is not recommended for years now, you should convert to xfs.
April 30, 20206 yr Author Noted. These are disks from a 2011 setup, hence. Will make the shift. Again, Thanks a lot man. Really appreciate.
April 30, 20206 yr Community Expert 5 minutes ago, extremeaudio said: These are disks from a 2011 setup, hence. Will make the shift. Do you know what has to be done for this?
April 30, 20206 yr Author Not very sure, was planning to read up on it. If there is some easy to use guide please advise. Thanks
April 30, 20206 yr Community Expert There has been a lot written about it on this forum, including a topic pinned near the top of this same subforum with link to a somewhat long wiki and a link to the long thread that was very active when many people were first doing this. It depends on how comfortable you are, working with things on the server at the disk level, as to how complicated you think this is. But long story short, when you change the filesystem of a disk, it gets formatted to the new filesystem. So if you want to keep any of that disk's data, you have to put it elsewhere. From your diagnostics it looks like most of your disks are pretty full. If you can, starting with adding a new disk assigned to a new data slot and formatted XFS would be simplest, then you could move all files from another disk to that new XFS disk so you could reformat that other disk as XFS. I say simplest because if you start with an empty disk then you can be sure you have space to move all of a disk. Then that reformatted disk could be the target for moving the files off another disk, repeat as necessary, doing the smaller disks last since they don't have space for the contents of the larger disks obviously. Looks like you only have 5.5TB free so that won't be enough capacity to just shuffle things around on your existing disks. You could move everything off the smaller disk2 to other disks, reformat it as XFS, then replace / rebuild it to a larger disk and get the free capacity needed to work with those larger disks. The unBALANCE plugin can help with shuffling things between disks. You don't have so many disks compared to some, but I would expect it to take a few days to get them all done. Do you have backups of anything important and irreplaceable?
May 1, 20206 yr Author I am comfortable with all of the above. Should not be an issue. Planning to 1. install a windows VM to backup/ sync my data to a Google Drive 2. delete a lot of data that serves no point sitting on the hard disks 3. see if that leaves me with enough space to free up disk by disk and format to XFS Will post back if any difficulties. Thanks again.
Archived
This topic is now archived and is closed to further replies.