I was sure it was finished. Could I have been mistaken? I have attached the report.

Disk6 reiserfsck report.txt

If that's the complete output it didn't finish, you need to run it again.

Do I need to run a normal check (without extensions) first or du I run it with --rebuild-tree at once?

 

I am pretty sure it was not running this morning, but I might be mistaken.

Edited September 1, 20178 yr by kno

run with --rebuild-tree

2 minutes ago, johnnie.black said:

run with --rebuild-tree

 

Just to be sure, in "Maintenance Mode" right?

yes

Likely same scenario as yesterday:

 

-All HDDs have spun down

 

-Report similar as yesterday. Stops with: ####### Pass 1 #######

 

I have not yet started unraid to check, but if the report is not right, then there might be somehting else I need to do. Any suggestions?

 

Edit: Screenshots removed.

 

Edited September 4, 20178 yr by kno

I found this post:

 

 

Is this the same as my problem?

 

Edit: Diagnostics removed.

 

Edited September 4, 20178 yr by kno

24 minutes ago, kno said:

Likely same scenario as yesterday:

 

-All HDDs have spun down

 

-Report similar as yesterday. Stops with: ####### Pass 1 #######

 

I have not yet started unraid to check, but if the report is not right, then there might be somehting else I need to do. Any suggestions?

 

It could well be.    There are at least 4 passes.    According to your report only pass 0 completed.

Looks like reiserfsck is hanging, try with unRAID v6.4rc7 as it includes newer reiser tools, or try running it in a different computer, with the complete array if possible or just the problem disk alone (in the latter case you'll need to re-sync parity in the end).

I could add more memory to the Unraid computer. Do you think that would help?

3 minutes ago, kno said:

I could add more memory to the Unraid computer. Do you think that would help?

 

Yes, you only have 2GB, that's very likely the problem, use 4GB minimum.

Edited September 2, 20178 yr by johnnie.black

Ok, I have another computer with 6GB of RAM with similar motherboard. I will lend those to my Unraid server.

 

So should I just add more RAM, or should I add more RAM and update Unraid?

Edited September 2, 20178 yr by kno

Just add the RAM, I bet that's the problem.

I ran with --rebuild-tree over the weekend. When I came back home the disk was spun down. Did it complete?

 

Copy of report is below:

 

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/md6) tree
Will put log info to 'stdout'
Replaying journal: 
Replaying journal: Done.
Reiserfs journal '/dev/md6' in blocks [18..8211]: 0 transactions replayed
###########
reiserfsck --rebuild-tree started at Sat Sep  2 12:18:27 2017
###########

Pass 0:
Loading on-disk bitmap .. ok, 862357032 blocks marked used
Skipping 52923 blocks (super block, journal, bitmaps) 862304109 blocks will be read
0%....20%....40%....60%....80%....100%
	"r5" hash is selected
Flushing..finished
	Read blocks (but not data blocks) 862304109
		Leaves among those 851507
			- leaves all contents of which could not be saved and deleted 2
		Objectids found 3242

Pass 1 (will try to insert 851505 leaves):
Looking for allocable blocks .. finished
0%....20%....40%....60%....80%....100%
Flushing..finished
	851505 leaves read
		851501 inserted
		4 not inserted

Pass 2:
0%....20%....40%....60%....80%....100%
Flushing..finished
	Leaves inserted item by item 4
Pass 3 (semantic):
Flushing..finished
	Files found: 3100
	Directories found: 141
	Names pointing to nowhere (removed): 1
Pass 3a (looking for lost dir/files):
Looking for lost directories:
Flushing..finished
Pass 4 - finished
	Deleted unreachable items 6687
Flushing..finished
Syncing..finished
###########
reiserfsck finished at Sat Sep  2 22:45:17 2017
###########
####### Pass 0 #######
block 180906004: The number of items (65416) is incorrect, should be (1) - corrected
block 180906004: The free space (270) is incorrect, should be (3279) - corrected
pass0: vpf-10110: block 180906004, item (0): Unknown item type found [67117057 604052743 0xff85005a ??? (15)] - deleted
block 183197996: The number of items (65416) is incorrect, should be (1) - corrected
block 183197996: The free space (268) is incorrect, should be (1489) - corrected
pass0: vpf-10110: block 183197996, item (0): Unknown item type found [167841791 16909312 0x1a014d ??? (5)] - deleted
3240 directory entries were hashed with "r5" hash.
####### Pass 1 #######
####### Pass 2 #######
####### Pass 3 #########
rebuild_semantic_pass: The entry [112 113] ("Edge Of Tomorrow (Norge Warner 5000188798).iso") in directory [69 112] points to nowhere - is removed
vpf-10650: The directory [69 112] has the wrong size in the StatData (112) - corrected to (48)
vpf-10680: The file [106 107] has the wrong block count in the StatData (17056) - corrected to (10376)
####### Pass 3a (lost+found pass) #########

18 minutes ago, kno said:

reiserfsck finished at Sat Sep 2 22:45:17 2017

 

Start the array and it should mount now.

It mounted now, so FS is repaired.

 

I made a file list with DOS command DIR /s before and after the repair. The file list is similar and there are no files in the lost+found folder created during the process.

 

How do I know if files are lost or not? I also made file lists for the other drives. Are they somehow affected?

10 minutes ago, kno said:

How do I know if files are lost or not?

 

If there are no files on lost+found they should all be there

 

10 minutes ago, kno said:

I also made file lists for the other drives. Are they somehow affected?

 

No

Great! It looks like I am soon back to a healthy setup. I think I will add a second parity drive soon as well. I do not feel that the WD Green disks are reliable. Two parity drives will reduce the risks at least.

 

I did have one corrupted file on disk 1. I found it when comparing checksums from the backup and the rebuilt drive. The file was not important.

I do not know if there are corrupted files on disk 5 (the first one I exchanged and rebuilt from parity). There might have been some corruptions there because it was rebuilt from parity and disk 1 also had some errors during the rebuild. I do not think there is a way to check for corruptions on this disk because I was not able to create a checksum file for it and I do not have a backup to compare with either.

 

What do you think? I guess the only way is to check each file manually? (The drive did only contain ISO’s backed up from my Blu-ray disks)

10 minutes ago, kno said:

I guess the only way is to check each file manually? (The drive did only contain ISO’s backed up from my Blu-ray disks)

 

If they are BD backups I think it's not worth the trouble, if some day you're watching a movie and notice a small or large glitch re-rip that one.

Now that I am satisfied with the results do I need to run another pairty check to make sure it is valid?

You don't need to but it's always good to make sure all is well, always run non-correct checks unless sync errors are expect, e.g., after an unclean shutdown.

I think this is solved now! Thanks for all the help!