@dureal99d This will depend entirely on what you’re trying to boot and how your machines are setup and what not.
Maybe the tools you’re trying to boot don’t support UEFI mode. Maybe you left Secure Boot on BIOS. Or maybe it’s something else entirely.
Check those two things for us first, if for nothing else but to rule them out.
From what I’ve read on the Wiki they need to be added to the additional dnsmasq options manually.
https://wiki.fogproject.org/wiki/index.php/FOG_with_DD-WRT_firmware
@dureal99d They need to have fsid assigned at the very least to work properly as far as I know.
@dureal99d You’ll need to add subtree_check as well, otherwise any folders underneath it won’t be accessible.
The files of /var/www/fog/service/ipxe are in your /var/lib/tftpboot folder and the the /tftpboot folder does not exist.
Try running the FOG installer again and hope it can fix this mess.
My guess is something went wrong with the upload.
Most likely FTP failing to move the newly captured images.
Can you check in /images/dev if there’s a folder there?
I’d just like to chime in and discourage using Excel to save csv files.
It tends to fuck up formatting, save large numbers in scientific notation and so forth.
Fairly certain size is calculated right after capture, seeing as you have a new database, this data is not in there.
Imaging should work.
It says the snapin is still queued, which means it has no completion time.
I’m guessing the formula for duration is
completion time - start time
So, most likely it simply doesn’t have a completion time yet.
Can you check your /opt/fog/.fogsettings for
snmysqluser="{root}"
snmysqlpass="{PasswordIfYouHaveOne}"
snmysqlhost="{localhost}"
Given that it says invalid login, I’m guessing the login will be invalid in the fogsettings file.
@THEMCV Did you edit the fog.drivers you got from Tom?
Because the default version would mount /images/drivers
@THEMCV I do not recommend having commands in the postdownloadscripts, only calls to your scripts.
Move the relevant information into another file, imo.
Do you have access to console/terminal?
If so, navigate to /images/dev
There you will see a folder, remove it and its contents.
Reboot the server and you should be fine.
Looks like the same thing happening over at
https://forums.fogproject.org/topic/8961/problem-on-hp-probook-650g2/11
@Sebastian-Roth said in ntfsresize & ssd Intel PRO 5400 series:
Possibly this change is causing the error? https://github.com/FOGProject/fogproject/commit/e748a9da95b91103890bf5d2c126091839875c8a
It seems to fail before it even does a resize test or otherwise there’s no output of it, which is most strange.
@Chuck2000 Hi, can you please highlight your new setup details?
OS version
FOG version (including RC number)
Also, what system are you trying to capture/deploy ?
Oh and is your FOG server the DHCP server now or is it using proxydhcp or did you alter the DHCP server? (and which bootfile are you using? (default is undionly.kpxe))
@SharonLampe Which file is currently set in the DHCP options?
Legacy BIOS can’t boot .efi files and UEFI BIOS can’t boot anything BUT .efi files.
@lebrun78 Hi, please do
rm -rf /var/www/html/fog
rm -rf /var/www/fog
Then try running the installer again.
You shouldn’t alter the installation files. I have no idea what state they’re in or what they’re actually doing now, making it impossible to assist.
The only problem you had was that PHP5.3 was installed and that a newer version needed to get installed. The installer has ways of managing that, no need to alter the scripts themselves.
So, remove your FOG svn folder and pull a fresh version to make sure everything is as it should be.
Then remove the packages= line from /opt/fog/.fogsettings (otherwise it will continue to select PHP5.3 packages as previously defined by 1.2 installer)
Remove every trace of PHP 5.3 from your system.
Run the commands Tom gave.
Then run the installer.
@svalding Double slash shouldn’t cause issues though (try adding a double slash in an url, it will resolve just fine)
Could you update to the latest version? Might help.