royalflush5 Posted May 12, 2020 Share Posted May 12, 2020 Hey, I've been having issues with my dockers where they just stop working. I went to update my plex docker and was getting a read only error. I rebooted and had all my containers gone from the list. I can add my containers back with the template section, but despite having the files in the appdata share, I have to start from scratch. Any ideas? Thank you diagnostics-20200512-0948.zip Quote Link to comment
trurl Posted May 12, 2020 Share Posted May 12, 2020 Your cache is corrupt and you should forget about getting dockers going again until you fix that. Post a screenshot of Main - Cache Devices Quote Link to comment
royalflush5 Posted May 12, 2020 Author Share Posted May 12, 2020 (edited) Damn cant believe i missed that. I recently swapped out to a new cache drive too. Started completely fresh a couple weeks ago. Any chance i can get the filesystem working? Edited May 12, 2020 by royalflush5 Quote Link to comment
trurl Posted May 12, 2020 Share Posted May 12, 2020 Do you have a backup of cache? 45 minutes ago, royalflush5 said: despite having the files in the appdata share These may be newly created on the array since cache isn't mounting. Or they will be only partial contents missing anything that was on cache. Do you have a backup of appdata from the CA Backup plugin? Quote Link to comment
royalflush5 Posted May 12, 2020 Author Share Posted May 12, 2020 yeah ive got a backup, you think I should wipe the cache and start over? Quote Link to comment
trurl Posted May 12, 2020 Share Posted May 12, 2020 21 minutes ago, royalflush5 said: yeah ive got a backup, you think I should wipe the cache and start over? That would be simplest. Disable dockers and VMs for now since there may be some additional cleanup needed. Just get appdata restored to cache and post new diagnostics. ***EDIT*** If you had anything else besides appdata backed up from cache, then go ahead and restore it too. But leave dockers,VMs disabled. Quote Link to comment
royalflush5 Posted May 12, 2020 Author Share Posted May 12, 2020 (edited) Alright, docker and vm service are off, formatted cache, here are the new diags: Quote If you had anything else besides appdata backed up from cache, then go ahead and restore it too. But leave dockers,VMs disabled. Nah nothing i care about left. I had a vm but i can reinstall diagnostics-20200512-1121.zip Edited May 12, 2020 by royalflush5 Quote Link to comment
trurl Posted May 12, 2020 Share Posted May 12, 2020 Your appdata, domains, and system shares are all on the array. Did you restore appdata? Not sure how that works since I have never needed to do it. I would have thought it would restore it to cache since appdata is cache-only. Ideally you want those shares all on cache and staying on cache so docker/VM performance will not be affected by the slower array, and so docker/VMs won't keep array disks spinning. Set those shares to cache-prefer, run mover, when it completes post new diagnostics. 1 Quote Link to comment
royalflush5 Posted May 12, 2020 Author Share Posted May 12, 2020 1 hour ago, trurl said: Your appdata, domains, and system shares are all on the array. Did you restore appdata? Not sure how that works since I have never needed to do it. I would have thought it would restore it to cache since appdata is cache-only. Ideally you want those shares all on cache and staying on cache so docker/VM performance will not be affected by the slower array, and so docker/VMs won't keep array disks spinning. Set those shares to cache-prefer, run mover, when it completes post new diagnostics. Nah I haven't restored anything yet. Probably just set that years ago and never thought anything about it. Here is the latest diagnostics-20200512-1432.zip Quote Link to comment
trurl Posted May 12, 2020 Share Posted May 12, 2020 appdata still has some files on the array. Go to Settings - Scheduler - Mover Settings and enable Mover Logging, then run mover again and post new diagnostics so we can see why those aren't getting moved. Quote Link to comment
royalflush5 Posted May 12, 2020 Author Share Posted May 12, 2020 (edited) here you go, looked like it is stuck on the file in radarr's appdata? trying to read it myself Edited May 12, 2020 by royalflush5 Quote Link to comment
trurl Posted May 12, 2020 Share Posted May 12, 2020 Logs indicate it moved and appdata is all on cache now. Not sure why it didn't finish before. You should turn off mover logging now since those aren't anonymized. Quote Link to comment
royalflush5 Posted May 12, 2020 Author Share Posted May 12, 2020 Thanks, going to remove the zip for privacys sake. I'm going to get to restoring everything, anything I should keep an eye out for? Quote Link to comment
trurl Posted May 12, 2020 Share Posted May 12, 2020 2 minutes ago, royalflush5 said: remove the zip for privacys sake That's OK, but there really wasn't anything there. The Diagnostics are still anonymized, but the mover logging part of the syslog isn't. That part only had a few lines in it that didn't seem very important for privacy in this case. Quote Link to comment
trurl Posted May 12, 2020 Share Posted May 12, 2020 7 minutes ago, royalflush5 said: anything I should keep an eye out for? Do you have Notifications setup so Unraid can notify you immediately by email or other agent if a problem is detected? Quote Link to comment
royalflush5 Posted May 12, 2020 Author Share Posted May 12, 2020 5 minutes ago, trurl said: Do you have Notifications setup so Unraid can notify you immediately by email or other agent if a problem is detected? Had it set up with pushbullet a while ago. Going to set it up again as i no longer use it 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.