yaroslav (staff) wrote:Hello tryllz,

Thank you for your update. Please let us do the update together at your convenience. Please contact us at support@starwind.com to log a call when you are in a position to do an update. Use this thread as a reference.

Sure, thanks..

Hello tryllz, The upgrade procedure does not delete anything but the StarWind Virtual SAN's targets would be disconnected during the update. It will be reconnected once the upgrade is done. However, I would highly recommend backing up your data prior to the update process just in case. Could you pl...

Hi Dmytro,

May I ask if updating the storage will remove all the data stored on the SAN & NAS ?

Thank You

Hello tryllz, Hope you are doing good. Would you mind clarifying whether the problem has occurred after you had submitted logs? At the moment, we have seen a potential problem only in the logs for December 28th. In order to work around that problem, I would like to suggest scheduling a remote sessi...

Gone through the logs and found the following errors relating to shutdown failure, in both systems. 12/30 15:42:41.209583 2d7 C[f9], LIN: iScsiConnection::doTransition: Event - LOGOUT. 12/30 15:42:41.210535 2d6 C[f9], IN_LOGOUT: iScsiConnection::doTransition: Event - LOGOUT_ACCEPT. 12/30 15:42:41.2...

Hello tryllz, Could you please collect and send us the logs of your two SAN & NAS appliances? To collect the logs use command-line or web interfaces. These pages should guide you. https://knowledgebase.starwindsoftware.com/troubleshooting/how-to-collect-logs-with-starwind-log-collector/ https:/...

yaroslav (staff) wrote:Hi,

There must be something using that volume. Try running the lsfs command for that one.

Thanks, the command does not seem to be a working one as in the attachment.

Hi, I'm running 2 StarWind SAN & NAS Free versions, both of them display this behavior. Sometimes both of them do not shutdown and show the below even if waited for extended period of time, then I have to force shutdown. Anything I can look into to determine the cause. Thank You https://i.ibb.co...

So as I understand, only 1 Starwind Appliance can be installed in vCenter at 1 time.

Also, I have 2 StarWind Appliance, I manage to install 1 and connect it to the vCenter, the other one when trying to connect to the same vCenter fails, is this normal, or can only 1 be connected ? https://i.ibb.co/PrHF0pf/Capture.png Logs attached. The plugin installed on the 1st Storage Appliance d...

Hi Dmytro,

Its working now, only a small glitch, it says that I can add vCenter by FQDN or IP, but it does not accept FQDN nor does it allow to type FQDN manually as can bee seen below (pasted FQDN).

Hi Dmytro,

Thanks for the prompt response, I do see the update date as being 5th July, nonetheless I'll try and update here accordingly..

yaroslav (staff) wrote:Colleagues,

Did you try re-deploying the VM?

I have deployed more than 1 Storage Appliance more than once, did not work.

yaroslav (staff) wrote:Did you create the StarWind Devices on those disks? If not, can you try creating some so you consume the capacity of the disks?

I'm not creating StarWind devices on the disks, I'm creating StarWind as a VM on ESXi and then attaching disks to the VM

yaroslav (staff) wrote:You were still not able to connect to vCenter?

I'm afraid no, the steps mentioned in both links do not work when StarWind SAN and NAS is installed as a VM on ESXi.