Jump to content











- - - - -

Windows 8 iSCSI boot fails after mandatory installation reboot

windows 8 iscsi networkboot

  • Please log in to reply
28 replies to this topic

#1 Guest_Matthias._*

Guest_Matthias._*
  • Guests

Posted 17 February 2013 - 05:34 PM

Hello Internet :)

 

We got a problem here, maybe you can solve it.

 

Here is what we did:

1. boot iPXE

2. attach iSCSI disk

3. boot WinPE4

4. install Win8 on SAN device through SMB-shared CD device

5. mandatory reboot while installing windows

6. boot iPXE

7. trying to boot from SAN device

8. nothing happens

 

Last messages:

Registerd SAN device 0x80

Booting from SAN device 0x80

 

 

Our setup:

8 identical computers (all having the same issues)

CPU Intel i7-2600k

VideoCard AMD/ATI Radeon HD 6800

Mainboard Gigabyte GA-H67MA-USB3-B3

with NIC Realtek RTL8111/8168 1Gbps

RAM 8GB

OnBoard-LAN boot ROM

iPXE

WinPE4

 

the Server:

DNSmasq as DHCP and DNS server

SCST as iSCSI target

TFTP-HPA as TFTP server

Samba3 as SMB server

 

 

How we already tried to fix it:

1. upgrade Win7 to win8 (same result after first reboot)

2. succesfully install Win8 on hdd, attach hdd to server, boot from hdd through iSCSI (fails at first boot)

3. replace NIC (same result after first reboot)

4. same procedure on other Computer (completely different HW) (Success!)

5. same procedure on VM (Success!)

6. use working VM image to boot through iSCSI (fails at first boot)

 

 

Now we need your help internet! Do your thing! :D



#2 drakein

drakein
  • Members
  • 2 posts
  •  
    United States

Posted 19 April 2013 - 01:50 PM

Try:

 

A. install the nic driver to the install.wim

B. on the 8 computers:

  1. install windows 7 or 8 to the local hardrive
  2. after completing the install and updating all the drivers sysprep the drive
  3. capture it to a wim
  4. retry the iscsi install using the captured wim with all the drivers.

  • Nuno Brito likes this

#3 Guest_Matthias._*

Guest_Matthias._*
  • Guests

Posted 02 May 2013 - 01:21 PM

thx for the response drakein. We already tried suggestion A. Unfortunately it didn't work, but we will give suggestion B a chance ;)



#4 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1974 posts
  • Location:Nantes - France
  •  
    France

Posted 03 May 2013 - 11:26 AM

Hi Mathias,

 

Works fine for me using the method described there : http://reboot.pro/to...r/#entry171734.

 

First boot goes to dvd (since iscsi target is blank), second boot goes to iscsi target (since freshly installed from previous boot).

 

Only difference is tha I use a dvd installation whereas you use a samba share but I dont think it makes a difference around boot on san.

 

Regards,

Erwan



#5 Guest_Matthias._*

Guest_Matthias._*
  • Guests

Posted 14 June 2013 - 07:38 PM

Hello again,

 

today we got the idea to update the BIOS. Now we no longer encounter the "San Device Problem". But unfortunately Win8 fails to boot with a BlueScreen (INACCESSIBLE_BOOT_DEVICE). After rebooting from Bluescreen the LAN MAC Address is set to 00:00:00:00:00:00 but this is fixed by turning the power supply off and back on after a few seconds.

So we managed to get a little further but we are suck again.

 

We also found out, that we can reproduce the old "San Device Problem" by setting the PCH SATA Mode to "AHCI". Maybe that was the problem all along and it got accidentially fixed by updating the BIOS and loading the optimized defaults. If it is set to "IDE" it works just fine until the BlueScreen appears.

 

Any ideas how we can fix the new problem?

 

Best regards

Matthias.



#6 biatche

biatche

    Member

  • Members
  • 86 posts
  •  
    Malaysia

Posted 23 August 2013 - 08:45 PM

Hi

 

I'm trying to do similar

 

1. boot iPXE (OK)

2. attach iSCSI disk (it registers fine)

3. boot w8pese / winpe4

4. install win7 via samba share

 

problem is the device never shows

