Unsolved Could not start download
-
Hello
I followed george1421 tutorial of booting an iso of windows 10
https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-imagesI can get in the FOG menu but when i select windows 10 it says
could not start download operation not suported
The version of fog i use is 1.5.0
-
@george1421 Oke! Say it when you found something.
-
@janspook I’m going to test this today. The 1.4.4 iPXE kernels should work correctly. The instructions were created using 1.4.4.
-
@tom-elliott
When will 1.5.1 be released because i have 2 weeks to roll it out. -
Sorry I posted this originally in the wrong thread, too much reading I guess.
I’ve updated the ipxe files to use be built with FTP and NFS. These files will be in 1.5.1, and are currently in the working-1.5.1 branch of github repository.
-
This post is deleted! -
@janspook I was just looking at the config files for iPXE issued by fog for another ticket and I found the NFS code has been turned off.
https://github.com/FOGProject/fogproject/blob/master/src/ipxe/src/config/general.h
Line #60. So that IS why the NFS protocol doesn’t work in the tutorial. The iPXE kernels I sent you should address the issue in the short term.
-
@george1421 I found this https://tinkerboarding.co.uk/wiki/index.php?title=PXE-boot
I will test it tomorrow.
-
@janspook said in Could not start download:
Using the default one
Not helpful. Its like me asking you if you like coffee or tea, and you responding “yes”. Just kidding.
Look at the FOG chat bubble, I’ll send you links to the older ipxe boot files.
Rename the existing ones using the linux console commands. The files are in /tftpboot.
Then install these files there. I’m interested in seeing if the older ipxe boot loaders work correctly.
-
@george1421
Using the default one. Is there a way to install an older version, i dont care if the webinterface look nicer, its only for installing Windows. -
@janspook I wonder if we can get a hold of ipxe from an earlier build and test that?
What boot file are you using? I still have 1.4.4. in my production environment. I’ll upload what ever iPXE boot loader you are using so you can grab it and test.
-
@george1421
Could be, i never had any isues with fog 1.4.4 which i used in a school project. But with 1.5.0 it doesnt seem to work anymore. -
@janspook said in Could not start download:
:os.windows10 initrd nfs://10.0.2.15/images/os/windows/WinPE_amd64.iso chain memdisk iso raw boot || goto MENUThis looks good.
I wonder if nfs support was removed from iPXE.
-
@george1421
http://prntscr.com/iwj3ip
#!ipxe
set fog-ip 10.0.2.15
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http://10.0.2.15/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap – -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.deployimage Deploy Image
item fog.multijoin Join Multicast Session
item fog.sysinfo Client System Information (Compatibility)
item os.windows10 test
choose --default fog.local --timeout 3000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:fog.memtest
kernel memdisk initrd=memtest.bin iso raw
initrd memtest.bin
boot || goto MENU
:fog.reginput
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://10.0.2.15/fog/ consoleblank=0 rootfstype=ext4 storage=10.0.2.15:/images/ storageip=10.0.2.15 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://10.0.2.15/fog/ consoleblank=0 rootfstype=ext4 storage=10.0.2.15:/images/ storageip=10.0.2.15 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.deployimage
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
param sysuuid ${uuid}
:fog.multijoin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
param sysuuid ${uuid}
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://10.0.2.15/fog/ consoleblank=0 rootfstype=ext4 storage=10.0.2.15:/images/ storageip=10.0.2.15 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:os.windows10
initrd nfs://10.0.2.15/images/os/windows/WinPE_amd64.iso
chain memdisk iso raw
boot || goto MENU
param sysuuid ${uuid}
:bootme
chain -ar http://10.0.2.15/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot -
This post is deleted! -
@janspook Well that is interesting. All of the bits are in place, it should download. I guess I need 2 more things.
- From a windows browser key in:
http://<fog_server_ip>/fog/service/ipxe/boot.php?mac=00:00:00:00:00:00replacing the fog_server_ip with the real IP address. Please post the results in here as text. - Provide a screen shot of the actual error message. I need to see the context of the error.
- From a windows browser key in:
-
-
@janspook That bit looks like its setup correctly. From the FOG server’s linux console will you post the output of this command:
ls -la /images/os/windowsThis should confirm the iso image is located in the proper spot.
-
-
Can you provide a screen shot of the iPXE menu from the web ui?
