Bottom Line: The Path Inside an App Is Not the Same Path You See in ZimaOS Files
MeTube may save to something like /downloads inside its container, while ZimaOS maps that path to a completely different folder on the host. Changing the wrong side of the mapping is why downloaded files seem to disappear.
Read the Volume Mapping as Host Path → Container Path
/media/Storage/Downloads/MeTube -> /downloadsMeTube writes to /downloads. The actual file appears under /media/Storage/Downloads/MeTube on ZimaOS. The current ZimaOS app paths explains exactly this model.
Docker calls the same mechanism Docker bind mounts. Docker's Docker volumes covers the other common storage model.
Find the File by Checking the App Settings First
Open the app settings and inspect every volume row. Identify the container path the app uses for downloads, then follow the host side of that row in ZimaOS Files. Do not search the entire NAS until you have checked the mapping.
Keep Download Data Off the System Drive
For downloaders, media servers and photo apps, map large data to a real storage space rather than the ZimaOS system disk. The ZimaOS data migration helps when an app is already writing to the wrong drive.
Use a Consistent Path Scheme Across Apps
For example, give downloaders and media managers the same parent host path where possible. This reduces path confusion and makes backups easier. The ZimaOS app requirements provides the wider app-storage context.