:w8pese-iscsi
echo Booting W8pese-iscsi
set net0/gateway 0.0.0.0
set net0/keep-san 1
set gateway 0.0.0.0
set keep-san 1
sanhook --drive 0x80 --no-describe iscsi:192.168.3.9:tcp:3260:0:iqn.2003-01.org.linux-iscsi.mserv.x8664:sn.1b092703530c

#sanhook --drive 0x81 ${boot-url}/windows/w8pese/sources/w8pese.wim
kernel ${boot-url}/windows/wimboot
initrd ${boot-url}/windows/w8pese/boot/bootmgr bootmgr
initrd ${boot-url}/windows/w8pese/boot/bcd bcd
initrd ${boot-url}/windows/w8pese/boot/fonts/segmono_boot.ttf segmono_boot.ttf
initrd ${boot-url}/windows/w8pese/boot/fonts/segoe_slboot.ttf segoe_slboot.ttf
initrd ${boot-url}/windows/w8pese/boot/fonts/wgl4_boot.ttf wgl4_boot.ttf
initrd ${boot-url}/windows/w8pese/boot/boot.sdi boot.sdi
initrd ${boot-url}/windows/w8pese/sources/w8pese.wim w8pese.wim
boot || goto failed
goto start

without --no-describe it boots super slow and it doesnt seem like the disk gets attached

... if i were to attach the disk via microsoft iscsi initiator, it  complains about ibft during installation.

 

whats going on?



#7 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1974 posts
  • Location:Nantes - France
  •  
    France

Posted 23 August 2013 - 09:30 PM

Hi,

 

I would recomment to boot to windows dvd setup (after ipxe), not to winpe.

 

Regards,

Erwan



#8 biatche

biatche

    Member

  • Members
  • 86 posts
  •  
    Malaysia

Posted 23 August 2013 - 10:07 PM

Hi

 

