StarWind SAN & NAS Free | Sometimes do not shutdown..

[tryllz]

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

[yaroslav (staff)]

Hi,

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

[tryllz]

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.

[dmytro (staff)]

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. ... collector/
https://www.starwindsoftware.com/resour ... 0838378624

Best regards,
Dmytro Malynka
Product Manager
StarWind Software

[tryllz]

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. ... collector/
https://www.starwindsoftware.com/resour ... 0838378624

Hi dmytro,

Logs were found in /opt/StarWind/StarWindVSA/drive_c/StarWind/logs.

Could not tar.gz them as the script file collectswlogs.run did not exist in the location mentioned.

Anyway, I have taken the logs and zipped them manually.

Files too large cannot attach in reply, uploaded here:

https://file.io/Nm8R1ytzn08i
https://file.io/k6gGE5DfFc4G

Gone through the logs and found the following errors relating to shutdown failure, in both systems.

Code: Select all

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.211446 2d6 Srv: *** SwSocket::Shutdown: shutdown() failed with error 10058!
12/30 15:42:41.213539 2d8 C[f9], CLEANUP_WAIT: iScsiConnection::recvData: Recv - peer shutdown
12/30 15:42:41.213591 2d8 C[f9], CLEANUP_WAIT: iScsiConnection::receive: recvData returned error 10058 (0x274a)!
12/30 15:42:41.213918 2d8 Srv: *** SwSocket::Shutdown: shutdown() failed with error 10058!
12/30 15:42:41.214910 2d8 Srv: *** SwSocket::Shutdown: shutdown() failed with error 10058!
12/30 15:42:41.215533 2d8 Srv: *** SwSocket::Shutdown: shutdown() failed with error 10058!
12/30 15:42:41.215895 2d7 S[f9]: iScsiSession::~iScsiSession: ~Session
12/30 15:43:07.366945 2f IMG: *** ImageFile_ScsiExec: SCSIOP (0x85) is not supported.
12/30 15:43:07.368263 2f IMG: *** ImageFile_ScsiExec: SCSIOP (0x85) is not supported.

[tryllz]

Gone through the logs and found the following errors relating to shutdown failure, in both systems.

Code: Select all

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.211446 2d6 Srv: *** SwSocket::Shutdown: shutdown() failed with error 10058!
12/30 15:42:41.213539 2d8 C[f9], CLEANUP_WAIT: iScsiConnection::recvData: Recv - peer shutdown
12/30 15:42:41.213591 2d8 C[f9], CLEANUP_WAIT: iScsiConnection::receive: recvData returned error 10058 (0x274a)!
12/30 15:42:41.213918 2d8 Srv: *** SwSocket::Shutdown: shutdown() failed with error 10058!
12/30 15:42:41.214910 2d8 Srv: *** SwSocket::Shutdown: shutdown() failed with error 10058!
12/30 15:42:41.215533 2d8 Srv: *** SwSocket::Shutdown: shutdown() failed with error 10058!
12/30 15:42:41.215895 2d7 S[f9]: iScsiSession::~iScsiSession: ~Session
12/30 15:43:07.366945 2f IMG: *** ImageFile_ScsiExec: SCSIOP (0x85) is not supported.
12/30 15:43:07.368263 2f IMG: *** ImageFile_ScsiExec: SCSIOP (0x85) is not supported.

Kindly ignore this as this is of today and I haven't shutdown the storage systems today, I misunderstood, and unsure why its showing shutdown errors when the system was not shutdown.

[dmytro (staff)]

Hello tryllz,

Happy New Year!

Thank you for providing the logs. We have started investigating the case.
Do my best to get the results this week.
Thank you for your understanding.

Best regards,
Dmytro Malynka
Product Manager
StarWind Software

[dmytro (staff)]

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 session during which our engineer will update the StarWind Virtual SAN services to a newer version.
Otherwise, we are going to release the next version of StarWind SAN & NAS in two-three weeks, and you would able update to it manually after the release.

Best regards,
Dmytro Malynka
Product Manager
StarWind Software

[tryllz]

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 session during which our engineer will update the StarWind Virtual SAN services to a newer version.
Otherwise, we are going to release the next version of StarWind SAN & NAS in two-three weeks, and you would able update to it manually after the release.

Best regards,
Dmytro Malynka
Product Manager
StarWind Software

Hi Dmytro,

I haven't been on the server as of the last 2 weeks due to work commitments, and thus would not be able to comment. If I get time to work on the server I will definitely update you, else I will wait for the udpate.

Appreciate your team taking time through the logs to find the issue.

Thank you.

[tryllz]

Hi Dmytro,

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

Thank You

[yaroslav (staff)]

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 please clarify when it would be suitable for you to have a quick remote session? Please contact us at support@starwind.com to log a call. Use this thread as a reference.
Also, do you have any Windows host running on your network by chance? It would be needed to perform the upgrade.

Thank you!

[tryllz]

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 please clarify when it would be suitable for you to have a quick remote session? Please contact us at support@starwind.com to log a call. Use this thread as a reference.
Also, do you have any Windows host running on your network by chance? It would be needed to perform the upgrade.

Thank you!

Hi yaroslav,

Thanks for the support, really appreciate it.

Spent the last few days understanding some configuration which if I had realized before, this thread might not be needed.

I realized I had connected the StarWind storage to 2 systems.

1) vCenter host storage
2) Veeam as proxy

When shutting down systems I would shutdown vCenter and the ESXi hosts followed by StarWind storage not shutting down Veeam Server connected to the storage which resulted in the storage not shutting down. And the reason for "sometimes" is I sometimes used to shutdown the Storage after everything else, until I noticed they shutdown properly after everything else is shutdown.

Thus apologizing, I believe the systems are working fine.

On a separate note, I would like to upgrade because even though the above is correct the Storage still shows the unmounting failure before shutting down.

Thank You

[yaroslav (staff)]

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.

[tryllz]

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..

[tryllz]

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.

I have sent an email to the address provided, looking forward to hear back.

Thank you yaroslav.