Sharing a single target to EWF-protected Windows initiators

[Yuriy (staff)]

Any progress with this bug now that you've known the cause and the fix?

We plan to release new build on monday (Oct 1 2012).
New build will be available for download from our site.

[digitalis99]

We plan to release new build on monday (Oct 1 2012).
New build will be available for download from our site.

Cool. Is there any way to know what the build number is before I download the installer entirely and check it?

[Yuriy (staff)]

digitalis99,

You can download last build of StarWind here:
http://starwindsoftware.com/tmplink/Sta ... 120927.exe

Waiting for your response!

[anton (staff)]

You'll have build date as a part of a setup executable.

We plan to release new build on monday (Oct 1 2012).
New build will be available for download from our site.

Cool. Is there any way to know what the build number is before I download the installer entirely and check it?

[digitalis99]

digitalis99,

You can download last build of StarWind here:
http://starwindsoftware.com/tmplink/Sta ... 120927.exe

Waiting for your response!

Ahh...not impressed so far. Installed this build and Windows booting from the target errors out with exact same error message as before (failure to find winload.exe).

I followed Anton's loose directions by creating an image file first, verifying I could boot successfully from it, converting it to an .ibv, removing that device, and creating a new device from the existing .ibv using ROW discard mode. Booting from that target failed.

What am I missing?

[anton (staff)]

Works absolutely brilliant here. Can you provide a logs so we'd see you did install recent build and doing what you're supposed to do?
Also tomorrow guys will provide step-by-step guide on what WE did here (just to figure out what's different from your side).

digitalis99,

You can download last build of StarWind here:
http://starwindsoftware.com/tmplink/Sta ... 120927.exe

Waiting for your response!

Ahh...not impressed so far. Installed this build and Windows booting from the target errors out with exact same error message as before (failure to find winload.exe).

I followed Anton's loose directions by creating an image file first, verifying I could boot successfully from it, converting it to an .ibv, removing that device, and creating a new device from the existing .ibv using ROW discard mode. Booting from that target failed.

What am I missing?

[digitalis99]

Works absolutely brilliant here. Can you provide a logs so we'd see you did install recent build and doing what you're supposed to do?
Also tomorrow guys will provide step-by-step guide on what WE did here (just to figure out what's different from your side).

I don't know how much of log you want to see, but I'm running the build I was pointed to:

The log file name: 'logs\starwind-20121002-092824.log'
10/2 9:28:24.164 1c8 Srv: StarWind iSCSI SAN Software v6.0.0 (Build 20120927, [SwSAN], Win64)
10/2 9:28:24.164 1c8 Srv: Built Sep 27 2012 19:34:39
10/2 9:28:24.164 1c8 Srv: Windows 7 Unknown Edition Service Pack 1 (Build 7601)
10/2 9:28:24.164 1c8 Srv: System CPU count: 8
10/2 9:28:24.164 1c8 Srv: CPU affinity mask 0xff from 0xff.
...

I've tried a few different methods already, but every time I create a new device in ROW with discard that points to an existing .ibv, Windows fails to boot early in the boot process with the 0xc000000e status code stating it can't find \Windows\system32\winload.exe.

Switching the device back to Snapshot and CDP mode, again using the same .ibv, enables a machine to boot from it again.

[Yuriy (staff)]

digitalis99,

Please, try to install Windows directly on IBV Growing Image -- skip the steps concerned with ImageFile device.
And then go to the ROW mode.

[anton (staff)]

Shouldn't converting from IMG also work? What did our QA team do EXACTLY?

digitalis99,

Please, try to install Windows directly on IBV Growing Image -- skip the steps concerned with ImageFile device.
And then go to the ROW mode.

[digitalis99]

Shouldn't converting from IMG also work? What did our QA team do EXACTLY?

digitalis99,

Please, try to install Windows directly on IBV Growing Image -- skip the steps concerned with ImageFile device.
And then go to the ROW mode.

I already tried both methods, neither worked. I can boot off of the target successfully when it's an .ibv in growing mode or it's an .img. Any time the device is removed and re-created as an .ibv in ROW with discard mode, the boot failures occur.

Yes, I need to know the exact steps you guys used to test this, because I haven't come up with a single logical combination that works as you say it should.

[Yuriy (staff)]

digitalis99,

Let's organize a remote session?
Details in private