Thanks for the reply.... but I absolutely need to use WinPE :(



#9 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1974 posts
  • Location:Nantes - France
  •  
    France

Posted 23 August 2013 - 11:48 PM

Then you need iscsi drivers in your winpe i would say.
Have a look at WinPE-StorageWMI winpe4 package.

#10 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1974 posts
  • Location:Nantes - France
  •  
    France

Posted 24 August 2013 - 11:41 AM

the following will add iscsi to your winpe4 image

Dism /mount-image /imagefile:g:\quickpe\x86\media\sources\boot.wim /index:1 /mountdir:g:\mnt
Dism /image:g:\mnt /add-package /packagepath:"C:\Program Files\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-WMI.cab" 
Dism /image:g:\mnt /add-package /packagepath:"C:\Program Files\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\en-us\winpe-WMI_en-us.cab" 
Dism /image:g:\mnt /add-package /packagepath:"C:\Program Files\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-StorageWMI.cab" 
Dism /image:g:\mnt /add-package /packagepath:"C:\Program Files\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\en-us\winpe-StorageWMI_en-us.cab" 
Dism /unmount-image /mountdir:g:\mnt /commit
 
then you can test
iscsicli QAddTargetPortal %ipaddress%
iscsicli QLoginTarget %TargetName%
 
before that, dont forget to start the iscsi service : 
net start msiscsi

 

Your method would then be :

1. boot iPXE

2. boot winpe4 over pxe

3. attach iscsi via command line

4. install win7 via samba share to iscsi disk (ensure target partition is set active)

 

Have fun,
Erwan


#11 biatche

biatche

    Member

  • Members
  • 86 posts
  •  
    Malaysia

Posted 24 August 2013 - 03:05 PM

http://w7pese.spam.net/Projects/Win7PESE/Components/IscsI.script

 

would you know if this is similar? only problem is that the iscsi service doesn't startup automatically

 

actually, using this, it's already installing windows... HOWEVER

 

for some reason:

 

WITH --no-describe, it's fast as usual but it complains about iBFT

WITHOUT --no-describe, it's ridiculously slow in starting up., it's also slow in doing all ?disk/network? related activity, one for sure is where it does the wpeinit network startup.... starting windows setup is super slow too.

 

anyway, speak of the devil... now while installing windows it just gave me:

 

"windows cannot install requried files. maek sure all files required for installation are available, and restart the installation. error code: 0x80070015"



#12 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1974 posts
  • Location:Nantes - France
  •  
    France

Posted 24 August 2013 - 04:35 PM

http://w7pese.cwcodes.net/Projects/Win7PESE/Components/IscsI.script

 

would you know if this is similar? only problem is that the iscsi service doesn't startup automatically

 

actually, using this, it's already installing windows... HOWEVER

 

for some reason:

 

WITH --no-describe, it's fast as usual but it complains about iBFT

WITHOUT --no-describe, it's ridiculously slow in starting up., it's also slow in doing all ?disk/network? related activity, one for sure is where it does the wpeinit network startup.... starting windows setup is super slow too.

 

anyway, speak of the devil... now while installing windows it just gave me:

 

"windows cannot install requried files. maek sure all files required for installation are available, and restart the installation. error code: 0x80070015"

 

At first look, yes the script you refer to seems to install iscsi initiator just like the winpe4 package I mentionned does.

 

MSISCSI service not starting up auto can be fixed easily in the boot.wim (or handled by a batch).

 

Still, if you go with the winpe4 package, you need to review your method which then should be :

1. boot iPXE (withtout the need of sanhook)
2. boot winpe4 over pxe (using wimboot or memdisk)
3. attach iscsi via command line from within winpe (you can even write a batch for this)
4. install win7 via samba share to iscsi disk

You can use quickpe to create the proper winpe4 iso.

 

Regards,

Erwan



#13 biatche

biatche

    Member

  • Members
  • 86 posts
  •  
    Malaysia

Posted 24 August 2013 - 05:44 PM

im unable to edit the post, the error msg was due to the target server getting a kernel panic..... for some reason..



#14 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1974 posts
  • Location:Nantes - France
  •  
    France

Posted 24 August 2013 - 06:14 PM

im unable to edit the post, the error msg was due to the target server getting a kernel panic..... for some reason..

 

so it does work?

can you sum up the method you used?



#15 biatche

biatche

    Member

  • Members
  • 86 posts
  •  
    Malaysia

Posted 24 August 2013 - 06:35 PM

Not entirely....

set netX/keep-san 1
sanhook iscsi:192.168.3.9:tcp:3260:0:iqn.2013-08.lan.mserv:test2

This is as simple as it gets....however within winpe its ridiculously slow... my mapped network drive is unresponsive except once.. not sure how and why..

 

so nothings fixed until network shares works properly

 

its getting frustrating :(

 

There anything necessary to set on the DHCP server? im using dnsmasq..


Edited by biatche, 24 August 2013 - 06:40 PM.


#16 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1974 posts
  • Location:Nantes - France
  •  
    France

Posted 24 August 2013 - 09:50 PM

you can also try the below ipxe script

 

#!ipxe
set net0/gateway 0.0.0.0
set net0/keep-san 1
set gateway 0.0.0.0
set keep-san 1
set initiator-iqn iqn.2008-08.com.starwindsoftware:test
sanhook --drive 0x81 iscsi:192.168.1.100:tcp:3260:0:iqn.2008-08.com.starwindsoftware:test
sanboot --no-describe --drive 0x80 ${boot-url}/images/winre.iso
 
In winpe4 (without any specific customisation), i can mount win8 over the network, launch the install and get to the point where I see my iscsi disk.
 
Regards,
Erwan


#17 biatche

biatche

    Member

  • Members
  • 86 posts
  •  
    Malaysia

Posted 24 August 2013 - 09:54 PM

I'm using w8pese, at this stage, after all the trouble, I'll assume somethings not right with w8pese, so you recommend that I give your QuickPE a go?

 

Does the DHCP server require any special config? (I'm on dnsmasq)


Edited by biatche, 24 August 2013 - 09:56 PM.


#18 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1974 posts
  • Location:Nantes - France
  •  
    France

Posted 24 August 2013 - 10:36 PM

My dhcp server runs under windows and does not have any specific config.

 

Using QuickPE, you should be able to generate a winpe4 in a clean and quick way.

You'll need MS ADK to be installed.

 

If you dont have MS ADK installed, QuickPE can use a windows 8 dvd or iso as source.



#19 biatche

biatche

    Member

  • Members
  • 86 posts
  •  
    Malaysia

Posted 25 August 2013 - 06:47 AM

Sorry but QuickPE is meant only for x86? I can't get it to even begin as it complains about copype missing, I don't see the file anyway.



#20 biatche

biatche

    Member

  • Members
  • 86 posts
  •  
    Malaysia

Posted 25 August 2013 - 10:06 AM

OK there's some progress with my setup, for some reason although sluggish, i managed to succeed the first phase of the installation which is to say, running windows setup, and copying/expanding to disk... and as you know, after this part, it has to reboot

 

here's where trouble begins

set netX/keep-san 1
sanboot iscsi:192.168.3.9:tcp:3260:0:iqn.2013-08.lan.mserv:test2
boot

with this, it gives me windows boot manager

 

e1e6032e.sys

status: 0xc0000428

info: windows cannot verify the digital signature of this file.

 

that appears to be the driver for my intel nic, which is the latest  version -- 18.5

 

why does this happen? when installing to physical disk, it's fine.



#21 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1974 posts
  • Location:Nantes - France
  •  
    France

Posted 25 August 2013 - 10:44 AM

Sorry but QuickPE is meant only for x86? I can't get it to even begin as it complains about copype missing, I don't see the file anyway.

 

QuickPE will run on x86 or x64 but will generate x86 winpe4 only.

It should not be a problem for your scenario, right?



#22 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1974 posts
  • Location:Nantes - France
  •  
    France

Posted 25 August 2013 - 10:46 AM

OK there's some progress with my setup, for some reason although sluggish, i managed to succeed the first phase of the installation which is to say, running windows setup, and copying/expanding to disk... and as you know, after this part, it has to reboot

 

here's where trouble begins

set netX/keep-san 1
sanboot iscsi:192.168.3.9:tcp:3260:0:iqn.2013-08.lan.mserv:test2
boot

with this, it gives me windows boot manager

 

e1e6032e.sys

status: 0xc0000428

info: windows cannot verify the digital signature of this file.

 

that appears to be the driver for my intel nic, which is the latest  version -- 18.5

 

why does this happen? when installing to physical disk, it's fine.

 

see my previous post, stick to x86 winpe4 to avoid issues with x64 drivers not being signed.



#23 biatche

biatche

    Member

  • Members
  • 86 posts
  •  
    Malaysia

Posted 25 August 2013 - 11:22 AM

I need to install win7 x64... i've been doing so all along using w8pese (x64) just that, all along ive been installing to local physical drives, but just this time im trying to install to iscsi.

 

To understand better:

 

1. Boot to WinPE (OK, although slow)

2. Run windows 7 x64 setup (OK, very slow to enter disk management screen)

3. Stage 1 windows installation (fast, as normal)

4. Reboots, now to set boot device to the iscsi disk. It gives me this digital signature error.


Edited by biatche, 25 August 2013 - 11:28 AM.


#24 erwan.l

erwan.l

    Gold Member

  • Developer
  • 1974 posts
  • Location:Nantes - France
  •  
    France

Posted 26 August 2013 - 07:07 PM

about my proposed method in post 12

1. boot iPXE (withtout the need of sanhook)
2. boot winpe4 over pxe (using wimboot or memdisk)
3. attach iscsi via command line from within winpe (you can even write a batch for this)
4. install win7 via samba share to iscsi disk

Forget it, this is wrong.

Although winpe4 and the windows setup will see the iscsi disk, the windows setup will complain about the iscsi disk not being a net boot disk.

 

Also, the sanhook+sanboot method fails on me.

This time, the windows setup will see the iscsi disk but it will complain about that disk controller not existing in the bios :(

 

And bad luck, sanhook+wimboot winpe4 does not work either :(  

Always get "Ensure that the disk's controller is enabled in the computer's BIOS menu".

 

I flashed the latest bios and also tried AHCI or Compatible mode in my bios setting without luck.



#25 biatche

biatche

    Member

  • Members
  • 86 posts
  •  
    Malaysia

Posted 26 August 2013 - 07:34 PM

using the same setup, w8pese gave me a lot of issues while my old win7pese works fine. windows is now up and running...

 

ive NO idea why w8pese does that tho







Also tagged with one or more of these keywords: windows 8, iscsi, networkboot

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users