The source setup used ZimaOS as an application server while keeping all media on an existing Unraid NAS. Plex, Emby, and OpenWebUI ran on ZimaOS and initially accessed the remote data successfully. After about a week—and again after reboot—the network share disappeared from the application environment. Reconnecting it in Files and restarting the apps restored access.
This exposes a design boundary that matters for “compute node + separate NAS” deployments: a network location visible in the Files app is not automatically the same thing as a durable host mount that every Docker container can depend on through reboot and reconnect events.
The Apps Lost Their Media Because the Remote Share Vanished
Plex and Emby were not reported to have database failures. They simply lost the paths pointing at data on Unraid. When the user re-added the share, the applications began rebuilding or rescanning.
That points toward storage reachability, not a corrupted Plex or Emby installation.
Files Access and Docker Volume Access Are Different Layers
ZimaOS Files can connect to LAN Storage over SMB. That connection lets a user browse and move files from the web interface.
A Docker application needs a host path that remains available when the container starts. If the underlying network mount disappears or is re-created under a different lifecycle, the app can see an empty or missing path even though Files can reconnect later.
UUID Advice Does Not Apply to a Normal SMB Share
One reply suggested mounting “using a UUID.” Another participant correctly pointed out that the remote Unraid share was connected by IP/SMB rather than being a local block device.
UUIDs are useful for identifying local filesystems and block devices. An SMB share is identified through a network server/share path, credentials, and mount configuration.
A Community Reply Suggested /etc/fstab
Another participant said a persistent SMB mount in /etc/fstab had been stable for them. That is conventional Linux administration and can work, but it was community advice and the original poster did not confirm a final working configuration.
On an appliance-style OS, manual host mount configuration also means you own boot ordering, credentials, reconnect behavior, and compatibility across updates.
Current ZimaOS Still Supports LAN Storage in Files
Current IceWhale documentation shows adding LAN Storage from the Files sidebar by entering the remote NAS IP address and credentials. This is the supported way to browse or migrate data from another NAS.
Use the current LAN Storage connection workflow when the goal is file access or migration.
The Thread Did Not Establish a Supported Persistent App-Mount Method
No IceWhale developer replied with a documented “mount this SMB share permanently for Docker apps” procedure, and the original poster remained skeptical that the Files connection would survive the observed lifecycle.
A durable article must preserve that unresolved status rather than promoting the community fstab suggestion as the official solution.
For a Media Server, Decide Where the Stable Mount Boundary Lives
If Plex and Emby must automatically recover after power loss, the remote media path must be mounted before the containers start and remain stable throughout reconnects. That can be achieved in several Linux architectures, but the exact choice should be tested on the current ZimaOS release.
For high-value always-on setups, verify cold reboot, remote-NAS reboot, switch reboot, and temporary network loss before considering the storage path production-ready.
Prevent Unnecessary Media Rescans
When a media share disappears temporarily, Plex or Emby may interpret that as content removal depending on library settings. Avoid automatic destructive library cleanup until the remote-mount behavior is proven stable.
Remote NAS App-Mount FAQ
Did reconnecting the share in Files restore the apps?
Users reported that reconnecting the share and restarting the apps restored access.
Can an SMB share be mounted by filesystem UUID?
Not in the same sense as a local disk. SMB uses a network share path and credentials.
Did IceWhale publish a confirmed persistent Docker-app mount fix in this thread?
No. The public thread ended without one.
