Best Practices for setup

Hello all… Been playing around with this OS to test what it can and cant do properly…

My current setup… Unraid which hosts all the data and in an attempt to offload some of processes I started with this OS to host Emby, Plex, and OpenWebUI.

Everything seemed to be fine till yesterday when both plex and Emby lost access to all of the data on unraid… confused, I restarted the server and on restart the share vanished from Zima…

Not ideal… I readded the share and things are starting to rebuild…

So… how do I prevent the share from vanishing after 7? days… and how do I make the share survive a reboot…

anything short of making those two things work like a fine oiled machine, I can not accept this OS as a ‘server’

A server that requires human intervention everytime the power goes out is not a good one

In order for this to work correctly, I believe you’re going to have to mount your DATA drive, using a unique UUID. Then point to that drive for your actual data/configs.

By mounting using a UUID, when you reboot, it will always read that mount, and load every time.

That’s where I would start, sorry I am heading out the door, but thought I’d try to give a quick answer/suggestion.

I am experiencing the same issue after reboot. My network storage access to my NAS is lost to my “apps.”
Only disconnecting and reconnecting in the files app then restarting the apps restores the connection.
LAN or Network storage isnt able to be mounted in the storage settings in ZimaOS and doesnt even show there when connected via the files app.
There needs to be a way to actually mount the LAN storage inside the storage settings of the OS that would allow to mount via UUID. As of now the files app connects through ip address and doesnt actually mount the network storage.

Is this something that resonates with many here? I have the feeling this distro is young but given the lack of text, this would be a make or break feature for me at least.

I think this would allow this distro to reach a wider market if this was implementated. Not everyone is wanting to abandon thier current hardware to run this OS(such as my case), given that there are many that have a NAS already, this could be a gateway for them into knowing the OS and adopting it once they are comfortable with it.

Any Dev care to provide input or thoughts?

If im not mistaken, for a UUID to be used, that would be referencing iSCSI via fiber if my years in IT are not mistaking me. For my use case, UNRaid doesnt provide that feature. I have the hareware that could support it but not the OS. I have some good hardware but not the $$$ for the software

is this an unreasonable request?

Hi, mount adding line in /etc/fstab. For me has been super stable both for mounting SMB shares &/or binds. If not familiar just check with ChatGPT. If you also want convenient GUI acces via Files App just “Star” as needed & you’ll have your Shortcut icon pinned on the sidebar.

And this will persist longer then 7 days and survive a restart?

I have to cast boubt on your comment… GUI access isnt valid given the 7 day limitation… thus requiring manual intervention after 7 days or a reboot… thus breaking the dockers…

try again?