July 23, 20169 yr I've been running Unraid 6.1.9 for a few months now with zero issues. I have had docker running as well, with binhex-sabnzbd, crashplan, and PlexMediaServer. Today I tried to install a fan under my SSD cache drive since it tends to be a bit warm. The fan is powered by branching into the cable that powers the SSD and it splits off. Since I installed this fan, none of my docker apps work. I'm wondering if that is because I accidentally turned my server on without the cache SSD drive power cable in so it booted without seeing the cache drive. When I go to my docker tab Plex and Sabnzbd are not running and I can not start them. It says crashplan is running but if I enter the GUI it appears all config info is gone. If someone could please help me out. I can of course supply any more information that is needed. I have included a screen capture of of all the error messages I am getting. Thanks. this is the hardware: https://pcpartpicker.com/user/happymaan/saved/#view=dN89TW
July 23, 20169 yr First try starting array in maintenance mode and running. looks like you have btrfs corruption maybe due to unclean shutdown. btrfs check --repair /dev/sdf1 If prob still exists you may have a corrupt docker image on your btrfs cache drive. You will need to delete the docker image and recreate it. Dont worry you can easily get dockers back. 1 goto settings/docker put on advanced 2. click disable docker 3 click delete docker image 4. setup new docker image 5 start docker 6 goto docker tab 7 At bottom of page click add container (Assuming you installed dockers using community apps plugin your templates will be there) 8 select the templates you had installed before. And install missing dockers. Template will remember your paths etc and your appdata should still be okay. ......for future ref its a good idea to backup appdata now and then with squids excellent community apps plugin hopefully this should be okay .....edit...... If you only have one cache drive, not a cache pool i would use xfs format on the cache rather than btrfs. Obviously you would have to backup your appdata if on cache and any other cache shares. Run mover aswell before to clear cache. Then resetup cache as xfs then recreate cache shares and restore backup into them
July 23, 20169 yr Author That fixed it, thanks! It's because of people like you on this forum I so comfortably choose to use unraid.
July 23, 20169 yr That fixed it, thanks! It's because of people like you on this forum I so comfortably choose to use unraid. great glad you fixed it
July 23, 20169 yr Author I was good for a little while, but now I have this coming up...and docker is not working again:
July 23, 20169 yr The cache drive is formatted with ReiserFS and the system has detected corruption on it so it is now mounted read-only to prevent any further corruption https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
July 23, 20169 yr The cache drive is formatted with ReiserFS and the system has detected corruption on it so it is now mounted read-only to prevent any further corruption https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Squid, in the photos he first posted all errors are btrfs but now in the lastest image posted he is getting ReiserFS errors. Im confused?
July 23, 20169 yr The cache drive is formatted with ReiserFS and the system has detected corruption on it so it is now mounted read-only to prevent any further corruption https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Squid, in the photos he first posted all errors are btrfs but now in the lastest image posted he is getting ReiserFS errors. Im confused? I've relooked at the pictures, and I don't see where you got sdf1 from to run a btrfs check against. The pic shows btrfs corruption on loop0 which is the docker.img file.
July 23, 20169 yr The cache drive is formatted with ReiserFS and the system has detected corruption on it so it is now mounted read-only to prevent any further corruption https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Squid, in the photos he first posted all errors are btrfs but now in the lastest image posted he is getting ReiserFS errors. Im confused? I've relooked at the pictures, and I don't see where you got sdf1 from to run a btrfs check against. The pic shows btrfs corruption on loop0 which is the docker.img file. Ah okay I see. Yes i forgot to say in my post for him to edit the device id to his cache dev id as i couldnt see it in the image posted (as i cut and pasted command). I didnt realise that the loop0 was the image file, i just assumed his cache drive was using btrfs so my confusion was now seeing the ReiserFS. thanks for clearing that up for me
July 23, 20169 yr Author I booted into maintenance mode and run the test on my cache drive, which is indeed ReiserFS I ran the test and received this: reiserfsck 3.6.24 Will read-only check consistency of the filesystem on /dev/sdb1 Will put log info to 'stdout' ########### reiserfsck --check started at Sat Jul 23 10:48:01 2016 ########### Filesystem seems mounted read-only. Skipping journal replay. Checking internal tree.. finished Comparing bitmaps..Fatal corruptions were found, Semantic pass skipped 1 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Sat Jul 23 10:48:13 2016 ########### bad_path: block 32604411, pointer 81: The used space (3560) of the child block (32604276) is not equal to the (blocksize (4096) - free space (480) - header size (24)) bad_stat_data: The objectid (1484478) is marked free, but used by an object [807511 1484478 0x0 SD (0)] bad_stat_data: The objectid (1484476) is marked free, but used by an object [810633 1484476 0x0 SD (0)] bad_path: block 113836052, pointer 67: The used space (4012) of the child block (28803087) is not equal to the (blocksize (4096) - free space (128) - header size (24)) bad_path: The left delimiting key [810639 880481 0x1 DIR (3)] of the node (74547205) must be equal to the first element's key [810639 880481 0x0 SD (0)] within the node. bad_stat_data: The objectid (1484472) is marked free, but used by an object [826043 1484472 0x0 SD (0)] bad_stat_data: The objectid (1484482) is marked free, but used by an object [829211 1484482 0x0 SD (0)] bad_path: block 75923653, pointer 102: The used space (764) of the child block (12779522) is not equal to the (blocksize (4096) - free space (3196) - header size (24)) vpf-10640: The on-disk and the correct bitmaps differs. After that I ran the check again with the "--rebuild-tree" command and this was the output: 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/sdb1) tree Will put log info to 'stdout' Filesystem seems mounted read-only. Skipping journal replay. ########### reiserfsck --rebuild-tree started at Sat Jul 23 11:13:11 2016 ########### Pass 0: Loading on-disk bitmap .. ok, 8325684 blocks marked used Skipping 11937 blocks (super block, journal, bitmaps) 8313747 blocks will be read 0%....20%....40%....60%....80%....100% "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 8313747 Leaves among those 60281 Objectids found 550144 Pass 1 (will try to insert 60281 leaves): Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....100% Flushing..finished 60281 leaves read 59092 inserted - pointers in indirect items pointing to metadata 1 (zeroed) 1189 not inserted non-unique pointers in indirect items (zeroed) 206 Pass 2: 0%....20%....40%....60%....80%....100% Flushing..finished Leaves inserted item by item 1189 Pass 3 (semantic): Flushing..finished Files found: 220735 Directories found: 276901 Symlinks found: 52506 Pass 3a (looking for lost dir/files): Looking for lost directories: Looking for lost files: Flushing..finished Objects without names 2 Files linked to /lost+found 2 Pass 4 - finished Deleted unreachable items 1 Flushing..finished The partition is mounted ro. It is better to umount and mount it again. Syncing..finished ########### reiserfsck finished at Sat Jul 23 11:14:49 2016 ########### ####### Pass 0 ####### 550140 directory entries were hashed with "r5" hash. ####### Pass 1 ####### ####### Pass 2 ####### ####### Pass 3 ######### vpf-10680: The file [1484270 1484461] has the wrong block count in the StatData (7104) - corrected to (5448) ####### Pass 3a (lost+found pass) ######### vpf-10670: The file [2 666270] has the wrong size in the StatData (0) - corrected to (994242560) vpf-10680: The file [2 666270] has the wrong block count in the StatData (411344) - corrected to (409512) ____________ Currently my cache drive is still being listed as "unmountable" If SSH in I can still see the contents of the cache drive. When I check the drive status while the array is up I get "Unmountable - No file system (32)" Any ideas? Thanks again for your help.
Archived
This topic is now archived and is closed to further replies.