Closed corcorac closed 8 months ago
Can you run the command with the path test1 and see what the return message is? smartctl -a -n standby ${path} -j
I checked, and it says unsupported here. I've made a judgment call, and if it's not supported, it's considered healthy.
Sorry about that, I was asleep at the time. I can still run it on my end if need be? I imagine it's the same and smart info isn't passing through the scsi driver, but is with sata. Thank you on the judgment call, that works for me since proxmox does still monitor smart on the disks.
May be worth it to still warn "healthy, no smart support" on hover as some may not know to ensure they're checking smart outside of the VM, but not exactly imperative either.
I have dealt with this issue and still consider it healthy without a clear judgment of failure. Thanks for your feedback. I'll close the file and reopen it if in doubt.
Drives added in GUI as scsi# (scsi1, 2, 3, etc) or passed through as scsi# type will show as "Unhealthy" no matter what settings are chosen. Passed through as sata# (sata1, 2, etc) will show healthy, show temp readout, and allow for raid/creating storage pools, etc.
In a Proxmox VM, using steps in documentation linked on main Github page, both before and after expanding the original image. I can provide any logs/info needed to help.
Images of scsi1 in ZimaOS, drive marked unhealthy:
Proxmox settings qcow:
Proxmox settings raw:
ZimaOS:
Images of scsi1 working correctly in CasaOS minus drive temp:
Proxmox settings:
CasaOS: