Impossible start ISO image after update Fog to 1.3.0
-
@Tom-Elliott said in Impossible start ISO image after update Fog to 1.3.0:
@george1421 personally that makes the most sense considering the fog directory will be overwritten on any update.
Voice of experience: Already been hit by that upgrade bus a few times.
-
@george1421 well I do copy back the prior folder now too but yeah safety and storage all in one nice package
-
@Junkhacker the web root is FOG !:
-
@george1421 hi, what is your FOG_WEB_ROOT string ?
-
@Tom-Elliott Could you check my dnsmasq setting and tftpboot directory ?
-
@george1421 HI, but the question is:
the syntax of ipxe command it’s changed ?
the system variables are add/changed ?
i tried move rdimage in your example directory with your syntax into advanced boot menu;
the image start but crash with memdisk command …
I tried with sanboot and return others error…i dont know !!!
-
@zingaro said in Impossible start ISO image after update Fog to 1.3.0:
Could you check my dnsmasq setting and tftpboot directory ?
It’s wrong.
the one line should beundionly.0
instead ofundionly.kpxe
and also, between the empty pair of commas, you should have your IP address again. The multi-adapter stuff looks neat, where did you find that? See this for a simple reference setup:
https://wiki.fogproject.org/wiki/index.php?title=Fedora_21_Server#dnsmasq_.28if_using_ProxyDHCP.29_setup -
HI,
there are news ?
I’m not solved again the problem for the boot iso image !!! -
@zingaro See my post ?
-
@Wayne-Workman
hi,
for now i restored the previous hdd image with fog 1.2.0…
I will test your suggest modify on VmWare System after update to 1.3.0…
the Pc’s production is too important for retry a new installation … !! -
@Wayne-Workman
hi, i tried with replace undiolny.0 , into dnsmasq configuation but the result is the same…
i note this anomaly into fog settings , see the image attached.Ho can reset fog tftpboot configuration ?
-
@zingaro it’s possible test a load of image after enter into ipxe shell ?
I tried runnig directly the command:
. memdisk iso raw <- execution ok
. initrd http://192.168.1.130/fog/images/winpe.iso <-- execution failed !! -
In my tutorial I linked below this is the order of command execution
initrd http://<fog_server_ip>/isoimg/LiteTouchPE_x86.iso chain memdisk iso raw
Also make sure permission on the file is world readable.
-
@george1421 sames results… ![0_1474627619530_Capture.JPG]does not works…sames result !!
-
@zingaro where is the iso currently physically located on your server?
-
@Tom-Elliott said in Impossible start ISO image after update Fog to 1.3.0:
where is the iso currently physically located on your server?
/var/www/fog/images
sames pc where fog is installed ! -
@zingaro now the error when trying to boot the iso is execution fail? Or permission denied? The pic you tried to upload isn’t showing up.
-
Oh and web root is configured in two places for rc10. The reasoning is its more dynamic. The global web root from before is for a common GUI setup. But ultimately the communication tries to happen at the node level first. If that fails the global setting will be used. Check the storage nodes web root as well.
-
@Tom-Elliott said in Impossible start ISO image after update Fog to 1.3.0:
now the error when trying to boot the iso is execution fail? Or permission denied? The pic you tried to upload isn’t showing up.
-
@Tom-Elliott said in Impossible start ISO image after update Fog to 1.3.0:
Oh and web root is configured in two places for rc10. The reasoning is its more dynamic. The global web root from before is for a common GUI setup. But ultimately the communication tries to happen at the node level first. If that fails the global setting will be used. Check the storage nodes web root as well.
how i can perform this tests ?