February 23, 201511 yr So I created my unraid box about a year ago. I have a 240GB SSD for my cache, and 3TB drive for my parity, Disk 1, and Disk 2. I recently added a new 3TB drive. The first one was DOA. Here is how the rest of the addition has gone for me: -Got new disk -Preclear -Add to the array -Worked for a couple of weeks. -Showed up faulty one day. --All my shares didn't show up --I could see Disk3 (so I assumed parity was okay) -Order replacement disk (this is where it gets weird) -Preclear --New disk showed up in "preclear_disk.sh -l", but when I tried to preclear the disk it would tell me that it failed to respond to an "fdisk -l". --Power cycled --Changed SATA cables --Changed SATA ports -Finally got it to preclear, but it took longer than expected (over 40 hours) -Added to the array, but it showed up faulty. -I replaced the drive again -New disk had the same problems preclearing as above on my fifth SATA port every time, but it precleared just fine on the sixth SATA port. -Had the blue ball when I added it as Disk 3 -Got my hopes up. -Started array and the disk showed up faulty. I was going to throw a tantrum and punch my machine, but figured I should come beg for help first. My suspicion is that I have a bad MOB, but I want to be sure before I replace yet another thing. I'm not all that experienced when it comes to troubleshooting unraid, because from a system perspective, everything has just worked up until now. I've attached my syslog. Thanks in advance for any help! tower_syslog.zip tower_syslog.zip
February 23, 201511 yr Author Also This: ########### reiserfsck --check started at Mon Feb 23 12:40:02 2015 ########### Replaying journal: Done. Reiserfs journal '/dev/md3' in blocks [18..8211]: 0 transactions repl Checking internal tree.. \/ 14 (of 143-/ 12 (of 85-block 2026912: Th items ( is incorrect, should be (2) the problem in the internal node occured (2026912), w/ 20 (of 143-/ bad_path: block 346854782, pointer 9: The used space (2368) of the ch 346854785) is not equal to the (blocksize (4096) - free space (1896) ze (24)) / 63 (of 143// 80 (of 170/7 bad_path: block 541340573, pointer 53: The used space (4020) of the child block (54 block 104562689: The number of items (63) is incorrect, should be (38) the problem in the internal node occured (104562689), whole subtree is skipped bad_path: block 720686200, pointer 23: The used space (4072) of the child block (72 99: The level of the node (0) is not correct, (2) expected the problem in the internal node occured (287075799), whole subtree is skipped Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 3 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Mon Feb 23 12:45:46 2015 ###########
February 23, 201511 yr Author And here is the report from my --rebuild-tree. I didn't know what was relevant so I left it all in. root@Tower:~# cd root@Tower:~# samba stop root@Tower:~# umount /dev/md3 umount: /dev/md3: not mounted root@Tower:~# reiserfsck --check /dev/md3 reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/md3 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you ########### reiserfsck --check started at Mon Feb 23 12:40:02 2015 ########### Replaying journal: Done. Reiserfs journal '/dev/md3' in blocks [18..8211]: 0 transactions repl Checking internal tree.. \/ 14 (of 143-/ 12 (of 85-block 2026912: Th items ( is incorrect, should be (2) the problem in the internal node occured (2026912), w/ 20 (of 143-/ bad_path: block 346854782, pointer 9: The used space (2368) of the ch 346854785) is not equal to the (blocksize (4096) - free space (1896) ze (24)) / 63 (of 143// 80 (of 170/7 bad_path: block 541340573, pointer 53: The used space (4020) of the child block (54 block 104562689: The number of items (63) is incorrect, should be (38) the problem in the internal node occured (104562689), whole subtree is skipped bad_path: block 720686200, pointer 23: The used space (4072) of the child block (72 99: The level of the node (0) is not correct, (2) expected the problem in the internal node occured (287075799), whole subtree is skipped Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 3 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Mon Feb 23 12:45:46 2015 ########### root@Tower:~# root@Tower:~# root@Tower:~# root@Tower:~# root@Tower:~# reiserfsck --rebuild-tree /dev/md3 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/md3) tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Replaying journal: Done. Reiserfs journal '/dev/md3' in blocks [18..8211]: 0 transactions replayed ########### reiserfsck --rebuild-tree started at Mon Feb 23 12:56:30 2015 ########### Pass 0: ####### Pass 0 ####### Loading on-disk bitmap .. ok, 23602764 blocks marked used Skipping 30567 blocks (super block, journal, bitmaps) 23572197 blocks will be read 0%..block 2026912: The number of items ( is incorrect, should be (2) - corrected block 2026912: The free space (884) is incorrect, should be (2784) - corrected ..20%.block 104562689: The number of items (63) is incorrect, should be (38) - corrected block 104562689: The free space (244) is incorrect, should be (1004) - corrected pass0: block 104562689, item 37 (lower): Item [171 1063 0x0 SD (0)] is out of order - deleted ...40%....60%....80%....100% left 0, 35287 /sec 1073 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 23572197 Leaves among those 23357 - corrected leaves 1 - leaves all contents of which could not be saved and deleted 1 Objectids found 1104 Pass 1 (will try to insert 23356 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....100% left 0, 51 /sec Flushing..finished 23356 leaves read 23344 inserted 12 not inserted non-unique pointers in indirect items (zeroed) 2 ####### Pass 2 ####### Pass 2: 0%....20%....40%....60%....80%..vpf-10260: The file we are inserting the new item (4 10 0x1 IND (1), len 2548, location 1548 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped ..100% left 0, 0 /sec Flushing..finished Leaves inserted item by item 12 Pass 3 (semantic): ####### Pass 3 ######### /TVvpf-10680: The directory [2 171] has the wrong block count in the StatData (2) - corrected to (1) vpf-10650: The directory [2 171] has the wrong size in the StatData (936) - corrected to (48) /Mo/Moviesrebuild_semantic_pass: The entry [4 9] ("Minuscule The Valley Of The Lost Ants 2013 Nordic 720p BluRay x264-DAWGS") in directory [2 4] points to nowhere - is removed ... 080p.BluRay.x264-SPARKS/big.hero.6.2014.1080p.bluray.x264-sparks.sample.mkvvpf-10680: The file [1046 1047] has the wrong block count in the StatData (101288) - corrected to (96088) /Movies/Big.Hero.6.2014.1080p.BluRay.x264-SPARKSrebuild_semantic_pass: The entry [1046 1048] ("big.hero.6.2014.1080p.bluray.x264-sparks.subs.sfv") in directory [4 1046] points to nowhere - is removed /Movies/Big.Hero.6.2014.1080p.BluRay.x264-SPARKSrebuild_semantic_pass: The entry [1046 1049] ("Big.Hero.6.2014.1080p.BluRay.x264-SPARKS.idx") in directory [4 1046] points to nowhere - is removed /Movies/Big.Hero.6.2014.1080p.BluRay.x264-SPARKSrebuild_semantic_pass: The entry [1046 1050] ("Big.Hero.6.2014.1080p.BluRay.x264-SPARKS.mkv") in directory [4 1046] points to nowhere - is removed vpf-10650: The directory [4 1046] has the wrong size in the StatData (320) - corrected /Moviesvpf-10650: The directory [2 4] has the wrong size in the StatData (832) - corrected to (744) rebuild_semantic_pass: The entry [2 260] ("Audiobooks") in directory [1 2] points to nowhere - is removed vpf-10650: The directory [1 2] has the wrong size in the StatData (192) - corrected to (160) Flushing..finished Files found: 152 Directories found: 16 Names pointing to nowhere (removed): 5 Pass 3a (looking for lost dir/files): ####### Pass 3a (lost+found pass) ######### Looking for lost directories: /171_172get_next_directory_item: The entry ".." of the directory [171 172] pointes to [2 171], instead of [2 1105] - corrected /171_186get_next_directory_item: The entry ".." of the directory [171 186] pointes to [2 171], instead of [2 1105] - corrected vpf-10650: The directory [171 186] has the wrong size in the StatData (48) - corrected to (72) /171_192get_next_directory_item: The entry ".." of the directory [171 192] pointes to [2 171], instead of [2 1105] - corrected /171_199get_next_directory_item: The entry ".." of the directory [171 199] pointes to [2 171], instead of [2 1105] - corrected /171_205get_next_directory_item: The entry ".." of the directory [171 205] pointes to [2 171], instead of [2 1105] - corrected /171_211get_next_directory_item: The entry ".." of the directory [171 211] pointes to [2 171], instead of [2 1105] - corrected /171_217get_next_directory_item: The entry ".." of the directory [171 217] pointes to [2 171], instead of [2 1105] - corrected /171_224get_next_directory_item: The entry ".." of the directory [171 224] pointes to [2 171], instead of [2 1105] - corrected /171_231get_next_directory_item: The entry ".." of the directory [171 231] pointes to [2 171], instead of [2 1105] - corrected /171_239get_next_directory_item: The entry ".." of the directory [171 239] pointes to [2 171], instead of [2 1105] - corrected /171_253get_next_directory_item: The entry ".." of the directory [171 253] pointes to [2 171], instead of [2 1105] - corrected /171_989get_next_directory_item: The entry ".." of the directory [171 989] pointes to [2 171], instead of [2 1105] - corrected /171_996get_next_directory_item: The entry ".." of the directory [171 996] pointes to [2 171], instead of [2 1105] - corrected /171_1003get_next_directory_item: The entry ".." of the directory [171 1003] pointes to [2 171], instead of [2 1105] - corrected /171_1010get_next_directory_item: The entry ".." of the directory [171 1010] pointes to [2 171], instead of [2 1105] - corrected /171_1017get_next_directory_item: The entry ".." of the directory [171 1017] pointes to [2 171], instead of [2 1105] - corrected /171_1025get_next_directory_item: The entry ".." of the directory [171 1025] pointes to [2 171], instead of [2 1105] - corrected /171_1032get_next_directory_item: The entry ".." of the directory [171 1032] pointes to [2 171], instead of [2 1105] - corrected /171_1040get_next_directory_item: The entry ".." of the directory [171 1040] pointes to [2 171], instead of [2 1105] - corrected /179_180get_next_directory_item: The entry ".." of the directory [179 180] pointes to [171 179], instead of [2 1105] - corrected rebuild_semantic_pass: The entry [180 1080] ("The Blacklist - S02E10 - 720p HDTV X264-DIMENSION nzb.mkv") in directory [179 180] points to nowhere - is removed /The Blacklist - S02E09 - 720p HDTV X264-DIMENSION nzb.sfvvpf-10680: The file [180 184] has the wrong block count inrebuild_semantic_pass: The entry [180 185] ("The Blacklist - S02E09 - 720p HDTV X264-DIMENSION nzb.srr") in directory [179 180] points to nowhere - is removed vpf-10650: The directory [179 180] has the wrong size in the StatData (816) - corrected to (656) /260_261get_next_directory_item: The entry ".." of the directory [260 261] pointes to [2 260], instead of [2 1105] - corrected /260_295get_next_directory_item: The entry ".." of the directory [260 295] pointes to [2 260], instead of [2 1105] - corrected /260_628get_next_directory_item: The entry ".." of the directory [260 628] pointes to [2 260], instead of [2 1105] - corrected /260_720get_next_directory_item: The entry ".." of the directory [260 720] pointes to [2 260], instead of [2 1105] - corrected /260_859get_next_directory_item: The entry ".." of the directory [260 859] pointes to [2 260], instead of [2 1105] - corrected /1054_1055get_next_directory_item: The entry ".." of the directory [1054 1055] pointes to [171 1054], instead of [2 1105] - corrected /1060_1061get_next_directory_item: The entry ".." of the directory [1060 1061] pointes to [171 1060], instead of [2 1105] - corrected /1067_1068get_next_directory_item: The entry ".." of the directory [1067 1068] pointes to [171 1067], instead of [2 1105] - corrected /1074_1075get_next_directory_item: The entry ".." of the directory [1074 1075] pointes to [171 1074], instead of [2 1105] - corrected /1085_1086get_next_directory_item: The entry ".." of the directory [1085 1086] pointes to [171 1085], instead of [2 1105] - corrected /1092_1093get_next_directory_item: The entry ".." of the directory [1092 1093] pointes to [171 1092], instead of [2 1105] - corrected /1099_1100get_next_directory_item: The entry ".." of the directory [1099 1100] pointes to [171 1099], instead of [2 1105] - corrected Looking for lost files:9 /sec Flushing..finishede 0, 0 /sec Objects without names 38 Dirs linked to /lost+found: 32 Dirs without stat data found 1 Files linked to /lost+found 6 Pass 4 - finished done 1, 0 /sec Deleted unreachable items 2432 Flushing..finished Syncing..finished ########### reiserfsck finished at Mon Feb 23 13:22:26 2015 ###########
February 23, 201511 yr Author Sigh... and now this. I'm at the end of what I can think to do. Disk 1 has never run hot before btw. I need help please!
Archived
This topic is now archived and is closed to further replies.