Originally posted in support ich777 - Gamesrver

Seeking your guidance.

I have downloaded Palword from Apps with no modifications.  

Gave it time to download and watched it in the logs -- no issues.

The Docker is up and running.

I have stopped it to change the ini files:

    hoping to change the Server Name, Password, Admin Password -- then planned on logging in.

Well, I went to where the files should be and I am baffled.

/mnt/cache/appdata/palworld

I cannot seem to find this folder.

I do fave the shares set for primary storage to Cache-nvme -- and other apps do appear here get moved appropriately, I think.

Secondary storage is set to Array 

Mover action is set to Array -> Cache-nvme

Yet for the life of me I can not find my Pal

I have removed it and have reinstalled and continue to have the same issue, cant seem to find the folder so I can access the ini file.

Its been a few day so I have been trying to figure this out but not sure how or why it occurred.

I did originally notice this in early version 6 of Unraid — when I was trying to do Dedicated ARK server — same thing shows listed to show in /mnt/cache/appdata/ but when I go to find the files — no ARK; did not purse it then as I was too busy.  SO I believe what ever occurred has been an issue but I do have a few other files that do show up correctly which is why this troubles me.

Appreciate any help you can give.

Do you mean that you want appdata to span both pools? Appdata share should never have mover enabled, unless you are temporarily moving data with Docker disabled.

13 hours ago, Soulkiss said:

Well, I went to where the files should be and I am baffled.

/mnt/cache/appdata/palworld

Have you tried looking under /mnt/user/appdata/palworld ? That is the User Share path and should locate it regardless of what drive it is located on.

The docker container template probably has /mnt/cache/appdata and you didnt change it to /mnt/user/appdata OR appdata is set to write to cache as primary share and not cache-nvme.

You need to check your settings and make sure everything goes to the correct disk/pool/array

It also looks like your postgres17 conatiner is also writing to the /mnt/cache/appdata folder as well which could result in a loss of data IF this location doesn't actually physically exist (meaning you dont have a pool named cache).

Edited July 16Jul 16 by MowMdown

If you don't actually have a pool named cache, /mnt/cache is a path in rootfs, the RAM reserved for the OS. Anything stored there won't persist.

Check the host volume paths for the containers.

On 7/15/2026 at 11:43 PM, JorgeB said:

Do you mean that you want appdata to span both pools? Appdata share should never have mover enabled, unless you are temporarily moving data with Docker disabled.

Not sure what you mean.

Its my understanding that anything in the /mnt/cache gets eventually moved to the /mnt/appdata/

