-
-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem in Storage Manager using a SCSI data drive in a Proxmox VM #1545
Comments
These Portmap Options are only for Sata Controller: https://github.com/AuxXxilium/AuxXxilium/wiki/Arc:-Loader-Portmap Why do you have 2 Sata Controller in VM Config? DSM will show your Disks as Sata, this is nothing to worry about. I don't know why you get 2 Pools with 1 Disk. |
Really don't know why. This sysinfo is with no SATA drives attached and arc.img boot from SCSI: C8FABUGLJ |
Wrong code, but where is your problem? it lookes like, something went wrong with your dsm installation. |
where is your problem? i only see a healthy storagepool?! |
I was trying to make an optimal configuration using SATA as boot loader and SCSI for data disk (because under VM is way much performant), and I got stuck with this twin "Storage Pool" problem. If I use SATA for data disk, I see only one storage pool and config is consistent. If I use SCSI as data disk, I got the two storage pool and if I delete it I get an inconsistent situation (I can't recreate it) - check the screenshots on the first post |
Check the last screenshot of the first post: healty but 0 bytes allocated - it's an inconsistent config. And you can't add volumes, neither remove the only left storage pool. I repeat, IMHO is an inconsistent cofnig |
if you delete all storage pool, what will happen? |
you click on Remove on the only left and nothing happens Registrazione.schermo.2024-05-18.alle.12.37.50.mov |
Reboot? |
the same |
boot to config mode, use format disks function in dev section. |
If I can ask, for my knowledge: how SCSI drives are seen by DSM? How loader make them work under DSM? |
They are seed as SATA since DSM can't use them oob. My ESXi SCSI Controllers are working and others don't have these issue with Proxtrash. |
Oh, I see. Good luck. |
BTW, I was only using the wrong loader: yours. With another loader works like a charm. |
and which loader? and you selected also DS1019+ in this loader? |
I bet you are smart enough to find it by yourself. Thank for your time. |
i know 20 different, so tell me. |
mm works here, sata0 as arc.img and scsi0 as first disk, works on a DVA3221 build.. if i remove the storage pool 1 it unmounts the volume correctly and removes the pool, creation also works. Registrazione.2024-06-02.094923.mp4 |
Describe the Bug
I made a Proxmox VM with SATA:0 imported from arc.img (latest / yesterday - 24.5.16) and a SCSI drive that I want to use as data drive, using DriveIdxMap (activeports or max ports, does not make difference). Once full installed, if I create a volume using Storage Manager (SCSI data disk is seen as SATA but in my ignorance it can be completely normal), I will see 2 storage pools and one of them has the new volume in it. If I remove the volume, Storage Manager remains in an inconsistent state with one storage pool without volumes and does not allow to create a new volume neither remove the storage pool.
Screenshots
F5DZ9WRNB
Hardware
Many thanks for your help
The text was updated successfully, but these errors were encountered: