@Connie I’d start off by deleting everything in /images/dev because probably an upload was attempted but not completed due to insufficient space. A lot more work is probably needed though. This is what inevitably happens when you put everything on one partition. There are walk-throughs in the wiki that show how to partition a drive in order to avoid this.

Ah OK, I wasn’t aware of that function. Thank you for your prompt reply. I will give this a try tomorrow!

@pstoric The installer defaults to the (probably) correct choice. Debian would be correct if your installing on Ubuntu. And this choice is not your preference, it’s telling the installer how to interact with the system.

@Souldoubt said in Suggestions for server space recommendation and samba storage:

@Wayne-Workman

Any performance benefits/hits to storing the images in on the same FS as the FOG server?

Nope, other than everything being self contained. That’s how probably 95% of fog sites are. Large sites use multi-node setups.

Is there a best practices document for FOG that I can refer to.

Not really. There are some partitioning considerations that you need to think about, that’s probably the most important thing to get right from the start. Once you get into the groove of FOG, you will start doing things your way. We have some tutorials in the WiKi that are written for the absolute Linux newbie. If you’re a newbie I would recommend following one of the tutorials, and going with CentOS 7 only because it’s tutorial is up to date and I haven’t made tutorials for other distros yet… But if you wanted to go with another distro, we can help you along here in the forums.

@Sebastian-Roth under the Update and Install Packages on https://wiki.fogproject.org/wiki/index.php?title=Ubuntu_14.04 it ask that you run this

cd Desktop/
cd fog_0.32/
cd packages
wget https://svn.code.sf.net/p/freeghost/code/trunk/packages/udpcast-20120424.tar.gz
rm -f udpcast-20071228.tar.gz
sed -i ‘s:udpcastout=“udpcast-20071228”:udpcastout=“udpcast-20120424”:’ …/lib/common/config.sh
sed -i ‘s:udpcastsrc=“…/packages/udpcast-20071228.tar.gz”:udpcastsrc=“…/packages/udpcast-20120424.tar.gz”:’ …/lib/common/config.sh
cd …/bin/
sudo ./installfog.sh

during the “rm -f udpcast-20071228.tar.gz” I hit tab and it did this “rm -f udpcast-udpcast-20120424.tar.gz”.

So I erased the tar.gz that I just downloaded. So it couldn’t find the package which I assume caused the errors.

I hope that clarifies things.

@ghill Can you post screenshots of the area you’re working in to set Option 066 ? The immediate issues are probably there.

But yeah I’d say set up an old computer for testing. And as far as testing iterations go, well… you only need one iteration if you’re following one of our more recent tutorials.

Which brings me back to another point. You said you installed fog based on information in several guides on the internet… Are you aware that the fogproject has it’s own wiki? Things you find on other sites are highly likely to be very obsolete and will probably break more stuff and cause more complications when you try them on FOG Trunk with recent Linux versions.

If you want to make it so you don’t have to comment out port=0 then you can fix this by fixing the resolvconf missing dns server issue.

See this old post for a ton of detail…
https://forums.fogproject.org/topic/2799/dnsmasq-kills-dns-lookup-on-fog-server/6
I know I’ve posted it in a more readable form more recently, but found that one first.

TL:DR
just edit the interface-order at /etc/resolvconf/interface-order to have your main ethernet adapter at the top and be sure to have nameserver lines defined in your static ip definitions if not using dhcp.

Thanks Wayne for taking time to reply.

I will review your suggestions. I’m not really committed to Ubuntu so perhaps changing to OS is worth a look.

@irishfoguser Not sure what we can help you. The solution you mentioned (setup a new RAID and move the images) is perfectly fine!

@Tom-Elliott I know… and was wondering why Wayne posted the “old” URL. Didn’t pay attention and didn’t see that his post is months old…

@Tom-Elliott I updated earlier at work today (like I do most days) and I did notice that “adding needed repositories” took significantly longer than usual.

But - if that’s what it takes to ensure the remi repo gets installed, then that’s what it takes.

Should be fixed in the very latest version!

@mxc Logical partitions were an issue with FOG 1.2.0 when OS type was set to Windows as far as I can remember.

Best to debug things is to start the job/task in debug mode. When creating a capture/deploy task there is a checkbox “Schedule task as a debug task”. Starting the client you’ll get to a linux shell and you can start the task running the command fog from there (description will be displayed as well). Then you can step through the whole process by hitting ENTER. As well taking a picture or video (slow motion!) is always a great way to find out what’s going wrong. When reporting an error we need the exact error message (plus FOG version, server OS, image type and OS type) to be able to understand and reproduce the error.

GPT/MBR is a big chapter. GPT often leaves traces on the disk that might cause an issue. There is a tool called fixparts that you can use from the debug shell as well.

@RipAU Marking this solved as I feel there is nothing much more we can do. Feel free to post again if you have more questions on this.

@xmotion Sounds about right. 🙂

@Sebastian-Roth said:

@Wayne-Workman I like the “Related_to_xyz” naming. Would suite other things as well I guess. Might wanna add this to the Knowledge Base which is linked on the main wiki page!?

Done.

@Sebastian-Roth actually when I said both versions are 1.2 I meant that my old setup that is not on this network(and not connected at all, I connect to it to physically with an unmanaged switch to image right now) and the new server that is on 1.2 the other requests are coming from the dhcp and lead to an Altiris imaging server. I don’t think that matters but Ill try your solution and post real response tomorrow.

**Update ** this has been resolved using the new Undinoly.kpke from as instructed by Sebastian, Thanks you were 100% correct!

You can mark this as resolved if thats an option.
Thanks a bunch guys I just updated to trunk and am imaging my room right now.

If your running Ubuntu you should have some type of file editor installed already. I would assume that it has that loaded.

When you open your terminal you will be a local prompt, if your paths arent set you will not be able to access the file directly.

you will need to

cd /
cd etc
cd network
sudo vi interfaces

It will bring up the file in the VI text editor. Hit the insert key and then arrow down to the last line and enter

FOG Server IP (This is just a remark to remember what your doing)

auto (the name of the NIC you are using. You can use IFCONFIG to view the NICS in the machine) in my case its
auto p4p1
iface p4p1 inet static
address (your server address)
netmask(Your server netmask)
gateway(Your server gateway)

It should be some form of this. Hope this helps.

Tks Sebastian, I’ll try it on Monday in my work because I do not have access to the server today;)

@ManofValor I think Tom’s guess is right, It makes sense.

To be honest, there appears to be absolutely nothing wrong with any of the network configuration on your FOG server.

We can test to see if Tom’s guess is right or not. If this CentOS 7 was installed with a GUI, it came with Firefox. Use firefox to try to visit our forums. If you can, Tom is right - and it also means that only ports 53, 80, and 443 are allowed into your network. IF this is the case, you’ll need your boss to loosen the straps so you can get your FOG server going - after that, he can tighten em down again. Or he can create rules that allow the FOG server full access to the internet. If it were up to me, I wouldn’t have a firewall that prevents work from being done. Do you guys have a demilitarized zone the fog server can be placed in temporarily so it can be installed and configured?