iPXE discussion forum
Windows 10 (1804) installation on iscsi device - Printable Version

+- iPXE discussion forum (https://forum.ipxe.org)
+-- Forum: iPXE user forums (/forumdisplay.php?fid=1)
+--- Forum: General (/forumdisplay.php?fid=2)
+--- Thread: Windows 10 (1804) installation on iscsi device (/showthread.php?tid=12905)

Windows 10 (1804) installation on iscsi device - scratchy - 2018-09-03 02:24

Hello,

im trieing since days(!) to get windows installation running on an iscsi target.


basicly what i followed this tutorial: "http://it-joe.com/windows/iscsi_pxe_boot" but also googlet a lot and tried different things.

Im running into the same problem as "poekel"

Quote:Hi,
I earlier stated that i had problems that had to do with -> Windows cannot be installed on this disk
I have solved that.......
Win 10 installs on the iscsi target but at the end i get a message that some MANDATORY driver CANNOT be INSTALLED

What i tried so far is quoted here:
Quote:To be honest im out of idears. I successfully installed windows 8, with this tutorial which worked out like a charm.

I upgraded those version 8 to 10 and it complained about a not signed driver (prob. the ethernet driver) and was not booting anymore (if i remember right) prob this is the whole issue whats it about?

I also tried other things like:
- Use another software as iscsi server - didnt helped

- Tried different versions of Windows 10 (1803,1706,1606) including their specifig WAIKs - didned helped

- Used physical Hardware / Different Virtualisations Software (Virtualbox/VMware) - didnt helped
- Attached a disk during installation but installed it to iscsi - didndt helped

- Modified ipxe to support only "undionly" -> didnt helped

- Tried to patch windowsPE (any version) with iscsicpl -> didnt get it running (?) maybe helps to connect it manual instead with ipxe do get the proper driver installed (?)

- Tried to attach different Hardware Nics -> didnt get it running

- Tried to install it with the same env on a local disk -> worked -> but didnt helped to solve this issue

- Tried to install windows 7 -> didnt worked because of missing signed driver

- Tried different versions of "wimload" -> either doesnt helped or doesnt started winPE

Do you have further idears maybe? I have on my list maybe to use EFI no clue if this helps out..


Can anybody help me out with this issue or does have any idear whats going on?

Edit:

Figured out more:

If im using a Virtualbox Client and attach the disk via iscsi there (yeah thats possible, but only through cli), im able to install windows 10 without problems.
Later when i remove the iscsi from virtualbox and boot it 'normally' (still virtualbox as hypervisor but sanboot as ipxe feature) its booting from the network.

So somehow the Installer is maybe broken to let me install my things? Sad

RE: Windows 10 (1804) installation on iscsi device - NiKiZe - 2018-09-03 18:03

The link you are pointing to does the horrible thing of setting up an winpe iso that is booted via sanboot, there is much better tools for that - wimboot.

You have written on IRC - and I can respond there to try and help you - but it won't do much good if you leave the channel.

If instead what you want to do is install from a booted winpe - onto a iSCSI target that is a different matter that have had many getting gray hairs.
There have not been any (usefull) information given about what your environment is; (we need one specific case that we can work with, and the circumstances in that case, not mixed with anything else)
* What is the NIC you are using?
* Have you modified the winpe in any way (especially added drivers)
* Are the winpe from the same source as the installation files you are using?

After reading over what you have written once again, I'm quite sure that what you are seeing is the windows setup application starting and is unable to find any installation media.
What you have to do (and which is described on that site) is to open a prompt (press shfit+f10) and run wpeinit etc as described in http://forum.ipxe.org/showthread.php?tid=7059&pid=13472#pid13472 and then you will have to mount a installation share.

I don't think anyone have or will be able to get a pure windows iso to sanboot and be available as an installation media, the reason being that network needs to be started properly before any iSCSI devices will be detected.

a few other notes:
* don't use set keep-san 1 - legacy and not needed
* don't use syslinux, iPXE should be able to do everything on it's own
* don't use memdisk - if you are than that probably explains your issues even more.

If nothing of this helps then post exact configuration, including NIC etc with pciid as described above, as well as iPXE scripts that you are using, a link to image with the screen that you are seeing with the error message. - The goal with the description should be that anyone can recreate your exact scenario, that way more people can reproduce and help you find a solution.

RE: Windows 10 (1804) installation on iscsi device - scratchy - 2018-09-03 18:26

(2018-09-03 18:03)NiKiZe Wrote:  The link you are pointing to does the horrible thing of setting up an winpe iso that is booted via sanboot, there is much better tools for that - wimboot.

Sorry about that i also for sure tried out the wimboot method, from http://ipxe.org/wimboot. This didnt do a difference

(2018-09-03 18:03)NiKiZe Wrote:  You have written on IRC - and I can respond there to try and help you - but it won't do much good if you leave the channel.

I restarted my computer for pxe testing purposes sorry about that

(2018-09-03 18:03)NiKiZe Wrote:  If instead what you want to do is install from a booted winpe - onto a iSCSI target that is a different matter that have had many getting gray hairs.

i dont get this part sorry?

(2018-09-03 18:03)NiKiZe Wrote:  * What is the NIC you are using?

Virtualbox default NIC (virtual client) Intel PRO/1000 MT Desktop (82540OEM) / Intel V82579V / Different realteks on physically hardware

(2018-09-03 18:03)NiKiZe Wrote:  * Have you modified the winpe in any way (especially added drivers)

Tried both, vanilla winPE as well as different scripts for example one which i copy and pasted together ( https://pastebin.com/SLdSpc1p ) for adding iscsicpl stuff (i think stuff like this is outdated since a long time)? I didnt touched drivers in WinPE.

(2018-09-03 18:03)NiKiZe Wrote:  * Are the winpe from the same source as the installation files you are using?

Yes as WINPE was always matching the iso which im installing. Tried here 1803,1706,1607

(2018-09-03 18:03)NiKiZe Wrote:  After reading over what you have written once again, I'm quite sure that what you are seeing is the windows setup application starting and is unable to find any installation media.

Thats sadly wrong, i see the windows setup, as well as the installation media also the windows setup copys data over but the last step (!) shortly before the reboot fails with the mantadory driver error message (will attach a screen soon)

(2018-09-03 18:03)NiKiZe Wrote:  What you have to do (and which is described on that site) is to open a prompt (press shfit+f10) and run wpeinit etc as described in http://forum.ipxe.org/showthread.php?tid=7059&pid=13472#pid13472 and then you will have to mount a installation share.

I don't think anyone have or will be able to get a pure windows iso to sanboot and be available as an installation media, the reason being that network needs to be started properly before any iSCSI devices will be detected.


(2018-09-03 18:03)NiKiZe Wrote:  a few other notes:
* don't use set keep-san 1 - legacy and not needed
* don't use syslinux, iPXE should be able to do everything on it's own
* don't use memdisk - if you are than that probably explains your issues even more.

All three things i already figured out today, replaced syslinux (menu management is possible with ipxe as well), memdisk was replaced by wimboot and keep-san i wasnt sure, but if you say i can remove it ill do.

(2018-09-03 18:03)NiKiZe Wrote:  If nothing of this helps then post exact configuration, including NIC etc with pciid as described above, as well as iPXE scripts that you are using, a link to image with the screen that you are seeing with the error message. - The goal with the description should be that anyone can recreate your exact scenario, that way more people can reproduce and help you find a solution.


Heres my windows-10-installation section

Code:
:win-10
sanhook --drive 0x80 ${ISCSI_FULL_URL_WIN10}
kernel ${boot-url}/distros/tools/wimboot-2.6.0/wimboot

initrd ${boot-url}/distros/windows/winpe/startup/10/1803/install.bat                                install.bat
initrd ${boot-url}/distros/windows/winpe/startup/winpeshl.ini                                winpeshl.ini
#initrd ${boot-url}/distros/windows/winpe/WinPE_amd64_1803/media/bootmgr                      bootmgr
#initrd ${boot-url}/distros/windows/winpe/WinPE_amd64_1803/media/EFI/Boot/bootx64.efi          bootx64.efi

initrd ${boot-url}/distros/windows/winpe/WinPE_amd64_1803/media/Boot/BCD                     BCD
initrd ${boot-url}/distros/windows/winpe/WinPE_amd64_1803/media/Boot/boot.sdi                boot.sdi
initrd ${boot-url}/distros/windows/winpe/WinPE_amd64_1803/media/sources/boot.wim             boot.wim
boot

[Image: errormessage.png?dl=1]

[Image: fail.png?dl=1]

RE: Windows 10 (1804) installation on iscsi device - scratchy - 2018-10-03 22:47

tested 1809 still the same issue

but at least i have more output now i guess:

heres a log.. any idears how to solve it / if it brings me forward?

Code:
[Device Install Log]
     OS Version = 10.0.17134
     Service Pack = 0.0
     Suite = 0x0110
     ProductType = 1
     Architecture = amd64

[BeginLog]

[Boot Session: 2018/09/03 19:32:46.495]

>>>  [Device Install (DiInstallDevice) - PCI\VEN_8086&DEV_100E&SUBSYS_001E8086&REV_02\3&267A616A&0&18]
>>>  Section start 2018/09/03 19:35:01.202
      cmd: wpeinit
     ndv: Flags: 0x00000002
     dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
     sto: {Setup Import Driver Package: X:\windows\INF\nete1g3e.inf} 19:35:01.202
     sto:      Driver package already imported as 'nete1g3e.inf'.
!    inf:      Needed section [PciIoSpaceNotRequired] found in included INF "pci.inf", not referenced from [E1027.Hw]. Code = 1313, Line = 481
!    inf:      Needed section [PciIoSpaceNotRequired] found in included INF "pci.inf", not referenced from [E1079.Hw]. Code = 1313, Line = 555
!    inf:      Needed section [PciIoSpaceNotRequired] found in included INF "pci.inf", not referenced from [E107A.Hw]. Code = 1313, Line = 576
!    inf:      Needed section [PciIoSpaceNotRequired] found in included INF "pci.inf", not referenced from [E10B5.Hw]. Code = 1313, Line = 650
     sto: {Setup Import Driver Package - exit (0x00000000)} 19:35:01.220
     dvi: Searching for hardware ID(s):
     dvi:      pci\ven_8086&dev_100e&subsys_001e8086&rev_02
     dvi:      pci\ven_8086&dev_100e&subsys_001e8086
     dvi:      pci\ven_8086&dev_100e&cc_020000
     dvi:      pci\ven_8086&dev_100e&cc_0200
     dvi: Searching for compatible ID(s):
     dvi:      pci\ven_8086&dev_100e&rev_02
     dvi:      pci\ven_8086&dev_100e
     dvi:      pci\ven_8086&cc_020000
     dvi:      pci\ven_8086&cc_0200
     dvi:      pci\ven_8086
     dvi:      pci\cc_020000
     dvi:      pci\cc_0200
     dvi: Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
     dvi: {Plug and Play Service: Device Install for PCI\VEN_8086&DEV_100E&SUBSYS_001E8086&REV_02\3&267A616A&0&18}
     dvi:      Driver INF Path: X:\windows\INF\nete1g3e.inf
     dvi:      Driver Node Name: nete1g3e.inf:5f63e53407038284:E100ECopper:8.4.13.0:pci\ven_8086&dev_100e&subsys_001e8086,
     dvi:      Driver Store Path: X:\windows\System32\DriverStore\FileRepository\nete1g3e.inf_amd64_af58b4e19562a3​f9\nete1g3e.inf
     dvi:      Searching for hardware ID(s):
     dvi:           pci\ven_8086&dev_100e&subsys_001e8086&rev_02
     dvi:           pci\ven_8086&dev_100e&subsys_001e8086
     dvi:           pci\ven_8086&dev_100e&cc_020000
     dvi:           pci\ven_8086&dev_100e&cc_0200
     dvi:      Searching for compatible ID(s):
     dvi:           pci\ven_8086&dev_100e&rev_02
     dvi:           pci\ven_8086&dev_100e
     dvi:           pci\ven_8086&cc_020000
     dvi:           pci\ven_8086&cc_0200
     dvi:           pci\ven_8086
     dvi:           pci\cc_020000
     dvi:           pci\cc_0200
     dvi:      Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
     dvi:      {Core Device Install} 19:35:01.256
     dvi:           {Install Device - PCI\VEN_8086&DEV_100E&SUBSYS_001E8086&REV_02\3&267A616A&0&18} 19:35:01.273
     dvi:                Device Status: 0x01802400, Problem: 0x12 (0xc0000493)
     dvi:                Parent device: ACPI\PNP0A03\0
     dvi:                {Configure Device - PCI\VEN_8086&DEV_100E&SUBSYS_001E8086&REV_02\3&267A616A&0&18} 19:35:01.273
     dvi:                     Device Status: 0x01802400, Problem: 0x12 (0xc0000493)
     dvi:                     Parent device: ACPI\PNP0A03\0
     sto:                     {Configure Driver Package: X:\windows\System32\DriverStore\FileRepository\nete1g3e.inf_amd64_af58b4e19562a3​f9\nete1g3e.inf}
     sto:                          Source Filter  = pci\ven_8086&dev_100e&subsys_001e8086
     inf:                          Class GUID     = {4d36e972-e325-11ce-bfc1-08002be10318}
     inf:                          Class Options  = Configurable
     inf:                          {Configure Driver: Intel(R) PRO/1000 MT Desktop Adapter}
     inf:                               Section Name = E100ECopper
     inf:                               {Add Service: E1G60}
     inf:                                    Start Type    = 3
     inf:                                    Service Type  = 1
     inf:                                    Error Control = 1
     inf:                                    Image Path    = \SystemRoot\System32\drivers\E1G6032E.sys
     inf:                                    Display Name  = Intel(R) PRO/1000 NDIS 6 Adapter Driver
     inf:                                    Group         = NDIS
     inf:                                    Created new service 'E1G60'.
     inf:                               {Add Service: exit(0x00000000)}
     inf:                               Hardware Id  = PCI\VEN_8086&DEV_100E&SUBSYS_001E8086
     inf:                               {Configure Driver Configuration: E100ECopper}
     inf:                                    Service Name  = E1G60
     inf:                                    Config Flags  = 0x00000000
     inf:                               {Configure Driver Configuration: exit(0x00000000)}
     inf:                          {Configure Driver: exit(0x00000000)}
!    inf:                          Needed section [PciIoSpaceNotRequired] found in included INF "pci.inf", not referenced from [E1027.Hw]. Code = 1313, Line = 481
!    inf:                          Needed section [PciIoSpaceNotRequired] found in included INF "pci.inf", not referenced from [E1079.Hw]. Code = 1313, Line = 555
!    inf:                          Needed section [PciIoSpaceNotRequired] found in included INF "pci.inf", not referenced from [E107A.Hw]. Code = 1313, Line = 576
!    inf:                          Needed section [PciIoSpaceNotRequired] found in included INF "pci.inf", not referenced from [E10B5.Hw]. Code = 1313, Line = 650
     flq:                          Hardlinking 'X:\windows\System32\DriverStore\FileRepository\nete1g3e.inf_amd64_af58b4e19562a​3f9\E1G6032E.sys' to 'X:\windows\System32\drivers\E1G6032E.sys'.
!    flq:                          HardLink: 'X:\windows\System32\DriverStore\FileRepository\nete1g3e.inf_amd64_af58b4e19562a​3f9\E1G6032E.sys' to 'X:\windows\System32\drivers\E1G6032E.sys' FAILED
!    flq:                          Error 1: Incorrect function.
     dvi:                          Existing files modified, may need to restart related services.
     sto:                     {Configure Driver Package: exit(0x00000bc3)}
     dvi:                     Restart required for any devices using this driver.
     dvi:                     Install Device: Configuring device (nete1g3e.inf:pci\ven_8086&dev_100e&subsys_001e8086,E100ECopper). 19:35:01.332
     dvi:                     Install Device: Configuring device completed. 19:35:01.348
     dvi:                     Device Status: 0x01802000, Problem: 0x0 (0x00000000)
     dvi:                     {Restarting Devices} 19:35:01.348
     dvi:                          Start: PCI\VEN_8086&DEV_100E&SUBSYS_001E8086&REV_02\3&267A616A&0&18
!    dvi:                          Device pending start: Device has problem: 0x38 (CM_PROB_NEED_CLASS_CONFIG), problem status: 0x00000000.
     dvi:                     {Restarting Devices exit} 19:35:01.395
     dvi:                {Configure Device - exit(0x00000000)} 19:35:01.395
     dvi:                Device Status: 0x01802400, Problem: 0x38
     dvi:           {Install Device - exit(0x00000000)} 19:35:01.395
     dvi:      {Core Device Install - exit(0x00000000)} 19:35:01.395
     dvi:      Waiting for device post-install to complete. 19:35:01.395
     dvi:      Device post-install completed. 19:35:01.514
     ump: {Plug and Play Service: Device Install exit(00000000)}
<<<  Section end 2018/09/03 19:35:01.536
<<<  [Exit status: SUCCESS]


>>>  [Delete Device - STORAGE\VOLUME\{30C55B78-AFF3-11E8-BBFE-0800275D3201}#0000000022600000]
>>>  Section start 2018/09/03 19:47:30.820
      cmd: X:\windows\System32\vds.exe
<<<  Section end 2018/09/03 19:47:30.840
<<<  [Exit status: SUCCESS]


>>>  [Delete Device - STORAGE\VOLUME\{30C55B78-AFF3-11E8-BBFE-0800275D3201}#0000000000100000]
>>>  Section start 2018/09/03 19:47:32.925
      cmd: X:\windows\System32\vds.exe
<<<  Section end 2018/09/03 19:47:32.939
<<<  [Exit status: SUCCESS]


RE: Windows 10 (1804) installation on iscsi device - scratchy - 2018-10-10 10:35

Am i here alone in this forum? is it working for everybody else flawless?

I dont get what im doing wrong since it looks for me like a common use case?!

RE: Windows 10 (1804) installation on iscsi device - 62maxime - 2019-01-09 23:58

Hi scratchy,

I'm in the same situation as yourself. Do you have any leads on the bug ? Have you find some alternative to make it working ?

Thanks,
Maxime

RE: Windows 10 (1804) installation on iscsi device - scratchy - 2019-02-15 11:13

i gave up Sad

RE: Windows 10 (1804) installation on iscsi device - scan80269 - 2019-02-16 19:20

@scratchy,

It looks to me that a proper driver for your NIC needs to be added (injected) to the boot.wim for booting via wimboot.

I've been successful installing Win10 1803 (RS4) and 1809 (RS5) into iSCSI disks by booting the client into WinPE first. I injected Intel & Realtek NIC drivers into the WinPE boot.wim to support a variety of motherboards. I did the same for the OS installation install.wim, for the Pro edition of Win10 that I want to install. A small iSCSI disk carrying the OS install files (including the driver-augmented install.wim) is mounted (sanhook) to support OS installation and removes the need to plug a USB flash drive into the PC.

The boot.wim from Windows installation media has two images. The first image supports OS installation after bootup from the media, the second is a more traditional WinPE image. Your NIC driver needs to be injected into the first image. For over-the-network OS installation into iSCSI disk, the NIC driver is boot critical, so unless there is already an inbox NIC driver in the Windows installation files supporting your NIC, it is necessary to inject the proper NIC driver into boot.wim.

I prefer to network boot the PC into WinPE first, to give me some control over the OS installation process. I can check for proper iSCSI disk mounts via iscsicpl (also injected into WinPE), or run diskpart to clean the mounted iSCSI disk in preparation for OS installation, unbind ms_wfplwf_lower & ms_wfplwf_upper protocols (if enabled) from the NIC, etc.

RE: Windows 10 (1804) installation on iscsi device - 62maxime - 2019-02-27 00:07

Hi scan80269 and scratchy,

After a call with Microsoft, we did find a solution. The problem that I have was that I've used a French media for the installation of Windows. After trying with the English media, the installation ends successfully. I've noticed that the error message is in Deutsch in your case so maybe the problem occurs also in the Deutsch media.

Tell me if it helps !
Best regards.