luksak Posted June 13, 2016 Share Posted June 13, 2016 A few months back I had a disk failure which I fixed. Since then I have a few issues with my array. The first one is that I am unable to flag anything in Mac OSX finder. when traing to do so I get promted for my password and after inputting that I get the following error: The operation can’t be completed because you don’t have the necessary permission. The second issue is with docker containers. I have the Plex and the rutorrent containers running. since that disk failure they both start at first but I am never able to access their web UI. What might be wrong? Is this a file permission issue? I checked the folder where I tried to change the permissions and everything seemed fine. What inforamtion could I provide to solve this? Attached you can find my syslog. The interesting part is this: Jun 13 09:37:54 Tower kernel: REISERFS error (device md1): vs-4080 _reiserfs_free_block: block 569210750: bit already cleared Jun 13 09:37:54 Tower kernel: REISERFS (device md1): Remounting filesystem read-only syslog.txt Quote Link to comment
Squid Posted June 13, 2016 Share Posted June 13, 2016 No. There is corruption in the file system. You need to stop the array and restart it in maintenance mode then go to main, disk1 and check the file system Sent from my LG-D852 using Tapatalk Quote Link to comment
luksak Posted June 13, 2016 Author Share Posted June 13, 2016 Ok, I will try that and give feedback. Thank you! Quote Link to comment
luksak Posted June 15, 2016 Author Share Posted June 15, 2016 Here is the check of disk 1. I did them for the other ones as well, but those look good so far. disk1.txt disk2.txt disk4.txt disk3.txt Quote Link to comment
luksak Posted June 15, 2016 Author Share Posted June 15, 2016 And here is disk 5. disk5.txt Quote Link to comment
RobJ Posted June 15, 2016 Share Posted June 15, 2016 As I'm sure you saw, Disk 1 is corrupted and it instructed you to run reiserfsck again with the --rebuild-tree option. That's your next step. The Check Disk File systems wiki page has a little help for this, for both webGui and command line usage. Quote Link to comment
luksak Posted June 20, 2016 Author Share Posted June 20, 2016 Ok, I did that. Attached is the output. Is my disk fine now? At least my permission issues has been resolved. disk1.txt Quote Link to comment
RobJ Posted June 20, 2016 Share Posted June 20, 2016 That was a lot of work performed on your drive! It appeared to be correcting everything it found, but on completion it appears to be reporting additional issues, and attempting corrections there too. I'd run another check on the drive. Once you do get a clean check, you'll need to deal with the files moved to the lost+found folder. Quote Link to comment
luksak Posted June 22, 2016 Author Share Posted June 22, 2016 Here is the next log. I am running it again... disk1_3.txt Quote Link to comment
luksak Posted June 22, 2016 Author Share Posted June 22, 2016 And again. disk1_3.txt Quote Link to comment
RobJ Posted June 23, 2016 Share Posted June 23, 2016 And again. You attached the same file, perhaps you intended to attach disk1-4.txt? Quote Link to comment
luksak Posted June 23, 2016 Author Share Posted June 23, 2016 Yes. Sorry for that. Here is last two runs. Should I keep doing that? disk1_4.txt disk1_5.txt Quote Link to comment
RobJ Posted June 24, 2016 Share Posted June 24, 2016 Here is last two runs. Should I keep doing that? No, not with the --rebuild-tree option. Try with just the --check option. Quote Link to comment
luksak Posted June 25, 2016 Author Share Posted June 25, 2016 OK, looks good. In the lost+found share there are some files, but I don't know what do there: drwx------ 1 nobody users 368 Jun 20 00:01 ./ drwxrwxrwx 1 nobody users 360 Mar 23 10:00 ../ -rw------- 1 5598404 root 4096 Mar 6 1970 1284474_1288503 -r-Sr-S--T 1 539980910 1819047280 77824 Jul 1 2033 1284474_1288506 -rw------- 1 151587362 1528850025 4096 Sep 17 2028 1284474_1288507 ---------- 1 root root 20480 Jan 1 1970 1284474_1288510 -rw------- 1 31231 root 4096 Jan 1 1970 1284474_1288511 drwxrwsrwx 1 nobody users 80 Nov 9 2014 1284474_1288514/ -rwxrwxrwx 1 nobody users 352974734 Nov 6 2014 323178_323851* ---------- 1 root root 4075520 Jan 1 1970 323178_565143 drwxrwsrwx 1 nobody users 120 Nov 9 2014 570112_570188/ drwxrwsrwx 1 nobody users 120 Nov 9 2014 570112_570197/ disk1_6.txt Quote Link to comment
RobJ Posted June 27, 2016 Share Posted June 27, 2016 The Check Disk File systems wiki page has some comments about this, in the ReiserFS section, about other users with a lost+found folder and how they handled it. Quote Link to comment
luksak Posted August 17, 2016 Author Share Posted August 17, 2016 I just ran into the same issue again and tried to run reiserfsck again with the --rebuild-tree option. This time the drive showed up as unformatted. is it safe to reformat the disk and rebuild the array? attached is the syslog. systlog.txt Quote Link to comment
JorgeB Posted August 17, 2016 Share Posted August 17, 2016 is it safe to reformat the disk and rebuild the array? Format is never an option to recover data. Did you try running reiserfsck again? You have to start with --chech option, only use --rebuild-tree if told so after the --check. Quote Link to comment
luksak Posted August 17, 2016 Author Share Posted August 17, 2016 Ok, so, I am runing reiserfsck --check now. Quote Link to comment
luksak Posted August 18, 2016 Author Share Posted August 18, 2016 This is the output of reiserfsck --check: reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md1 Will put log info to 'stdout' ########### reiserfsck --check started at Thu Aug 18 00:52:11 2016 ########### Replaying journal: Replaying journal: Done. Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. Bad root block 0. (--rebuild-tree did not complete) Quote Link to comment
luksak Posted August 21, 2016 Author Share Posted August 21, 2016 Still the same issue... But wouldn't rebuilding the array solve the problem? Quote Link to comment
JorgeB Posted August 21, 2016 Share Posted August 21, 2016 Nope, rebuilding doesn't fix filesystem issues, rebuilt disk will be identical to current disk, filesystem corruption included. Quote Link to comment
luksak Posted August 21, 2016 Author Share Posted August 21, 2016 Meaning the data is lost? Quote Link to comment
JorgeB Posted August 21, 2016 Share Posted August 21, 2016 Reiserfsck is usually very good at doing its thing, try running it a few more times, always start with --check, only use --rebuild-tree if the output shows that corruptions found can only be fixed by using --rebuild-tree or --rebuild-tree did not complete (this last ones means that previous --rebuil-tree didn't run till the end). Looking a your OP, looks like this disk was badly corrupted, probably from a bad rebuild, in case you get it back recommend to copy all its data and format it, to make sure file system is OK for the future. Quote Link to comment
luksak Posted August 21, 2016 Author Share Posted August 21, 2016 Ok, I'll try again. Maybe some important information: I ran reiserfsk because my disk was mounted read-only. So after running reiserfsk --rebuild-tree, parity has never been rebuilt. Shoulnd't the data remain in the read-only state in parity? That way I could at least copy the data. Here is the log of my last run of reiserfsk --rebuild-tree. Something important to note is the notice that the drive is full. Might that help fixing the issue? reiserfsck 3.6.24 ************************************************************* ** 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 Fri Aug 19 10:13:07 2016 ########### Pass 0: Loading on-disk bitmap .. ok, 732566633 blocks marked used Skipping 30567 blocks (super block, journal, bitmaps) 732536066 blocks will be read 0%....20%.####### Pass 0 ####### block 162464995: The number of items (27200) is incorrect, should be (1) - corrected block 162464995: The free space (33792) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 162464995, item (0): Unknown item type found [99584 65821 0x185000a (12)] - deleted block 162465592: The number of items (27200) is incorrect, should be (1) - corrected block 162465592: The free space (33792) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 162465592, item (0): Unknown item type found [99584 65821 0x185000a (12)] - deleted block 165250540: The number of items (27200) is incorrect, should be (1) - corrected block 165250540: The free space (33792) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 165250540, item (0): Unknown item type found [99584 65821 0x185000a (12)] - deleted block 177010226: The number of items (27200) is incorrect, should be (1) - corrected block 177010226: The free space (33792) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 177010226, item (0): Unknown item type found [99584 65822 0x1850009 (12)] - deleted block 177011792: The number of items (27200) is incorrect, should be (1) - corrected block 177011792: The free space (33792) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 177011792, item (0): Unknown item type found [99584 65822 0x1850009 (12)] - deleted block 177011933: The number of items (27200) is incorrect, should be (1) - corrected block 177011933: The free space (33792) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 177011933, item (0): Unknown item type found [99584 65822 0x1850009 (12)] - deleted block 177013750: The number of items (27200) is incorrect, should be (1) - corrected block 177013750: The free space (33792) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 177013750, item (0): Unknown item type found [99584 65822 0x1850009 (12)] - deleted block 177196645: The number of items (27200) is incorrect, should be (1) - corrected block 177196645: The free space (33792) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 177196645, item (0): Unknown item type found [167772417 99584 0x1850011 (12)] - deleted block 177198708: The number of items (27200) is incorrect, should be (1) - corrected block 177198708: The free space (33792) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 177198708, item (0): Unknown item type found [167772417 99584 0x1850011 (12)] - deleted block 177465153: The number of items (21) is incorrect, should be (1) - corrected block 177465153: The free space (388) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 177465153, item (0): Unknown item type found [251658628 99328 0x184000b (12)] - deleted block 177467354: The number of items (21) is incorrect, should be (1) - corrected block 177467354: The free space (388) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 177467354, item (0): Unknown item type found [251658628 99328 0x184000b (12)] - deleted block 179674012: The number of items (21) is incorrect, should be (1) - corrected block 179674012: The free space (389) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 179674012, item (0): Unknown item type found [150995201 99584 0x184001d (12)] - deleted block 179676871: The number of items (21) is incorrect, should be (1) - corrected block 179676871: The free space (389) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 179676871, item (0): Unknown item type found [150995201 99584 0x184001d (12)] - deleted block 179677646: The number of items (21) is incorrect, should be (1) - corrected block 179677646: The free space (389) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 179677646, item (0): Unknown item type found [150995201 99584 0x184001d (12)] - deleted block 180182935: The number of items (27200) is incorrect, should be (1) - corrected block 180182935: The free space (33792) is incorrect, should be (...40%....60%....80%....100% "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 732536066 Leaves among those 790548 - leaves all contents of which could not be saved and deleted 21 Objectids found 334126 Pass 1 (will try to insert 790527 leaves): Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....Not enough allocable blocks, checking bitmap...there are 1 allocable blocks, btw out of disk space 4048) - corrected pass0: vpf-10110: block 180182935, item (0): Unknown item type found [369099140 99584 0x1850006 (12)] - deleted block 180188895: The number of items (27200) is incorrect, should be (1) - corrected block 180188895: The free space (33792) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 180188895, item (0): Unknown item type found [369099140 99584 0x1850006 (12)] - deleted block 180189189: The number of items (27200) is incorrect, should be (1) - corrected block 180189189: The free space (33792) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 180189189, item (0): Unknown item type found [369099140 99584 0x1850006 (12)] - deleted block 180221320: The number of items (34) is incorrect, should be (1) - corrected block 180221320: The free space (388) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 180221320, item (0): Unknown item type found [285213060 99584 0x1850009 (12)] - deleted block 180224721: The number of items (34) is incorrect, should be (1) - corrected block 180224721: The free space (388) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 180224721, item (0): Unknown item type found [285213060 99584 0x1850009 (12)] - deleted block 180227787: The number of items (34) is incorrect, should be (1) - corrected block 180227787: The free space (388) is incorrect, should be (4048) - corrected pass0: vpf-10110: block 180227787, item (0): Unknown item type found [285213060 99584 0x1850009 (12)] - deleted 334125 directory entries were hashed with "r5" hash. ####### Pass 1 ####### 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.