This is my first post here. I’ve just installed ZimaOS and I’m planning to migrate from my Synology setup. It was a pleasant surprise to find that I can install custom VMs – the first thing I did was set up a Debian VM with Synology DSM on top .
I have a few questions that I haven’t been able to find answers to yet. Managing Shares (Media, Photos, etc.): I haven’t found a good way in the GUI to move what I believe are the system’s predefined shares (like Media, Photos, etc.) to different locations.
The GUI seems to allow moving them all together to a single new storage location, but I’d like to spread these shares across different physical disks. Is it possible to move them manually despite any warning texts? Or would using symlinks from their original locations to new disk paths be a viable/recommended approach? What’s the best practice here?
The system seems to use some kind of A/B partitioning. Running sudo rauc status shows boot status: bad for the kernel slots. Is this a cause for concern?
Quite a few Docker containers from the app store either crash or don’t function correctly (e.g., Joplin, AnythingLLM etc). Is this a common experience, or could there be an issue with my specific setup? I plan to try installing these apps manually later to see if I can get them working, but I certainly appreciate the convenience of one-click apps when they function smoothly.
Overall, ZimaOS seems like a very promising OS! Thanks to the developers for their great work.
To store files on different partitions, we currently include JBOD and multiple RAID options. Is this what you want?
The A/B partition approach is to allow users to easily switch to the previous version of ZimaOS if they face issues with the newer one.
The Docker system does provide convenience for developers. But this convenience may bring some barriers on the user side. I believe that developers should be surprised to see the configuration panel of our application because it simplifies the configuration. But it may be a bit confusing for (a few)normal users. For some of the applications, users might need to enter the configuration panel, modify some configurations, and even find the running/auth parameters in the CLI interface of the app. Here is an example:
Of course, many apps support one-click installation and usage.
If the application requires manual configuration and finding info in the log, most people will be confused. Fortunately, annotations will be made in the Tips section of such applications.
I believe you have noticed that the App data migration function moves userdata to the disk you want, and the photo app will read the photos from there.
However, you mentioned that you want to spread these shares across different physical disks. This may be a challenge. There is no official photo album program for ZimaOS. I personally recommend immich. The external photo album function of immich can achieve this goal, but you need to allow immich to read all disk locations in the volume settings of immich.
Thanks!
I was thinking of using symlinks to putting Gallery on an SSD and Media/Download etc on a different larger HDD while keeping the system thinking they’re in the original spot. Do you know if those symlinks will stick around after a system update and is there any chance I mess things up with a setup like this?
Or is another better way of moving the folder, I’m sure what the warning is but my guess is that just moving it will be bad somhow? “The current folder is being used by pin, Continuing the migration may have an impact on it.”
.
