Since the release of ZimaOS v1.2.0, we’ve been listening closely to your feedback and incorporating your valuable suggestions into this update.
New Features Highlights
Redesigned Settings Panel: The interface is now simple and intuitive, displaying detailed information about the health of each disk, including boot time, temperature, brand information, and overall health status. Easily monitor your storage devices and ensure smooth system operation!
ZVM One-Click Installation: ZVM now supports the one-click installation of both Windows and Linux—virtualization made easy! This feature was inspired by community feedback from @goitr, a freelance developer who wanted a quicker, hassle-free way to set up VMs for his projects.
Share via Link: You can now easily share all your files with your friends via a link, ensuring secure and fast file transfers. With peer-to-peer connections, your privacy is protected during sharing.
Improvements & Optimizations
File Transfer Performance: We’ve significantly improved file transfer speeds—uploading 10,000 small files now takes just 1 second, a 5000x speed boost compared to before.
Thunderbolt Priority:Based on community feedback, users reported that when both LAN and Thunderbolt were connected, the actual transfer speed was limited by the LAN connection. We’ve optimized the ARP settings to ensure that Thunderbolt is prioritized for data transfer, delivering the speed you expect.
RAID Stability: We’ve also enhanced RAID stability to ensure a more reliable and seamless experience.
What’s Next for ZimaOS?
We’d love to hear from you! Please let us know in the comments section what features you would like to see added to ZimaOS 1.4. We’re focused on iterating on existing features to make them more stable and reliable, and we’ll do our best to incorporate the community-requested features that matter most to you!
I’m testing zimaos on a custom server with i5-4590, 16 GB DDR3 RAM and several drives.
ZimaOS 1.2.5 didn’t cause many problems. But after updating to 1.3.0 my drives disappeared. Even though they are connected and I still have access to them via SMB, the “Storage” tab is empty. The Files application shows “Error loading…” at the top and resets every time it is launched.
According to the description, maybe the localstorage service is inaccessible or the API responses too slowly. You can open the inspect tool on the web page (press F12), switch to the network tab, and click on the storage page to check if there is any interface information with errors (usually red).
SMB can be accessed normally, indicating that there is no problem with the disk mounting, because if the mounting fails, the SMB share on the disk will be removed by the Files service. At present, it seems that only the interface such as obtaining the storage list has errors.
Possible problems: For example, the disk is about to be damaged, resulting in the block device list or health check not returning results immediately; for example, the localstorage service has been unable to start due to some incompatibility issues? (It will restart automatically normally)
It will be good if the problem can be located through the web console. If not, we may need to check it through remote support.
testo encountered a problem that the storage API does not display but can be used normally. It seems different from your situation. I will repeat your problem and you can confirm it whether it’s correct:
The disk has been used normally on Windows
When formatting, it says that the name already exists. You need to confirm whether there is already a disk or storage with the same name
Did the error message shown in the screenshot appear during formatting and activation? The reason behind the error may be that the disk is being occupied (if you have never used it in zfs or iSCSI, there is a possibility that the disk is opened while obtaining space usage information of unmounted hard disks in the background. Try formatting and enabling it later to see if it can succeed. If it can, it should be this problem. We will optimize it in subsequent versions)
What format is the disk? FAT12, FAT16, FAT32, NTFS or exFAT?
1.Failed on zimaos 1.3.0,then succeeded on win.
2.I tried “HDD-Storage10” or other name,it still says that the name already exists.
3.It appeared after a few minites during formatting.But “name exists” appeared immediately.
What browser are you using, I suggest you open the privacy browser and take a look, if you still have problems, you can turn the developer mode on and take a screenshot for us.
im using safari on a Mac and have tried privet but its still the same. I used chrome and its rendering correctly so seems there is an issue with safari.
no plugins active and on an iMac 13.7.2 Ventura. the strange thing is that I updated and I didn’t see the changes right away and was only the next day I seen the new ui changes and that’s when this happened.
I am having an issue after updating to ZimaOS 1.3. Similar to the top of this thread. However I am having issues with a Raid5 on 3 SSD’s and on 4 HDD’s.
If I booth the system with all drives installed I get an issue with finding any of the drives installed and will only register the OS but can not show any info for the Disk Manager section.
If I start the Cube with no expansion and then install the 4 HDD’s it will find them and everything is okay until I restart. However all the apps and services are run on the SDD’s so I cannot run any of the services. If I slide in the SSD housing I am still unable to see them and if I reboot I have to start all over again.
ZimaOS v1.3.0 is Now Available! 
New Features Highlights
Improvements & Optimizations
What’s Next for ZimaOS?
