Better yet forget all of that mysql nonsense. You can add all of your hosts to a group and change Group Kernel to nothing, or whatever you may want there.

@Wayne-Workman Success!

ok the latest snapin has worked as expected. Root cause I think was the locations and how I had set them up. Each host has a Location entry and each location points to a storage group.

I’d set the host I was testing this on to the only location I’d set up for head office and this was pointing to the wrong storage group.

I’ll do some further testing this week but hopefully others with same issue can at least learn from my mistakes…

Wayne, really appreciate the time and effort you put in to help me out with this one, greatly appreciated.

cheers, Kiweegie.

@Lenny87 Hi, there is no “user guide” to add iso on iPXE, it depends what ISO you want to add : https://forums.fogproject.org/topic/5142/adding-iso

Ubuntu is … a hassal and is kind of expected to haver some hiccups. I’d recommend using Cent OS or Fedora. Or if you are more comfortable with Ubuntu, 12.04 LTS is great, its actually what one of my development servers run on.

Confirmed fixed, MBR looks like a much more reasonable 32k now.

Thanks!

Etherboot supports wifi network booting…

I’m looking into using that instead of the current FOG methods for booting.

https://wiki.fogproject.org/wiki/index.php/FOGUserGuide#Installing_FOG

I’d recommend any Red-Hat based linux (Fedora, CentOS, RHEL), but FOG pretty much works on every major distribution.

At work, I’m using Fedora 21 server, at home, I’m using Fedora 22 server.

CentOS 7, Debian 8, Fedora 21 - 22, Ubuntu 15.04, and current RHEL.

I’d just like to state that this issue has been solved.

In summary, the installer will fail if you use DNSMASQ’s built-in tftp server instead of tftpd-hpa.

Thank you for all of your help!

Please close

ok thank you

Make sure FTP works on your nodes, and check credentails for those nodes inside storage management.

https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

There is also credentials inside FOG Config -> FOG Settings -> FOG Storage Node -> Mysql credentails.

Yes, this is looking very good.

Thank you for your quick help! You can close this thread. Have a nice weekend guys!

quickest fix rather than re-installing everything is: on the server rename /var/www/fog/lib/plugins/LDAP to something else like: LDAP1

this will essentially stop the LDAP Plugin “loading”

now you have access back - login to the GUI, deactivate/remove the LDAP plugin (under installed plugins) then rename /var/www/fog/lib/plugins/LDAP1 back to LDAP

if you want to try again and re-check your setting you can now enable LDAP plugin again and if it fails follow the process above again to regain access…logs will be your friend here to figure out what’s wrong 🙂

Thanks to Wayne for all his help!

Thanks a lot 😉

@crosser said:

@Wayne-Workman

Possible? Yes. Practical? Not really, since we have quite a few legacy models.

What I think I might do though is leave our old FOG 0.32 server running in case we need to use it for these specific legacy images.

Thanks again to everyone on the FOG team for all of the development and support you all do!

That’s a good choice. Sorry we couldn’t help more, but this issue is pretty bizarre.

Yep it was the .mntcheck file causing the issue. Removed and now I can upload from any PC to the image without issue. Thanks guys for helping me out with all this

Update:

The single disk resizable seems to be working. I have successfully imaged two computers of various disk sizes and it works.

I guess from my knowledge (issues and experience) with Fog .32, I never used single disk because whomever was before me used multiple partition image. It is also good to know that the image is compressed when sent up to the server. I probably read it somewhere but glazed over it.

I think if I have any problems here on out I will update.

Thanks @Wayne-Workman and @Tom for your assistance, it is much appreciated 🙂 👍

no, it’s not.

However, each storage node has it’s own NFS setup.

So if you edit the image location in your /opt/fog/.fogsettings to be relevant for the node you’re on, the exports will be created following the proper nfs share point.

@mmiat There is no “complete” guide because every occurrence is going to vary in some way.

Sometimes ISO’s can be directly loaded as you attempted first.

Sometimes they cannot. Which can and which can’t is not spelled out nicely.

Most bootable ISO’s will not be an installer itself.

Most installer CDs/DVDs will not be able to be directly bootable.

You have to mount iso’s and use the relative kernel and initrd files from the CD to boot.

Again, I have no clue which will work and which will not work. Nor am I about to test every possible ISO on the market to write a guide for every ISO.

In the case of booting and installing from network using the net install ISO you downloaded, you will need to mount the ISO as if it’s another disk volume. Once it’s mounted, you can direct everything to look there and which files to look for. This should work fine for debian, ubuntu, fedora, or whatever linux distro you’re attempting. For Windows, I don’t know. They often require 4GB of RAM to load into in the first place and I’ve never really attempted such a feat myself. GParted, if it’s got instructions. should work in a similar manner to Debian.

The link I gave earlier should at least provide some insight as to what needs to be loaded from the relevant disk, which is why I provided. There is no guide because it is a completely case by case situation.

Final case: The debugging of this state closed. No solution found with those machines in testing. I ended up with a fully new hardware architecture, a lot newer machine. Fully reinstall again, now on Ubuntu 14.04.2 LTS, 64bit. Fun fact, issue never again happened. Maybe candid camera was removed from room… damn, it was a bit frustrating haveing such insane malfunction with a normally working software. A week passed by, no issue anymore. Strange.

Thx for replies and tries in helping!