Have any Beelink users managed to get zimaOS to recognise NVME SSDs?
I have both Raid 0 and Raid 5 pools that are accessible via the dashboard and smb. I was initially using zimaos 1.4.2 and have updated to 1.4.3 with no change. Although I can read / write to the NVMEs I would like some information to verify the condition of my SSDs
Hi!
I have a ssd carrying the SO and three ssds in a Raid 5 pool.
I startet with os v.14.1 and sidks weren’t properly recognized under the tab but perfectly funtional.
Ltaer i did the update to os v. 1.4.2 and they finally showed up..this morning i switched to v.1.4.3 and still they are in place.
I have installed zimaos on the eMMC and have populated the ssd bays with 6 nvmes, none of which are recognised correctly in the dashboard. However both my raid 0 and raid 5 pools are working. The SSDs are sharable via smb including as time machine backup disks, and I have installed plex and syncthing with no issues.
I have since discovered that the nvmes are correctly identified in the local-storage.db file in the casaos database folder on the system drive. So I would hope that it is all working under the hood but I would not trust it in it’s current form for any really vital data. So I’m hanging on to my old WD NAS a little while longer!
Thank you for the feedback. Although ZimaOS was initially designed for Zima devices, we will improve its compatibility with other hardware and make it a general NAS OS. Please give us some time. We will actively respond to user feedback. We will spare no effort to create a trustworthy, simple, and user-friendly NAS system.
Hello, this problem has been fixed in version 1.4.2, so can you provide the remote ID and account password? We would like to determine the cause of this problem
The first version of zimaos I tried was 1.4.2 and I have since upgraded to 1.4.3. I am generally happy with current configuration where I have a raid 0 pool for time machine backups and a larger raid 5 pool made from 4 x 2TB nvme ssds. I am able to run plex and syncthing apps and if the remaining issues with the dashboard are resolved I hope to retire my older WD NAS at some point…
The dashboard does not recognise any of my nvmes and in the case of the RAID 5 pool it does not recognise the amount of data written. Although 500GB has been written to the RAID 5 pool the dashboard suggests that the pool is empty with a full 6TB available (refer to screenshot above). When I access the same pool via SMB, MacOS indicates that there is only 5.5TB available which makes more sense. So my impression is that the implementation of the dashboard requires more work. I have already shared some of my configuration files with @Zima-Giorgio and am willing to pass them on to you via DM. I do not share remote access credentials and passwords as that would defeat the object of having my own private server
Same issue for me also. A new install on 1.4.3 on a Beelink ME Mini as of today and have the exact same failure to identify the drives - at least in the UI. The drives have initialised as a RAID 5 set ok and now have data on them.
Sorry to jump in here, but i am having an identical problem.
When i try to follow the instructions from the above post - How to Resolve Disk Display Issues on Non-ZimaCube Devices
I get no result for lsblk -o hctl
There are two set of instructions in that post, the first is for SATA drives, the second is for NVME drives, this is the bit you will need.
For me I changed the four drives in the conf file were setup as :
0a,0b,0c,0d (plus the other descriptors),
when I ran the command line from the instructions it showed that these needed changing to: 03,04,05,06 (even though I only had 3xNVME drives).
Once changed and restarted as per the instruction the drives showed up correctly as per my screen shot in the previous post.
)
