Topics created by Mike Fahey

@Mike-Fahey Just tried on a 1.5.9 install and it works perfectly fine for me (Firefox on Debian).

Possibly a browser or caching issue? Trycleaning the cache and using other browsers.

@Mike-Fahey Which mysql command do you use to connect to the database?

The installer uses the following command to login and check if it was successful:

mysql --host=localhost --user=root --password="yoursecurepassword" --execute="quit" [[ $? -ne 0 ]] && echo "Connection failed" || echo "Connection succeeded"

@Mike-Fahey Can you post the commands used to delete and how you see that there is still no free space? If we don’t see what you are, how can we help you?

@Mike-Fahey As George said, the ACPI messages should be ok to ignore for now. About the CPU stall, find some posts from other users in the forums:
https://forums.fogproject.org/topic/8918/fog-boot-to-fos-rcu_sched-self-detected-stall-on-cpu

Not sure if this is the same issue. Please read through the whole post start to end and see if it helps.

@cs_pccs Please start a new thread since your conditions are likely different than the OP, unless you just upgraded from 0.32 version of FOG.

Please include any images you feel are relevant in your post. HINT: A clear picture of the error provides us with an idea of the context of the error as well as the exact error message.

You need to use the kernel and inits shipped with FOG 1.5.4 (almost) or you will have an unsuccessful deployment. FOG kernel 4.17.0 is shipped with FOG 1.5.4. There is something wrong with that kernel version, it takes minutes to create partition tables on target computers. This is not a FOG issue per se, but a linux kernel issue. But to the point roll your FOG kernel back to 4.15.2 via the FOG Settings -> FOG Kernel menu. Also note that the inits are tied to the kernel version, so you need to put the FOG 1.5.4 inits back in place or you will get an error message. Once you provide the info in your own thread, we can start to dive into your issue.

also, support for UEFI systems is simply not practical with pxelinux.0

Well, I have gotten one step closer…kinda. I found a bootia32.efi file that successfully boots me into Grub 2.

Here it is if anyone would like to experiment…

[url=“/_imported_xf_attachments/1/1372_bootia32.zip?:”]bootia32.zip[/url]

if you run that again, it will probably say 1.3.0. i think Tom changed those values now
the svn trunk is the developers branch, it is what will become 1.3.0 when we decide to label it as such, just as it became 1.0.0 1.1.0 1.2.0 and 1.2.1 when we felt it was worthy of those labels. as a developers branch, it is always increasing in features, and varying in stability/functionality.

At work we purchased approximately 140 of these. We eventually gave up on FOG and turned to WDS. If you want to save yourself lots of time and stress I would go this route. Good luck!