Posts made by Tom Elliott

@AxeMeAQuestion22 Do the BIOS options have a “Legacy USB” mechanism to them?

@jflash so you changed it in mikrotek which is correct. however I believe your machines are also runnign with secure boot enabled, which often is what we see or somethign more along the lines of straight error loading, though freezing is more often what i recall from Lenovo, at least long ago when I first started seeing them.

@jflash Bootfilename should be snp.efi, or snponly.efi (if using UEFI booting) or one of the other ipxe files.

Having the bootfile be your kernel is likely the reason you’re seeing this issue.

@Jim-Holcomb If you’re able to show the error that’d really help. This, in my experience, really sounds kind of like a “Secure Boot Enabled” issue, at first glance.

@robertkwild I do not know why it’s not booting. It looks like it’s getting the file and trying things, but i’m not sure where it’s failing specifically?

@robertkwild The autoexec.ipxe isn’t a problem at all. It is just saying that the file doesn’t exist. It’s meant as a means to allow the consumer (you) to have other scripts that just “work” dynamically. It is not a required file and not the cause of the “freeze” I suspect you think it is.

@robertkwild Try using snponly.efi instead of snp.efi

@Alan-Lim The boot exit (either bios or efi) are configurable in 2 places, where the level at the host is considered the primary source. If a machine is loaded to your network, but not registered, then it will generally attempt to use the exit from the FOG Settings point you posted in your image.

@Alan-Lim Try setting EFI BOOT EXIT TYPE to EXIT

@robertkwild I’m suspecting there may have been a php module update that FTP was working similarly to a found issue in 1.6 and they finally addressed that. I apologize for not thinking of it sooner and glad it’s working. To my knowledge, we didn’t change anything regarding the Folder/File issue, so much appreciated in letting us know it’s working for you now.

@ReinierG What do you mean “it automatically exits”?

What does? Sorry just trying to understand what issue you’re having.

Are you saying there’s no screen for you to perform any action?

If that’s the case (and I’m only guessing) there is a way to extend the timeout. Again, I don’t have my actual option available but It would fall under FOG Settings -> Pxe Menu Timeout or something like that? I believe the default is 3 seconds.

I’d recommend updating this to 5, then increment it slowly (1 second at a time) so as not to make all your systmes seemingly suddenly slow.

@ReinierG This is a setting of the exit type for the host.

There’s 2 places this can be defined. The first place is global should should be configured under FOG Settings -> Exit Type (I cannot remember if it’s specifically under EFI Exit, but I think it is)

The 2nd place is individually to each host.

I would suggest looking at the host settings and see what it’s efi exit type is configured for. It sounds like it’s configured as rEFInd exit, if you set to EXIT does this fix the issue you’re seeing?

@ReinierG I feel like there’s missing information here.

Is fast-restart enabled?

I believe the command you’d need:
powercfg /h off as an administrator account and you should not have the dirty bit issue.

If this issue still persists, I’d also recommend doing a chkdsk/sfc scan of the disk as well.

@infotech_22 Generally speaking, if you do setupcomplete.com, you should completely disable the FOGService as re-enable it as the final step of the setupcomplete.com script.

The reason:

FOGService will attempt to start up and perform its actions alongside anything else that’s occurring. Generally, when the system is setup and running just fine, things are okay because there’s no interactions, but when you pair it with the OOBE configuration stuff, where it could be changing ini’s and Registry thigns, then the FOG Client is saying “Hey restart to change the name and join the domain” or “Hey restart because I completed installing this Snapin” or whatever else may be going on, it can leave your machine in an unknown and cause issues.

This isn’t something we’re able to fix in a codified manner unfortunately and we have given instructions many times to allow FOG Client while in OOBE state.

https://wiki.fogproject.org/wiki/index.php/FOG_Client#:~:text=If you plan to use,the image deployment is complete.

I don’t know if this is in the more modern Documentation, but it is in the original documentation as well.

@eliaspereira I’m not fully sure what is wrong or where it’s wrong at and I don’t really have a means to test.

I’m presuming you posted the issue on github which is a good place to start.

If that is the case it sounds like something missed a step during updating the database potentially?

@John-L-Clark can you try with snp.efi or snponly.efi?

@mashina You may have to make appropriate customizations but here are the basic steps:
https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

@robertkwild There’s only one “stable” one “major/master” and then the one we’re working toward.

Technically there’s also “nightly” so 4 main versions:

• master branch = 1.5.10 (Currently) - Baseline for stable and current updates of the master.

• stable branch = 1.5.10.1634 (Currently) - This is considered (if you will in linux terms) LTS (we’re wanting 1.6 to come out but in the mean time we still need to keep things up and running of the stuff most people are using.)

• dev-branch branch = 1.5.10.x >= 1634 (currently) - This is where we do updates for issues found/reported/ and hopeful fixes to go into the next release of stable. This is what I would call “nightly” but it’s not quite bleeding edge either as this is just holding fixes for hte 1.5.10 and later versions.

• working-1.6 branch = 1.6. This is what some might consider alpha/beta (all working branches will be intended in this manner at least) in that it is where it’s the fully latest bleeding where we hope and want to get to with fog.

@mckayj Ewww CentOS 7.5

I’m only kidding. While CentOS 7 is no longer supported and I would (also) suggest moving a a newer OS at this point this isn’t really an issue. Sorry strange mood for me this morning (for me).

Can you give us the output of your /var/log/php-fpm/www-error.log file? This likely is where the actual errors are showing and we can help provide more information.

@robertkwild If you have the git installation method:

cd /opt
git clone https://github.com/fogproject/fogproject
cd fogproject
git checkout working-1.6
cd bin
sudo ./installfog.sh -y

Should do the trick.

(You don’t have to copy paste and everything, it’s just how I think of it all).

I don’t know how you installed originally or how you stay updated.

I am of the mind git is the easiest method as to get the lastest items you just have to cd to the install and run git pull

But that’s one developer’s opinion

Hope that helps?