I’m running ZimaOS in a Proxmox VM and I have an existing RAID5 array with 3 disks. When I try to expand the array the disk selection window is broken. (See below)
Here is how the current RAID array is shown. This is ok.
And I have a new disk as follows:
Can you please fix this issue?
Hey, we want more info.
What are the specs of your machine?
[the detailed specs of the machine where the problem happens]
As I mentioned the system is a Proxmox VM.
To ensure I didn’t do something stupid I just recreated the array again from scratch. i.e removed the disks from the VM and then added 3 disks again. I created a RAID 5 array from those 3 disks (this works perfectly and shows the complete list of disks and their capacities for me to choose from). Then after the array was in sync I closed the OS down. Added another disk to the VM. Went to storage, where it shows me a new disk has been added, and then I selected the array I just created and choose Expand and then the list of disks is shown as above (i.e. just the 0 in the box representing each disk). Also I think the list should only have 1 disk in it so I don’t know why it is trying to show so many disks. There is only one free disk to be used to expand this array.
Here is the VM characteristics:
Let me know if there are some log file output you’d like to see. I’m very new with ZimaOS and have not fully come to grips where everything is located on the OS side.
A little bit more information. For some reason the Expand arry shows a disk list with 10 disks of 0 B, however there are only 7 disks (including the OS disk) attached to the VM.
The local-storage configuration is as follows (if that helps):
root@MyNAS:~# cat /etc/casaos/local-storage.conf
[common]
RuntimePath = /var/run/casaos
[app]
LogPath = /var/log/casaos
LogSaveName = local-storage
LogFileExt = log
DBPath = /var/lib/casaos/db
ShellPath = /usr/share/casaos/shell
[server]
USBAutoMount = True
SataStartNumber = -7
DiskSleepWaitTime = 0
NVME = 0a:00.0,0b:00.0,0c:00.0,0d:00.0
Thanks for your detailed info. ZimaOS is built for installing on physical machine. But our engineer will look at this issue. And it might be fixed.
I am not sure if it is possible to set the drive mode to AHCI. Would you try to achieve it and make the system volume on the AHCI one instead of the SCSI one?
Besides, many users failed to install ZimaOS in PVE. How did you achieve that? It will be perfect if you share your detailed steps for installing it in PVE.
I added my instructions for installing on Proxmox as a new topic.
ZimaOS install on Proxmox (for testing) - Insight & Feedback - IceWhale Community Forum
Just to confirm whether this problem is related to running on a VM, I tested on a native x86_64 system today with 6 SSD drives.
I can confirm the exact same result as I first got. The initial drive creation with 3 drives is perfect and shows all disks and correct capacities but when select the “Expand RAID” → Start button to extend the RAID5 array, I get an “Expand storage” window which seems to be listing 10 disks (but this system has only 7 disks in it) with no information and then with “0B” showing. Exactly the same as the first screen shot I sent you.
There is definitely a bug here somewhere .
