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!

@Wayne-Workman It’s only working if the NAS isn’t the Master Node, I think…

@Wayne-Workman Multicast works now fine. Thanks for the update 😄

Man thank you so much, we have our students save their files on SD cards and man does that screw with the mounting process for drives in FOG. Never even thought of that and my employee said today what if we take the card out, problem solved.

@Tom-Elliott

Where do I do that? Can I do it in the FOG GUI or from a command prompt?

@Etrain

lol… that’s definitely why it wasn’t working.

Additionally, with that check box checked, you do not use FOG Crypt any longer.

You type your plain text password in, hit save, and it gets encrypted with an insanely secure security/encryption system.

Also, with that checkbox checked, the Active Directory section on the host management page only accepts plain text (if you type it in manually) and then encrypts whatever you type there. The auto-populate would just populate the already-encrypted password.

I move the machine over to another hosts in a new blade-center (Was in a crappy Dell 1U server host before) Problem ceased to exist. I also upgraded to the SVN latest and it seems to be working pretty good;

Glad you got it working! and, that info is good to know.

I am going to have to set FOG up at our central location for something like 27 buildings soon… glad to know what to use now!

At the moment, I’m sort of the lone ranger using FOG in just one building, and everyone is envious of my 4 minute image deployment time, with auto naming and auto joining to domain… and web functionality. And, the people at Acronis screwed up when my manager called them up with a list of basic questions about their network solution… and nobody he got on the phone with could give direct answers… so they missed out on something like a $50,000 sale lol. My manager wants to move forward with FOG now. 🙂

@fsu1tm I sent you a message in chat as I am sure we can help fix this issue for you. It’s relatively simple to work out.

The FOG_STORAGENODE_MYSQLUSER and FOG_STORAGENODE_MYSQLPASS are for storage nodes to link to a central fog server.

Hopefully this helps explain that. These are not what you would want to put in your main server, though I suppose it wouldn’t hurt them either.

@ch3i said:

@Oleg

Hi,

Not sure in 1.2, but in SVN version you can specify the default boot via FOG Configuration > iPXE Menu Customization

Regards,
Ch3i.

perfect, that’s what I was searching for.
I will give it a try.
Here the tutorial for installing the SVN for other with the same problem:
https://wiki.fogproject.org/wiki/index.php/SVN

The long-term solution is having only one FOG server, and having storage nodes at the different sites. You could use the “location plugin” also.

ok. I´ve found it.

Just changing the config in
/etc/php5/cli/php.ini and /etc/php5/apache2/php.ini

Thanks
Angel