Hi there,
I recently had to reinstall my TOS 6 system on my Terramaster F424 Pro due to a corrupted system.
After reinstall, I noticed my Docker containers were not getting the saved preferences loaded from the volume, even though nothing changed in the Docker configs.
I thought it uas a UID or GID issue but nothing had changed. I then moved all the folders out of that share and when I looked at the file map in Terminal (cd, ls, etc) the folders and new config files where still there but not showing in file manager.
Any thoughts?
[Help] Terminal and File Manager/Shared Folder Show Different Contents
Re: [Help] Terminal and File Manager/Shared Folder Show Different Contents
This issue may involve multiple modules. Based on the currently known information, it is still impossible to guess the cause.
You can consider contacting the official website's Live Chat window to schedule a remote troubleshooting session (please attach the forum post to confirm it is you).
Alternatively, you can collect a system report zip file and send it to the support email (Technical Support - Report Issues).
You can consider contacting the official website's Live Chat window to schedule a remote troubleshooting session (please attach the forum post to confirm it is you).
Alternatively, you can collect a system report zip file and send it to the support email (Technical Support - Report Issues).
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: [Help] Terminal and File Manager/Shared Folder Show Different Contents
When you reinstalled the OS, the new system likely created a new internal user ID (UID) and group ID (GID), even if the names appear the same. Although your Docker configs were unchanged, the container processes now run under a different, newly mapped UID/GID, causing them to lose permission to read/write the existing volume data. The ghost files in your terminal are likely the original data still present in the Linux file system (the share), but the file manager might be filtered or caching incorrectly based on the new OS installation.
To fix this, try:
To fix this, try:
- Stop your containers.
Use the chown command via SSH to recursively change the ownership of the volume folders to the user/group that the containers are now running as. This should fix the permission issue.