I had followed How to Setup a Palword Server with Unraid Guide [https://www.youtube.com/watch?v=URC_SP1TQ8I&t=17s] by SPX Labs -- and it should show up the the /mnt/appdata/ --> which is what I can not find. It why am asking the question.

On 7/16/2026 at 6:00 AM, itimpi said:

Have you tried looking under /mnt/user/appdata/palworld ? That is the User Share path and should locate it regardless of what drive it is located on.

Its not showing up -- yet the docker says its running but I can not find or access the files.

On 7/16/2026 at 6:03 AM, MowMdown said:

The docker container template probably has /mnt/cache/appdata and you didnt change it to /mnt/user/appdata OR appdata is set to write to cache as primary share and not cache-nvme.

In the share setting it only gives 3 options of the 3 ssds I have on the rig.

I want them on the nvme ssd and it shows up as cache-nvme.

On 7/16/2026 at 6:03 AM, MowMdown said:

You need to check your settings and make sure everything goes to the correct disk/pool/array

It also looks like your postgres17 conatiner is also writing to the /mnt/cache/appdata folder as well which could result in a loss of data IF this location doesn't actually physically exist (meaning you dont have a pool named cache).

Not sure about the disk/pool/array -- but I will look into it.

Postgres 17 -- yes shows up in the /mnt/cache/appdata --but I followed a guide when setting up Immich.

I am new to all this but learning as I go.

On 7/16/2026 at 8:43 AM, trurl said:

If you don't actually have a pool named cache, /mnt/cache is a path in rootfs, the RAM reserved for the OS. Anything stored there won't persist.

Check the host volume paths for the containers.

Ok, I will look into that as well.

I was told to consider erasing all drives and just to reinstall Unraid after; there is not much on the system yet as I am trying to learn.

But I have been puzzled as to why the cache-nvme; no option for just cache

I am able to find the /mnt/cache-nvme -- in terminal but no listing of PalWorld

This is why I am baffled. Should I have placed it in the /mnt/cache-nvme/appdata in the Edit of the Docker instead of what is defaulted: /mnt/cache/appdata

Edited July 18Jul 18 by Soulkiss

If you do not have a pool called ‘cache’ then the location /mnt/cache/appdata is only in RAM, not on a physical device, and its contents will not survive a reboot. If a container has that location in a disk mapping it will not work correctly if you do not have a pool called ‘cache’.

It is better to use the location /mnt/user/appdata as that is the User Shard path that works regardless of which drive the ‘appdata’ share is located on.

4 hours ago, Soulkiss said:

But I have been puzzled as to why the cache-nvme; no option for just cache

You do not have a disk pool named “cache” and your “ServerFiles” is writing to /mnt/cache/appdata which should be /mnt/cache-nvme/appdata

However as Itimpi said you should instead use /mnt/user/… instead of disk names and let Unraid manage it.

8 hours ago, itimpi said:

If you do not have a pool called ‘cache’ then the location /mnt/cache/appdata is only in RAM, not on a physical device, and its contents will not survive a reboot. If a container has that location in a disk mapping it will not work correctly if you do not have a pool called ‘cache’.

It is better to use the location /mnt/user/appdata as that is the User Shard path that works regardless of which drive the ‘appdata’ share is located on.

I understand. Thought I did it as the videos instructed.

I did notice that on the storage of the Shares -- the arrow for the Array points back to the Cache-nvme where the other have the arrow reversed, could this be the issue?

The mover direction is correct. For performance reasons you normally want appdata files to end up on a pool rather than the main array.

The 'system' share should also be like that as you want its contents on a pool for performance reasons. Note that you need to have the docker and VM services disabled if you want mover to move files for the 'system share' as those services keep files open while they are enabled which stops them being moved.

If you run VMs then you may also want the 'domains' share set up like - again for performance reasons although in this case size considerations of the disk image files used by VMs may make it more awkward.

When you have any those shares purely on a pool you may want to remove the Secondary Storage of 'array' option (which then removes the mover option) and then check that Exclusive shares are enabled under Settings->Global Share settings as this enhances performance for accessing files that are only on a pool and set to stay that way.

There is the appdata backup plugin available for periodically moving the contents of those shares to a backup location on the main array.

2 hours ago, itimpi said:

The mover direction is correct. For performance reasons you normally want appdata files to end up on a pool rather than the main array.

The 'system' share should also be like that as you want its contents on a pool for performance reasons. Note that you need to have the docker and VM services disabled if you want mover to move files for the 'system share' as those services keep files open while they are enabled which stops them being moved.

If you run VMs then you may also want the 'domains' share set up like - again for performance reasons although in this case size considerations of the disk image files used by VMs may make it more awkward.

When you have any those shares purely on a pool you may want to remove the Secondary Storage of 'array' option (which then removes the mover option) and then check that Exclusive shares are enabled under Settings->Global Share settings as this enhances performance for accessing files that are only on a pool and set to stay that way.

There is the appdata backup plugin available for periodically moving the contents of those shares to a backup location on the main array.

When you indicate like that --you mean having the arrows pointing to the left?

I do have 2 VMs for gaming -- given I was not able to get the docker ARK SA or Evolved working -- placed them in VM and we launch when ready to play.

Also have VM working on few other games for my husband -- but he really wants Palworld and ARK up in dockers if able.

The Dockers for ARK had same issue not being redirected into the /mnt/appdata.

I was informed that the cache should be moving things into the /mnt/appdata -- but I am not seeing that happen with Palworld. I am hoping once I solve this then I can get ARK up on docker too.

Thank you guys for taking the time to help me out with this issue.

12 minutes ago, Soulkiss said:

When you indicate like that --you mean having the arrows pointing to the left?

I do have 2 VMs for gaming -- given I was not able to get the docker ARK SA or Evolved working -- placed them in VM and we launch when ready to play.

Also have VM working on few other games for my husband -- but he really wants Palworld and ARK up in dockers if able.

The Dockers for ARK had same issue not being redirected into the /mnt/appdata.

I was informed that the cache should be moving things into the /mnt/appdata -- but I am not seeing that happen with Palworld. I am hoping once I solve this then I can get ARK up on docker too.

Thank you guys for taking the time to help me out with this issue.

when you setup a docker container the appdata should be

/mnt/user/appdata/CONTAINER_NAME

Container name is a placeholder in this example. also 9 times out of 10 you don’t have to alter it so I’m not sure how this became an issue.

/mnt/appdata is not correct.

Edited July 19Jul 19 by MowMdown

20 hours ago, MowMdown said:

when you setup a docker container the appdata should be

/mnt/user/appdata/CONTAINER_NAME

Container name is a placeholder in this example. also 9 times out of 10 you don’t have to alter it so I’m not sure how this became an issue.

/mnt/appdata is not correct.

Ohhh, will then blow it up and reattempt knowing this.

Still same issue -- unable to see the /mnt/user/appdata/Palworld despite everything.

Post docker run for Palworld

SOLVED! Apparently in the edit i should have set it to the cache-nvme and not to just the cache.

Now the folder appears and I can manipulate the files need.

Thanks for all the help

5 hours ago, Soulkiss said:

SOLVED! Apparently in the edit i should have set it to the cache-nvme and not to just the cache.

Now the folder appears and I can manipulate the files need.

Thanks for all the help

That's what I posted earlier about, see below:

On 7/18/2026 at 4:33 PM, MowMdown said:

You do not have a disk pool named “cache” and your “ServerFiles” is writing to /mnt/cache/appdata which should be /mnt/cache-nvme/appdata

However with that said, you shouldnt be using disk-pool names and instead be using /mnt/user/appdata/... for your paths to appdata

Edited July 23Jul 23 by MowMdown