<div dir="ltr">Thanks for reply everyone. My issue was resolved after using different driver set in creation of win pe. I don't now why, but that helped and setup process went like a breeze. I used links provided by ccboot project: <a href="http://www.ccboot.com/download.htm">http://www.ccboot.com/download.htm</a> , see Intel-drivers etc.Hope that helps someone with similar issues. =)<br></div><div class="gmail_extra"><br><div class="gmail_quote">2014-11-17 20:59 GMT+03:00 shouldbe q931 <span dir="ltr"><<a href="mailto:shouldbeq931@gmail.com" target="_blank">shouldbeq931@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Mon, Nov 17, 2014 at 3:03 PM, Andrew Bobulsky <<a href="mailto:rulerof@gmail.com">rulerof@gmail.com</a>> wrote:<br>
> Ivan,<br>
><br>
> The 7E stop code is usually something esoteric. If the drivers weren't<br>
> loading up at all, you'd get a 7B error, or "Inaccessible Boot Device."<br>
><br>
> As I recall, anyway ;)<br>
><br>
> I saw that you scripts set your gateway to 0.0.0.0. Something makes me think<br>
> that this may be causing a problem. I believe Michael added functionality to<br>
> his sanbootconf driver that works around the gateway issue in a very clean<br>
> way; you may want to try bundling it into your WinPE.<br>
><br>
> Anyway, I speculate that your gateway of 0.0.0.0 might be a problem...<br>
> Because that's *technically* a real IP address.<br>
><br>
> Try clearing the setting completely instead, by running<br>
><br>
> clear netX/gateway<br>
><br>
> in place of the line where you're setting it.<br>
><br>
> No clue if it'll help, but I'd say it's wort a shot :)<br>
><br>
> Regards,<br>
> Andrew<br>
><br>
><br>
><br>
> On Monday, November 10, 2014, Ivan Krutskikh <<a href="mailto:stein.hak@gmail.com">stein.hak@gmail.com</a>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> Thou this is not technically speaking a ipxe question, but I think this is<br>
>> an appropriate place to get some help with it.<br>
>><br>
>> So I am developing a Linux/Windows diskless boot system based on ipxe,<br>
>> zfsonlinux and python. Linux part works like a bliss with multiple distros,<br>
>> different hardware e.t.c.<br>
>><br>
>> At first I made some progress with windows 7 too, using pure cd-rom setup<br>
>> for single station ( a supposed to be a Microsoft supported scenario) and a<br>
>> ccboot client v2.0 for injecting multiple nic drivers for different<br>
>> hardware.<br>
>><br>
>> I used the same booting script for both:<br>
>> eg:<br>
>><br>
>> #!ipxe<br>
>><br>
>> set keep-san 1<br>
>> set netX/gateway 0.0.0.0<br>
>> sanboot iscsi:192.168.0.242:::1:iqn.2014-06.bootup.mtt:testinstall<br>
>><br>
>><br>
>> But after some time ( maybe some windows updates as well, hard to tell)<br>
>> the whole windows booting sequence broke and I cannot fix it or reproduce it<br>
>> with fresh install. All windows bootups end with hang windows logo followed<br>
>> by<br>
>> bsod 7e and a reboot. As far as I can tell, this is because windows<br>
>> couldn't find the driver for main hdd storage. ( basically, it is the lan<br>
>> driver + msicsi)<br>
>><br>
>> After some experiments with never ccboot versions, I tried a different<br>
>> approach based on <a href="http://ipxe.org/howto/winpe" target="_blank">http://ipxe.org/howto/winpe</a>. So I made a custom 3.0 winpe,<br>
>> booted it with ipxe script:<br>
>><br>
>> #!ipxe<br>
>><br>
>> set netX/gateway 0.0.0.0<br>
>> sanhook iscsi:192.168.0.242:::1:iqn.2014-06.bootup.mtt:testinstall<br>
>> kernel <a href="http://192.168.0.242:8080/boot/wimboot" target="_blank">http://192.168.0.242:8080/boot/wimboot</a><br>
>> initrd <a href="http://192.168.0.242:8080/media/bcd" target="_blank">http://192.168.0.242:8080/media/bcd</a> BCD<br>
>> initrd <a href="http://192.168.0.242:8080/media/boot.sdi" target="_blank">http://192.168.0.242:8080/media/boot.sdi</a> boot.sdi<br>
>> initrd <a href="http://192.168.0.242:8080/media/boot.wim" target="_blank">http://192.168.0.242:8080/media/boot.wim</a> boot.wim<br>
>> boot<br>
>><br>
>> My nic was perfectly recognized and configured, windows 7 setup was able<br>
>> to see my iscsi drive and installed windows just like it would on a local<br>
>> hdd. But after reboot- same old story. Bootup hangs, BSoD 7e. Tried<br>
>> launching a local VM from the same media, which was used to provide iscsi<br>
>> target- setup finished succesfull, new desktop welcomed me.<br>
>><br>
>> At this point I'm out of ideas. What differs installing windows by winpe<br>
>> to iscsi from the same scenario with cdrom? Not to mention there are a<br>
>> number of tutorials on the internet suggesting the second method for client<br>
>> provision.<br>
>><br>
>> What am I doing wrong here?<br>
>><br>
>> Thanks in advance.<br>
><br>
><br>
</div></div>> _______________________________________________<br>
> ipxe-devel mailing list<br>
> <a href="mailto:ipxe-devel@lists.ipxe.org">ipxe-devel@lists.ipxe.org</a><br>
> <a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a><br>
><br>
<br>
<br>
I had a problem a while ago that was resolved by using the iSCSI<br>
target (on the same L2 network) as the gateway<br>
<br>
Cheers<br>
</blockquote></div><br></div>