August 20, 201510 yr I am having a continuing problem with my docker files. I am only running sickbeard and sabnzb, and every week or couple of weeks they both loose there config files. Meaning if I go to docker tab I can see sickbeard sabnzb and the volume mapping are all correct on the main page, but if I select one of them and choose edit everything is blank. And I end up getting and error page, I have attached a copy of that. I have no idea what is happening and I can not seem to find what is causing this. Any help would be greatly appreciated. Thank you. sickbeard_error.txt
August 20, 201510 yr Community Expert What are your volume mappings? Is the config host path on a cache-only share? If not it probably got moved to the array and you will have to clean it up.
August 20, 201510 yr Author The volume mapping is on appdatata and is set for use cache disk only, it takes at least a week up to 2-3 weeks for this problem to reoccur and the cache disk moves every night so I don't think that is the issue.
August 20, 201510 yr Author Here is the zip file, I have never used this before so hopefully I did it correctly. Thank you for your help, I have allot to learn. server-diagnostics-20150820-1609.zip
August 20, 201510 yr Community Expert Looking at your syslog, mover was indeed skipping appdata every night as it should Aug 5 03:44:09 server logger: .d..t...... Media/ Aug 5 03:44:09 server logger: skipping "appdata" Aug 5 03:44:09 server logger: mover finished ... Aug 19 03:43:34 server logger: .d..t...... Media/ Aug 19 03:43:35 server logger: skipping "appdata" Aug 19 03:43:35 server logger: mover finished but then it looks like your flash got corrupted Aug 20 03:30:00 server kernel: FAT-fs (sda1): Directory bread(block 8192) failed Aug 20 03:30:00 server kernel: FAT-fs (sda1): Directory bread(block 8193) failed Aug 20 03:30:00 server kernel: FAT-fs (sda1): Directory bread(block 8194) failed Aug 20 03:30:00 server kernel: FAT-fs (sda1): Directory bread(block 8195) failed Aug 20 03:30:00 server kernel: FAT-fs (sda1): Directory bread(block 8196) failed Aug 20 03:30:00 server kernel: FAT-fs (sda1): Directory bread(block 8197) failed Aug 20 03:30:00 server kernel: FAT-fs (sda1): Directory bread(block 8198) failed Aug 20 03:30:00 server kernel: FAT-fs (sda1): Directory bread(block 8199) failed Aug 20 03:30:00 server kernel: FAT-fs (sda1): Directory bread(block 8200) failed Aug 20 03:30:00 server kernel: FAT-fs (sda1): Directory bread(block 8201) failed then it must have forgot about your share settings, which are stored on flash, because the next time mover ran Aug 20 03:51:51 server logger: moving "appdata" Aug 20 03:51:51 server logger: ./appdata/sabnzb/admin/future ... Aug 20 03:52:25 server logger: >f+++++++++ appdata/sick beard/config/supervisord.log.1 Aug 20 03:52:25 server logger: mover finished Put your flash in your PC and let it checkdisk. Find appdata on your other disks and either delete it or move it back to cache. And check your share and other settings.
August 20, 201510 yr Author Wow I would not have figured that out. I followed you instructions and have things back up and running. If this keeps happening should I get a new flash drive? Strange that it has done this every couple of weeks. Thanks for taking time to help me out, it is much appreciated.
August 28, 201510 yr Author So it looks like the same thing has happened again. The mover has moved the appdata folder. Also there was a power flicker yesterday and the ups kicked in, not sure if that has something to do with it but I have had problems the backup software not working. Any suggestions as to what I should do to keep this from happening? Or what is the root of this problem? Thanks for any help you can give me. server-diagnostics-20150828-1354.zip
August 28, 201510 yr Author Also I rebooted the server and when it started up it had detected and unclean shutdown, so i am attaching the diagnostics file from that, just trying to give you guys as much information to help me I can. Thank you. server-diagnostics-20150828-1413.zip
August 28, 201510 yr Community Expert unRAID stores the array configuration and its started/stopped status on the flash drive in config/super.dat. If the flash is unwritable, it will not be able to save the fact that you had stopped the array, so the next time it starts it will think you had an unclean shutdown. The current 6.1 release candidate has changed the way mover works so it won't move any share that is on cache unless it is explicitly set to cache-yes, and since the default for shares is cache-no, that might solve the problem of your appdata share getting moved because it forgets what its settings are. However, 6.1 breaks some plugins, and I think it breaks unMenu as well, though there is a possible workaround for unMenu. If you want to try that look in the Announcements. Not sure what to suggest about your flash, though. Try fixing it again, and maybe try it in a different port, then keep checking your logs to see if it is still getting corrupted. You may need to replace it.
August 29, 201510 yr Author Thanks for the help I am going to replace the usb drive and see if this solves the problem. Thanks for taking the time to help me out again.
Archived
This topic is now archived and is closed to further replies.