No drives available while booting

[myme3project@gmail.com]

Hello Team,

I'm trying to use Synology NAS in place of WDS server.
I'm trying to boot Windows 10 .wim file.
I'm new to this technology and have tried many things to get this thing working.
However, I'm stuck at a step. Please help me out with this.
Everything goes fine and the Windows installation page appears, but after that it asks to Select a Driver and no Drives are shown. But when I click on browse, it is showing me Documents, Downloads etc.
I've followed http://ipxe.org/wimboot and http://reboot.pro/topic/20166-wimboot-fr...nux-setup/
I'm using pxelinux.0
The configuration I'm using is shown below.

#Default
DEFAULT menu.c32

PROMPT 0

NOESCAPE 0

ALLOWOPTIONS 0

MENU BACKGROUND testback.jpg

# Timeout in units of 1/10 s

TIMEOUT 300

#MENU WIDTH 40

#MENU MARGIN 0

MENU ROWS 12

MENU TIMEOUTROW 14

MENU HSHIFT 5

MENU VSHIFT 2

MENU COLOR BORDER 30;44 #00000000 #00000000 none

MENU COLOR TABMSG 1;36;44 #00000000 #00000000 none

#MENU COLOR TITLE 1;36;44 #00000000 #00000000 none

MENU COLOR SEL 30;47 #40000000 #20ffffff



MENU TITLE MAQ Software

MENU WIDTH 80

MENU MARGIN 18



LABEL local

MENU DEFAULT

MENU LABEL Boot from Harddisk

LOCALBOOT 0

LABEL IPXE.lKRN
MENU label Windows 10
KERNEL ipxe.lkrn
initrd wimboot.ipxe

where wimboot.ipxe is

#!ipxe
dhcp net0 && echo IP address: ${net0/ip} ; echo Subnet mask: ${net0/netmask}
kernel wimboot
initrd bootmgr bootmgr
initrd efi/boot/bootx64.efi bootx64.efi
initrd boot/bcd bcd
initrd boot/boot.sdi boot.sdi
initrd sources/boot.wim boot.wim

And moreover this thing works only in Legacy boot not in UEFI.
I would like to boot using UEFI.

Thank you in advance

[NiKiZe]

(2016-11-30 12:13)myme3project@gmail.com Wrote:  Hello Team,

I'm trying to use Synology NAS in place of WDS server.
I'm trying to boot Windows 10 .wim file.
I'm new to this technology and have tried many things to get this thing working.
However, I'm stuck at a step. Please help me out with this.
Everything goes fine and the Windows installation page appears, but after that it asks to Select a Driver and no Drives are shown. But when I click on browse, it is showing me Documents, Downloads etc.
I've followed http://ipxe.org/wimboot and http://reboot.pro/topic/20166-wimboot-fr...nux-setup/
I'm using pxelinux.0
The configuration I'm using is shown below.

....

LABEL IPXE.lKRN
MENU label Windows 10
KERNEL ipxe.lkrn
initrd wimboot.ipxe

where wimboot.ipxe is

#!ipxe
dhcp net0 && echo IP address: ${net0/ip} ; echo Subnet mask: ${net0/netmask}
kernel wimboot
initrd bootmgr bootmgr
initrd efi/boot/bootx64.efi bootx64.efi
initrd boot/bcd bcd
initrd boot/boot.sdi boot.sdi
initrd sources/boot.wim boot.wim

And moreover this thing works only in Legacy boot not in UEFI.
I would like to boot using UEFI.

Thank you in advance

Do you get any error or what happens? what is the issue?

I would strongly encourage you to not use pxelinux and instead load ipxe directly. for legacy this can be done by using undionly.kpxe, you will then want to read http://ipxe.org/howto/chainloading#break...inite_loop
If you decide to use your dhcp server to break the loop you will want to remove the dhcp command from your script.
The alternative to doing this on the DHCP server is to instead embed the script in the ipxe binary, this is explained at the above link.

about your script for wimboot, first you should not need to specify any of the bootmgr options, and it seems you are missing the boot command in the file.

Code:

