FOG Could not start download: Invalid Argument

[HowToGravity]

@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

[george1421]

@HowToGravity said in FOG Could not start download: Invalid Argument:

chain https://192.168.20.2/fog/service/ipxe/boot.php

If you key in the above do you still get an error? I’m going to say yes, but I’m wondering if there are any more helpful error messages.

[HowToGravity]

@george1421
I only get the error:
Could not start download: Invalid argument (http://ipxe.org/1c25e082)

[george1421]

@HowToGravity This is the only thing that is being downloaded

console --picture https://192.168.20.2/fog/service/ipxe/bg.png --left 100 --right 80

But again the only model throwing this error is this inspiron?? The true table is tell me its the computer and not the fog server. I simply don’t understand the error.

Can you confirm the firmware is up to date on this target computer?

Is this an AMD processor? I have seen some references to an AMD processor creating this error too. But I’m not really believing that either.

[HowToGravity]

@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]

@HowToGravity So lets assume that iPXE is incompatible with this workstation for some reason. We have an alternate method to boot into FOS Linux (the custom linux OS that captures and deploys images).

I have a tutorial on how to build a fos linux usb boot drive. Read the article and understand the caveats of going this route. The tutorial is a bit out of sequence because of the way the forum works. So read the first post and then scroll all the way to the bottom for the second posts. Also look at the FOG Forum chat bubble for some additional tips.

https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image

[HowToGravity]

@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]

@HowToGravity said in FOG Could not start download: Invalid Argument:

Grub-install error: cannot find EFI directory

In part 2a or 2b you missed the bit about installing the additional grub libraries it sounds like: sudo apt-get install grub-efi-amd64 grub-efi-ia32 parted kpartx I think you might have an issue with the ia32 and amd64 being installed at the same time. I seem to recall an issue with that.

[HowToGravity]

@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]

@HowToGravity It might be your build envrionment. When I created the instructions they were for ubuntu 14.04 based computers. My current build environment is based on linux mint 19.2 and it still works.

What linux host did you try to build this under? I may need to update my instructions.

[HowToGravity]

@george1421 Ubuntu 20.04