I've managed to recreate this but not sure if I can repeat as I've been doing a lot of messing around this afternoon with upgrading StarWind versions in the lab. But it was something along the lines of this: Two HA nodes and one iSCSI initiator connected via two MPIO iSCSI channels (so four iSCSI in...

Managed to screen grab the splash screen. Cheers, Rob.

The splash screen is wrong too when you reconnect to the server.

Err... just upgraded from build 6884 to 7185 and noticed the following when restarting the service: sshot-53.png I'm not running the vSphere version! I've not updated the other node yet so I've included how it appeared in build 6884 (sshot-54) and for completeness, how it appears in the services lis...

I've just upgraded to build 7185 from 6884 and this bug is still present, i.e. after upgrade the CFG file changed from: <iScsiDiscoveryListInterfaces value="1"/> to: <!-- <iScsiDiscoveryListInterfaces value="1"/>--> Now interestingly, the existing iSCSI initiators have reconnecte...

Interesting, I noticed that I wasn't on the latest version in the lab so just upgraded node #1 from build 6884 to build 7185 and in this instance after the service is restarted, fast synchronisation is actually running, i.e. I didn't have to do anything.

Cheers, Rob.

I noticed that the latest build is 7185. The post needs updating please:

http://www.starwindsoftware.com/forums/ ... f=5&t=2069

Cheers, Rob.

Won't be able to follow this up I'm afraid as I had to trash that storage as part of the other post about recovery after clean shut-down.

Cheers, Rob.

LSLF storage re-created and same test carried out. StarWind v8 does not recover from a planned and controlled power down and power up. You have to manually mark one of the nodes as synchronised and then it jumps back into action.

Cheers, Rob.

So what *exactly* you'd like to see in terms of automatic recovery for absolutely broken shutdown

I think first we should concentrate on getting a clean shutdown and power-up working first.

Cheers, Rob.

Rather worryingly in that last test of clean shutdown and power-up, node #1 lost one of it's devices as well. See attached screenshot.

I have been messing around a lot with the lab here so I'm going to re-create all the storage.

Cheers, Rob.

StarWind *DOES* tracking of what was written last (some sort of a log) and is trying to do automatic recovery in case of all replicas went down @ the same time. All I can say is that it doesn't do automatic recovery in this pretty well defined clean shutdown & power-up sequence: Clean shutdown:...

In terms of doing a clean shutdown of StarWind for maintenance, one of the checks one may want to make is that all iSCSI targets are disconnected. At the moment, you have to go manually through each storage device one at a time. It would be very useful to display a summary at the server level. You a...

See attached screenshots from the lab. That doesn't look right to me. Different numbers of storage1*.spspx files in the two nodes? These two nodes are in sync.

Cheers, Rob.

Thanks Bill - my mistake as well as not spotting the "Storage Server" bit in the title. Panic over

Cheers, Rob.