Email sent.

I apparently used version 8.0.9996.0 from 2016. I saw very low usage at the time I did the tests, so shouldn't be the problem. Should I just attach the log here in the forum? The events triggered fast-syncs. So the node I did the changes on was the one that needed to sync from the other node. Only t...

Hi. I recently upgraded Starwind Virtual SAN on my two physical dedicated Supermicro servers from an much older version (like 2017-2018) to version 8.0.15159.0. I had some problems back in the day with unstability, and when I found a stable version I just sticked to that one. Now after some years I ...

Running ESX6.5 GA-release, build 4564106

best regards
Lars Ove

I created a new HD-device. Changes the parameter in the config on both nodes and restarted both nodes (one + resync + other one). Did a rescan on a few ESXi hosts. When adding datastore, the device is still identified as HDD... This was on a new device never added to any hosts until after the config...

We have some NVME-drives in our Starwind-nodes, and I'm wondering if there are any performance tests on NVME-drives + Starwind with the latest release vs previous release.
As we have no problems with the current version, I see no reason to upgrade unless there are performane gains etc.

No, not yet.
I will try to create a small test-device, HA and non-HA to check if NEW devices are detected correctly.

From log:
G:\p3600_2\p3600_2.img': disk is SSD, UNMAP supported

So I will have to look at the ESXi side. Very strange.. ALL hosts have been restarted, but not simultaneously of course (NOT possible).

Will check logs. I have tried rescans "here and there" without any luck.
Running vCenter 6.5 and ESXi 6.5

Sigh.. I did a reboot of all hosts, one and one, and still not identified as flash storage. Did the change like this: <device file="My Computer\F\p3600_1\p3600_1.swdsk" name="imagefile1" SolidStateDrive="1"/> This should be the correct method? Might be a delay in vCente...

btw, the ESXi-method sucks, as no host can use the datastore, not only the host I make the changes on. Not ideal when having 30-ish hosts.. :\

It might be that I have to reboot all hosts first. Will check.

I tried this change on both nodes and rebooted host. No automatic change of disk type.. :\
Is this a change in R5, og should the current release from Aug support this setting?

OK.
Are you worried about a crash, or just that a reboot is needed? A reboot is no problem.

GREAT!
This can be done on HA-devices by changing on one node, sync and then the other node? To prevent downtime.