@Wayne-Workman @Quazz Fixed, it was that fixparts was missing from 1.5.4 as discussed from this post https://forums.fogproject.org/topic/12059/fixparts-missing-1-5-4-win-10.
To be on the safe side I manually downloaded bzImage, bzImage32, init.xz, and init_32.xz and put them in /var/www/html/fog/service/ipxe/. I followed the directions “Manual update to latest kernel” on this wiki page https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update.
@george1421 So I ran sudo apt-get install grub-efi-amd64 parted kpartx & sudo apt-get install grub-efi-ia32 parted kpartx separately and I am still getting the same error.
I also tried using Method #2 (windows path / BIOS boot) but the i am not able to get the file ldlinux.sys generated. I am running the unetbootin-shortcut as Admin, i even tried 2 sperate ways of running it as admin. First way was right click the shortcut and run as admin, second way was running CMD as admin and launching unetbootin with the parameter showcustom=y.
Not sure what I am doing wrong or what I am missing.
@george1421 So i am following the instructions listed on this form https://forums.fogproject.org/topic/6532/usb-boot-target-device-into-fog-os-live-fosl-for-debugging to create a FOS linux USB and I am getting on step #12 sudo grub-install --force --no-floppy --boot-directory=/mnt/boot /dev/sdX. Every time i run the command i get the following error Grub-install error: cannot find EFI directory.
Hopefully i am following the right instructions.
@george1421
Just finished updating the BIOS and still no luck. Everything else looks to be up to date.
Do you know if anyone has had an luck with imaging eMMC flash storage before?
Exact model is Dell Inspiron 11 3195.
@george1421
I only get the error:
Could not start download: Invalid argument (http://ipxe.org/1c25e082)
@george1421
So i deleted the host LIB1723561 and i am still getting the same error as before.
This is the contents of /tftpboot/default.ipxe
#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch ${buildarch}
params
param mac0 ${net0/mac}
param arch ${arch}
param platform ${platform}
param product ${product}
param manufacturer ${product}
param ipxever ${version}
param filename ${filename}
param sysuuid ${uuid}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
:bootme
chain https://192.168.20.2/fog/service/ipxe/boot.php##params
Any specific commands I should enter in the iPXE shell after hitting s
Just to be clear here, this problem only happens on this specific model of computer? All other computes work correct, right?
Yes, since updating the bzImage this morning I was successful at capturing and deploying an Optiplex 5040 image.
If that assumption is correct, do you have a cheap/dumb/unmanaged network switch?
Yes, exact model is D-link DGS-1008G
@george1421
netstat -an | grep :80
tcp6 0 0 :::80 :::* LISTEN
netstat -an | grep :443
tcp6 0 0 :::443 :::* LISTEN
tcp6 0 0 192.168.20.2:443 192.168.20.3:56931 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56922 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56923 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56910 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56921 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56933 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56932 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56920 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56930 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56935 ESTABLISHED
tcp6 0 0 192.168.20.2:443 192.168.20.3:56928 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56929 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56912 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56919 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56918 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56908 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56917 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56927 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56909 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56911 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56913 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56916 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56926 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56934 TIME_WAIT
tcp6 0 0 192.168.20.2:443 192.168.20.3:56925 TIME_WAIT
@george1421 Not to my knowledge I do not have HTTPS setup, I am the only person who access the FOG server. I followed the link and it does lead me to the background image for FOG, but it is unsecured.
*edit: Interesting HTTPS port is active. I don’t believe I opened it, FOG is the only thing i am using this server for.
@george1421 Is this computer currently in an imaging mode? Like it was registered then you picked deploy or capture. When you are booting after scheduling the task this is the error you get?
The computer it self is not registered yet with FOG, i still have to get it registered. But from looking at the log, I believe the USB to Ethernet adapter MAC address is registered but under a different computer. So no task has been schedule yet for this computer. My intentions were to boot to FOG then perform a full host inventory and registration.
I am not sure if adding the “-” (hyphen) in the MAC address into the URL makes any difference but I will add both of the outputs below.
without hyphen.txt
with hyphen.txt
*Edit: There are no task queued on the server