Einzigstes Posted March 25, 2019 Share Posted March 25, 2019 Hi, I updated to version 6.6.7 a few days ago and I noticed the next day, that my plex-server was not accessable. I had to restart the whole system, as the docker wouldn't restart (Execution Error) All my shares are not displayed either in that case. It works fine for some amount of time, but if every day now, when I come home in the evening without using my server for most of the day I get these problemes. I didn't change anything besides updating the system server1-diagnostics-20190324-1724.zip Quote Link to comment
trurl Posted March 25, 2019 Share Posted March 25, 2019 You didn't notice that your cache isn't mounted? Quote Link to comment
Einzigstes Posted March 25, 2019 Author Share Posted March 25, 2019 28 minutes ago, trurl said: You didn't notice that your cache isn't mounted? oh, i did not somehow It is listed under unmountable disks. I can't explain why this has happened. What can I do now? Is it safe to format? Thanks! Quote Link to comment
trurl Posted March 25, 2019 Share Posted March 25, 2019 48 minutes ago, Einzigstes said: Is it safe to format? Format means it will become empty. Is that what you intend? Let me tag @johnnie.black to see if he has something to add. Quote Link to comment
trurl Posted March 25, 2019 Share Posted March 25, 2019 52 minutes ago, Einzigstes said: It is listed under unmountable disks. Do you mean they are listed under Unassigned Devices, or do you mean they are listed under Cache Devices but are shown there as unmountable? Quote Link to comment
JorgeB Posted March 25, 2019 Share Posted March 25, 2019 15 minutes ago, trurl said: he has something to add. Not really, diags are after whatever happened, cache doesn't have a valid UUID, though if there's any important data OP can still try these before formatting. Quote Link to comment
Einzigstes Posted March 25, 2019 Author Share Posted March 25, 2019 (edited) 1 hour ago, trurl said: Do you mean they are listed under Unassigned Devices, or do you mean they are listed under Cache Devices but are shown there as unmountable? It's only shown here under "Array operations" in Main-Tab. 1 hour ago, johnnie.black said: Not really, diags are after whatever happened, cache doesn't have a valid UUID, though if there's any important data OP can still try these before formatting. All data that is on there, would not be accessible now, as the disk is not mounted, right? I'm not missing any data at all and there schouldn't be anything important on the cache anyways, so i'll just format the drive, re-assign it to the cache and see if that solves my problem. thank you! Edited March 25, 2019 by Einzigstes Quote Link to comment
JorgeB Posted March 25, 2019 Share Posted March 25, 2019 5 minutes ago, Einzigstes said: All data that is on there, would not be accessible now, as the disk is not mounted, right? Correct. Quote Link to comment
trurl Posted March 25, 2019 Share Posted March 25, 2019 5 minutes ago, Einzigstes said: I'm not missing any data at all and there schouldn't be anything important on the cache anyways Are you sure nothing important? Normally people put their docker image and appdata on cache, and that is what your configs say you have. But your diagnostics is also showing system, appdata, and domains shares do not currently exist, presumably because cache isn't mounted. Quote Link to comment
Einzigstes Posted March 25, 2019 Author Share Posted March 25, 2019 Just now, trurl said: Are you sure nothing important? Normally people put their docker image and appdata on cache, and that is what your configs say you have. But your diagnostics is showing system, appdata, and domains shares do not currently exist, presumably because cache isn't mounted. Currently everything is fine, except for the drive, that shows up as unmountable. All my shares are there and dockers are running just fine. It's only after a while, those shares disappear. I have my dockers as well as a vm on the cache, but the files are the only thing, that's really important to me. Those dockers can be set up again. I will add a new diagnostics file from now, when everything is working: server1-diagnostics-20190325-2021.zip Quote Link to comment
trurl Posted March 25, 2019 Share Posted March 25, 2019 Those shares do exist now, but they are on the array. After you get cache going again you will have to stop docker and vm services so you can move them to cache. Might be just as easy to delete and recreate the stuff on the system share and only move the appdata. Quote Link to comment
Einzigstes Posted March 26, 2019 Author Share Posted March 26, 2019 20 hours ago, trurl said: Those shares do exist now, but they are on the array. After you get cache going again you will have to stop docker and vm services so you can move them to cache. Might be just as easy to delete and recreate the stuff on the system share and only move the appdata. So, cache is working again. Server was running all day and shares were still there when I came home. Dockers were running but Plex didn't work. No media files would play and after a restart, It won't run. Is there a simple way to reset all the dockers etc so that I can reinstall them? Is it enough to just remove them & delete the image? All shares related to the docker are set cache only, so a reinstallation will automatically put the docker on the cache, right? (I will also change the path to /mnt/cache/appdata/plex/ etc.) Or can I just format my cache entirely? I don't really know what to do but I'd rather do everything new now instead of messing up somewhere and having problems again later. Thank you!! Quote Link to comment
trurl Posted March 26, 2019 Share Posted March 26, 2019 Do you want to keep your appdata? Quote Link to comment
Einzigstes Posted March 26, 2019 Author Share Posted March 26, 2019 1 minute ago, trurl said: Do you want to keep your appdata? I don't need it. I'll make backups of plex and tautulli etc.. So everything can get deleted Quote Link to comment
trurl Posted March 26, 2019 Share Posted March 26, 2019 OK. As mentioned your last diagnostics had system share on the array. Probably if you delete docker and libvirt images (Settings - Docker and Settings - VM Manager) it will be gone and then would get recreated on cache. You can easily check which disks are used by each share using the Compute feature on the User Shares page. Quote Link to comment
Einzigstes Posted March 27, 2019 Author Share Posted March 27, 2019 On 3/26/2019 at 7:24 PM, trurl said: OK. As mentioned your last diagnostics had system share on the array. Probably if you delete docker and libvirt images (Settings - Docker and Settings - VM Manager) it will be gone and then would get recreated on cache. You can easily check which disks are used by each share using the Compute feature on the User Shares page. Ok, so I did that and re-installed some of my dockers wich seem to work fine. Thank you! When I tried to setup my windows vm however I got a creation error: I have tried to mess with the settings, used different ISO's etc. but always the same error! server1-diagnostics-20190327-2119.zip Quote Link to comment
trurl Posted March 27, 2019 Share Posted March 27, 2019 Your cache is completely full. You need to get all shares except domains, appdata, and system off your cache drive. Go to Settings - Docker and disable docker and delete the image Go to Settings - VM Manager and disable VM and delete the image Go to each User Share and set it to Use cache disk: Yes Go to Main - Array Operations and click Move Now Check to make sure no shares are using cache by going to Main - Cache Devices and clicking on the folder icon at the far right. After you complete this then we can discuss the next steps. Quote Link to comment
Einzigstes Posted March 28, 2019 Author Share Posted March 28, 2019 22 hours ago, trurl said: Your cache is completely full. You need to get all shares except domains, appdata, and system off your cache drive. Go to Settings - Docker and disable docker and delete the image Go to Settings - VM Manager and disable VM and delete the image Go to each User Share and set it to Use cache disk: Yes Go to Main - Array Operations and click Move Now Check to make sure no shares are using cache by going to Main - Cache Devices and clicking on the folder icon at the far right. After you complete this then we can discuss the next steps. Ok, my cache drive is empty now! Is there anything else I should do, before I install my dockers & vm's? Quote Link to comment
Einzigstes Posted March 28, 2019 Author Share Posted March 28, 2019 1 minute ago, trurl said: Post new diagnostics server1-diagnostics-20190328-2208.zip Quote Link to comment
trurl Posted March 28, 2019 Share Posted March 28, 2019 Looks good. Set appdata, domains, and system shares to Use cache disk: Prefer Run mover again. Wait for it to complete Go to the User Shares and Compute for appdata, domains, and system shares to make sure all of their data is on cache Post a new diagnostic when finished with these. Quote Link to comment
trurl Posted March 28, 2019 Share Posted March 28, 2019 3 minutes ago, trurl said: Looks good. Looked at them again and it looks like you have VMs enabled. You were supposed to disable and delete the libvirt image. Quote Link to comment
Einzigstes Posted March 28, 2019 Author Share Posted March 28, 2019 3 minutes ago, trurl said: Looked at them again and it looks like you have VMs enabled. You were supposed to disable and delete the libvirt image. Vm's are currently disabled in my webinterface: Quote Link to comment
Einzigstes Posted March 28, 2019 Author Share Posted March 28, 2019 Just now, Einzigstes said: Vm's are currently disabled in my webinterface: I followed your steps exactly and i'm sure that I disabled the vm's Quote Link to comment
trurl Posted March 28, 2019 Share Posted March 28, 2019 OK let's just go with it for now. It was libvirt that was corrupt before so you may end up having to delete and recreate it. Go ahead with the moving those shares back to cache. 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.