Invalid folder appdata contained within /mnt

[Freshavakado]

I've been using the plugin Fix Common Problems and it recently came up with the error listed in the title. I'm still very new to UnRaid and I'm not sure what the issue is or how to fix it. Anyone know how to fix this issue and if its a problem or not. Thanks!

[Squid]

Probably either Settings - Docker Settings (default appdata storage location) or one of your apps (on the docker page look at the volume paths) is referencing /mnt/appdata instead of /mnt/user/appdata or /mnt/cache/appdata.

 

Net result is that whichever container is causing this is not saving its appdata and you will lose it on every reboot.  (in addition to the memory that its consuming which may cause other problems)

[Freshavakado]

Okay, I checked my Docker settings and it was setup to /mnt/user/appdata and I changed it to /mnt/cache/appdata then back again to /mnt/user/appdata and for both the error still came up. Anything else I could be missing?

 

 

[itimpi]

Have you checked the settings for each docker container you are running?

[Freshavakado]

I just checked, the only docker container I have at the moment is MineOS and I tried the Host Path both of these ways and neither got rid of the problem (or the issues I'm having with starting the Minecraft Server with MineOS).

[trurl]

Your screenshot is showing you what Squid already told you was a likely problem.

5 hours ago, Squid said:

one of your apps (on the docker page look at the volume paths) is referencing /mnt/appdata

 

[Freshavakado]

I guess my question is if neither of the paths fix the issue, what is the problem then? I may not have explained myself well enough. The first one was what it defaulted to, the second is what I also tried and that didn't work either. Refering to the Host Path that is, which is what I believe I'm supposed to be looking at.

[Squid]

The invalid path is in screenshot #1.  If screenshot #2 is the fixed version, then a reboot to clear out the invalid folder will fix you up.

[Freshavakado]

Thank you both, the reboot fixed it and there is no longer any warning message from Fix Common Problems, just having issue with starting the Minecraft Server on MineOS but that is problem for another discussion thread. Thank you very much for your help.

[Squid]

NB  If you had everything all set up, then that is now lost as the appdata was being stored in RAM and wouldn't have survived anyways.

[Freshavakado]

It did fix that issue and it makes a lot more sense now, all the settings stay after rebooting the docker container now unlike previously. I'm just looking around forums now to see why it won't start after I followed a couple tutorials. It seems to be an issue with accepting the EULA but I cannot find where the eula.txt file is nor have any idea where the server root is. 

[Squid]

You'll be semi-happy to know that the issue wasn't caused by you.  The template itself is incorrect and has that path in it.  I've added a comment to the app.

[Freshavakado]

That's good to know, I didn't even think the problem could've originated there. Thanks again for the help!

[dockerPolice]

Debating what to do with the app itself.  Hasn't been updated in a few years, no idea if the other mine apps are suitable replacements, and it is a rather large error.  There is a PR on @hernandito's GitHub for the template.

[Freshavakado]

An update to the MineOS issues, I was able to start the server running 1.12.2 but anything that is 1.13 or newer won't allow the server to start, I'm going to try to contact @hernandito about this to see if they have any idea as to what the problem may be.