Unable to install/update - Stopping the StarWindService

Software-based VM-centric and flash-friendly VM storage + free version

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
Ionic
Posts: 2
Joined: Thu Sep 21, 2023 8:54 pm

Thu Sep 21, 2023 9:09 pm

Hi,
I've been using StarWind vSAN free in my homelab since 2021. I've upgraded from v8_14338 to v8_14398 without any issues in 2022 after reinstalling one of my hosts on Windows Server 2022 and am revisiting now because I was gonna expand my image file.
Now I saw, that there were a lot of newer versions, so I went on to update to v8_15260. I've stopped the cluster node, disconnected my iSCSI targets and started the installer. Now I was prompted to close the management console (no issues there) and am stuck now at the "Stopping the StarWindService service..." for ages. After like 5 minutes of it looping (I witnessed the successful stopping of the service, so it was so stopped after a few seconds), I killed the process and rebooted the server. No help there. Then I went ahead and uninstalled the software via the unins000.exe. Now I am expecting a fresh install, but again it shows that message, while the service doesn't even exist yet. I'm out of ideas what to try next and stuck without redundancy, as I'm unable to get my second instance back up. I've also tried the v8_14398 installer which I had lying around still.
Screenshot 2023-09-21 225748.png
Screenshot 2023-09-21 225748.png (13.51 KiB) Viewed 3074 times
I've ran the installer another time with " /LOG="C:\StarWindUninstall.log"", so here is the output (sadly doesn't tell much).
2023-09-21 22:47:11.069 Log opened. (Time zone: UTC+02:00)
2023-09-21 22:47:11.069 Setup version: Inno Setup version 5.5.9 (a)
2023-09-21 22:47:11.069 Original Setup EXE: C:\Users\admin\Desktop\starwind-v8_15260.exe
2023-09-21 22:47:11.069 Setup command line: /SL5="$500BC,141906806,355840,C:\Users\admin\Desktop\starwind-v8_15260.exe" /LOG=C:\StarWindInstall.log
2023-09-21 22:47:11.069 Windows version: 10.0.20348 (NT platform: Yes)
2023-09-21 22:47:11.069 64-bit Windows: Yes
2023-09-21 22:47:11.069 Processor architecture: x64
2023-09-21 22:47:11.069 User privileges: Administrative
2023-09-21 22:47:11.148 64-bit install mode: Yes
2023-09-21 22:47:11.163 Created temporary directory: C:\Users\admin\AppData\Local\Temp\is-CRRHP.tmp
2023-09-21 22:47:11.366 Extracting temporary file: C:\Users\admin\AppData\Local\Temp\is-CRRHP.tmp\StarWind_EULA_Commercial.rtf
2023-09-21 22:47:14.726 Extracting temporary file: C:\Users\admin\AppData\Local\Temp\is-CRRHP.tmp\StarWind_EULA_Evaluation.rtf
2023-09-21 22:47:14.726 Extracting temporary file: C:\Users\admin\AppData\Local\Temp\is-CRRHP.tmp\StarWind_EULA_Free.rtf
2023-09-21 22:47:50.429 Extracting temporary file: C:\Users\admin\AppData\Local\Temp\is-CRRHP.tmp\SwsChk64.exe
2023-09-21 22:47:50.632 Extracting temporary file: C:\Users\admin\AppData\Local\Temp\is-CRRHP.tmp\SwsChk64.dll
2023-09-21 22:47:50.632 Extracting temporary file: C:\Users\admin\AppData\Local\Temp\is-CRRHP.tmp\SwsChk-xml-64.dll
2023-09-21 22:47:50.726 Extracting temporary file: C:\Users\admin\AppData\Local\Temp\is-CRRHP.tmp\SwsSysMan64.dll
2023-09-21 22:47:50.742 Extracting temporary file: C:\Users\admin\AppData\Local\Temp\is-CRRHP.tmp\tools64.dll
2023-09-21 22:47:50.742 Extracting temporary file: C:\Users\admin\AppData\Local\Temp\is-CRRHP.tmp\LogLib64.dll
2023-09-21 22:47:50.757 Extracting temporary file: C:\Users\admin\AppData\Local\Temp\is-CRRHP.tmp\NativeLib64.dll
2023-09-21 22:47:50.757 Extracting temporary file: C:\Users\admin\AppData\Local\Temp\is-CRRHP.tmp\libcrypto-364.dll
2023-09-21 22:47:50.976 Extracting temporary file: C:\Users\admin\AppData\Local\Temp\is-CRRHP.tmp\libssl-364.dll
2023-09-21 22:47:51.007 Extracting temporary file: C:\Users\admin\AppData\Local\Temp\is-CRRHP.tmp\vcruntime14064.dll
2023-09-21 22:49:20.882 Extracting temporary file: C:\Users\admin\AppData\Local\Temp\is-CRRHP.tmp\dotnet-runtime-2.0.3-win-x64.exe
I'd be grateful for any ideas on how to proceed here. Maybe there is a cleanup script of some sort available.
yaroslav (staff)
Staff
Posts: 2361
Joined: Mon Nov 18, 2019 11:11 am

Thu Sep 21, 2023 10:40 pm

Greetings,

Sorry to read that. If only you reached out earlier to us so we could save time for redeploying StarWind VSAN.
It looks like the service is hanging there.
1. Kill StarWindService on the affected node.
2. Go to Services.
3. Set StarWind Autostart to disabled.
4. Reboot.
5. Re-run installer.

You will need to recreate the replica afterward.
1. Run the script for removal of the replication partner
2. Use another script to add replication.

I'd also suggest removing the cache once the system is stable again.
Ionic
Posts: 2
Joined: Thu Sep 21, 2023 8:54 pm

Fri Sep 22, 2023 4:22 pm

Hi,

somehow I got it working again. I still had all my files, so there was no need to resync again. Also I had a backup of my StarWind.cfg.
I tried installing with the vSAN Server preset before which didn't work as explained above. I now tried installing only a minimal subset of components -> service only... which worked.
I then narrowed the issue down to the "Cloud Replicator for VTL" component. Deselecting it, I had no issues installing the update/from scratch.
After that I just placed my StarWind.cfg back into the program folder and everything worked again as I still had my image files where I left them.

When upgrading the second node, the same issue arose, but as mentioned above, deselecting the "Cloud Replicator for VTL" component, I had no issues upgrading in place.
Thanks for your help though, I will keep these options in mind if I have further issues down the road.
yaroslav (staff)
Staff
Posts: 2361
Joined: Mon Nov 18, 2019 11:11 am

Sat Sep 23, 2023 1:05 pm

Hi,

Thanks for your update! Happy to read that it worked.
Post Reply