How to Resolve Disk Display Issues on Non-ZimaCube Devices

Operating System ZimaOS
1

Introduction:

With the continuous iteration and upgrades of ZimaOS, more and more users have begun installing and using ZimaOS on their own x86 devices. Although ZimaOS was primarily designed for ZimaCube, we sincerely appreciate the enthusiasm and trust from everyone. During this process, we have learned that some users with non-ZimaCube devices have encountered UI compatibility issues, particularly with disk slot display. Therefore, we have compiled this document to help you resolve these issues smoothly. Once again, thank you for your ongoing support!

Please confirm your disk interface type first.

SATA Interface Disk :

  1. Run the following command to view disk information:
lsblk -o hctl
  1. Modify the SataStartNumber value in the local-storage.conf configuration file. If the result of Step 1 starts from 0, set the SataStartNumber value to 0:
vi /etc/casaos/local-storage.conf

1897Ă—544 88.2 KB

  1. Restart the service:
systemctl restart zimaos-local-storage

NVMe Interface Disk :

  1. Run the following command to view the NVMe PCI address:
lspci
  1. Modify the NVME value in the local-storage.conf configuration file, setting the value to the NVMe PCI address. Use commas (,) to separate multiple addresses:
vi /etc/casaos/local-storage.conf

2718Ă—1066 285 KB

  1. Restart the service:
systemctl restart zimaos-local-storage

If you have any other questions, please feel free to leave a comment. Thank you again for your support!

3 Likes
2

Thanks, but I had to move on. I have installed OMV and all is good. I’ll try ZimaOS in a year or so after it matures a bit more.

1 Like
3

on a lincstation n1 all i did was reinstall zimaos with the new version and now it works.

1 Like
4

Thank you, great documentation!

1 Like
7

for anyone who wants more than 6 hard drives or connects them over a pice card. you can just change the SataStartNumber to the number of the drive you want to add to your Raid (in my case it was 32) an than it shows up in the ui and you can expand/create an raid. The other drives don’t disappear and work totally fine just some little ui mishaps (they show at negativ positions like -24 or so). For the devs maybe a drop down or so would much appreciated here. Maybe in the new dev mode(and ik its not officially supported but still would be awesome Thx).

1 Like
8

Hello,
I tried the procedure above on zimaos 1.4.2 and my nvme is still not accessible, any further advice to recover ?

9

Hey, would you please explain your issue in more detail? It will be helpful if you attach the screenshot here.

10

Very important finding (at least for me, and probably for others too):

Using a COMMA (,) between PCI addresses did NOT work. Instead, you must use a SPACE.

[- Example -]

Not working >>> NVME = 0a:00.0**,**0b:00.0
Does work >>> NVME = 0a:00.0 0b:00.0

Anyway, I think the documentation should clarify some points better…

You only need to modify the SataStartNumber line if your issue is related to SATA. The same applies to NVMe. If a NVMe is missing, than only modify the NVMe line.

You don’t have to change both unless you actually have both issues. Right now, it reads as if both changes are required, which can be confusing!

For NVMe specifically:

The line should only include as many PCI addresses as you find in your „Ispci“-output under “Non-Volatile memory…”.

Example: If you find 5 entries with “Non-Volatile memory…”, then you should update the NVME line to 5 PCI adresses.

Also note: The „lspci“-output does not always display entries in separate lines, so check each line carefully.

Since i have only two, i assume that the 4 pci adresses are some sort of templates or placeholders…