#!ipxe
dhcp
echo IP address: ${netX/ip}
echo Subnet mask: ${netX/netmask}
kernel wimboot gui pause
initrd boot/bcd bcd
initrd boot/boot.sdi boot.sdi
initrd sources/boot.wim boot.wim
boot

So the changes are:
* let dhcp command auto detected devices.
* use netX instead of net0 so the last found device is used.
* add gui and pause options to wimboot
* remove bootmgr and bootx64 files
* add boot command at the end
One other thing you might want to change is to use absolute http based paths instead, such as
kernel http://server/ipxe/wimboot gui pause
instead.

I would recommend that you get this working in legacy bios mode first.
When you have that going you can look into adding ipxe.efi or snponly.efi to your dhcp server instead, and when you have that it might actually just work.

[myme3project@gmail.com]

(2016-11-30 20:15)NiKiZe Wrote:  

(2016-11-30 12:13)myme3project@gmail.com Wrote:  Hello Team,

I'm trying to use Synology NAS in place of WDS server.
I'm trying to boot Windows 10 .wim file.
I'm new to this technology and have tried many things to get this thing working.
However, I'm stuck at a step. Please help me out with this.
Everything goes fine and the Windows installation page appears, but after that it asks to Select a Driver and no Drives are shown. But when I click on browse, it is showing me Documents, Downloads etc.
I've followed http://ipxe.org/wimboot and http://reboot.pro/topic/20166-wimboot-fr...nux-setup/
I'm using pxelinux.0
The configuration I'm using is shown below.

....

LABEL IPXE.lKRN
MENU label Windows 10
KERNEL ipxe.lkrn
initrd wimboot.ipxe

where wimboot.ipxe is

#!ipxe
dhcp net0 && echo IP address: ${net0/ip} ; echo Subnet mask: ${net0/netmask}
kernel wimboot
initrd bootmgr bootmgr
initrd efi/boot/bootx64.efi bootx64.efi
initrd boot/bcd bcd
initrd boot/boot.sdi boot.sdi
initrd sources/boot.wim boot.wim

And moreover this thing works only in Legacy boot not in UEFI.
I would like to boot using UEFI.

Thank you in advance

Do you get any error or what happens? what is the issue?

I would strongly encourage you to not use pxelinux and instead load ipxe directly. for legacy this can be done by using undionly.kpxe, you will then want to read http://ipxe.org/howto/chainloading#break...inite_loop
If you decide to use your dhcp server to break the loop you will want to remove the dhcp command from your script.
The alternative to doing this on the DHCP server is to instead embed the script in the ipxe binary, this is explained at the above link.

about your script for wimboot, first you should not need to specify any of the bootmgr options, and it seems you are missing the boot command in the file.

Code:

#!ipxe
dhcp
echo IP address: ${netX/ip}
echo Subnet mask: ${netX/netmask}
kernel wimboot gui pause
initrd boot/bcd bcd
initrd boot/boot.sdi boot.sdi
initrd sources/boot.wim boot.wim
boot

So the changes are:
* let dhcp command auto detected devices.
* use netX instead of net0 so the last found device is used.
* add gui and pause options to wimboot
* remove bootmgr and bootx64 files
* add boot command at the end
One other thing you might want to change is to use absolute http based paths instead, such as
kernel http://server/ipxe/wimboot gui pause
instead.

I would recommend that you get this working in legacy bios mode first.
When you have that going you can look into adding ipxe.efi or snponly.efi to your dhcp server instead, and when you have that it might actually just work.

I tried your suggestions, however it is still not showing the drives option.
http://ipxe.org/wimboot
I'm able to get the 'Install Windows' screen.
After it gives a window to select the drives and there are no drives listed.
Please open the link to see the error.
https://drive.google.com/file/d/0BwQzmvt...sp=sharing
If possible please send a document with the configuration.

Thank you

[NiKiZe]

Are you using the default boot.wim? have you pressed Shift+F10, mounted the NAS and started setup.exe from there? (what you see can be due to that install.wim is not found)

the mount command is something like
net mount * \\nasname\share
this will mount a driver letter that you can go to and start setup.exe (in the same path as you install.wim) "again" and hopefully that will work.