@stiger Look at this post:

https://forum.acronis.com/forum/acronis-true-image-home-forum-older-versions/pxe-boot-possible

I’m copy/pasting the important part in case the resource goes away:

After the installation of Acronis on your Desktop DON’T create an ISO.
Start a creation of an USB stick. Then on the USB Stick you’ll find the files
dat3.dat / dat2.dat.
The file dat3.dat ist the kernel.dat.
File dat2.dat ist the ramdisk.dat

So you could rename them and copy it to you’re tftp.
The menu should so look something like:

SAY 02 Acronis true Image 2010 Home
LABEL 02
kernel acronis/kernel.dat
append initrd=/acronis/ramdisk.dat vga=791 root=/dev/ram0 quiet

@m-fitzgerald said in How do I change to order of the Location ID’s?:

For some reason the PC will grab a storage node that is located at a different location from time to time.

Because they are not registered, therefore are not assigned a location. Because of that, FOG uses whatever node that has empty slots. Location Plugin restrictions can only apply to registered hosts that are assigned a location.

We can do it via registering first but it is a few extra key strokes

I want to point out that your entire problem is caused by not doing ‘a few extra key strokes’ to register the hosts and assign a location.

The overall issue I see here (not the location problem) is that you’re trying to use advanced imaging features that FOG has with a cloning mindset. FOG is not Ghost. FOG is an imaging solution, where imaging means intelligently applying an image and then configuring it. Ghost is a cloning solution, where it un-intelligently applies an image and does no configuration. Most of FOG’s intelligent imaging features require hosts to be registered, one of those intelligent imaging features is the use of locations.

@julianh Couple things:

• Make sure the new card gets the same IP as the old card, same subnet mask.
• inside of /opt/fog/.fogsettings update the interface field to the new card’s device name.
• inside of web gui -> storage management -> whatever nodes update your interface name.

@george1421 can you think of anything else?

I helped a bit with this remotely. I couldn’t figure out what was wrong with the DB in the time I had, so we opted to drop the database and re-run the installer. Then re-created one of the storage nodes and replication is working - so it was something to do with the database.

@Developers I did find an issue with creating a new location for the first time in 1.4.4 release - it appears to be some sort of gui bug that won’t let you create a new location. I’m going to confirm this when I get some time and if it’s a thing, I’ll make a bug thread (unless it’s already known about?).

@tvigneau Try this: http://x.x.x.x/fog/management where x.x.x.x is your fog server’s IP.

@barnzy said in HTTP 500: Internal Server Error:

I went to /var/www/fog/lib/fog/config.class.php to find that there was a password that I had set in the setup, once I had cleared this password I checked the mysql connection again and it was working!

Ofcourse that file is editable, but we don’t recommend people to edit it. Set the correct parameters inside of /opt/fog/.fogsettings and then re-run the installer. ELSE, the very-next-time you run the installer, it’ll be broke again because the installer will set the settings inside of /opt/fog/.fogsettings.
See this as a reference: https://wiki.fogproject.org/wiki/index.php?title=.fogsettings

However, kudos to you for using the troubleshooting article in the wiki!

@szeraax If it’s fully healthy and working, I wouldn’t worry too much about it. Make sure everything works though. Like windows activation, reboots are smooth and fast, etc.

@vinay said in Post Install Script does not work while deploying ubuntu 16.04 image using FOG.:

@sebastian-roth
Would you help me with the procedure to include chroot in my below mentioned script as i messed it up adding multiple things.?

I looked over your script. Looks like you’d put the chroot related lines at the start of your script. You should play around with chroot before doing this though. On a linux VM, boot to a live Ubuntu disk or something - then try to chroot from the Ubuntu disk to the local disk. Once you do this a couple times you’ll understand what chroot does and how to work with it. Also you should Google search it (or duckduckgo search it) too. We can’t do all your work for you, we rather show you the way.

Our wiki has this covered: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP
Let us know if you need more help.

@rlindenschmidt said in Image Capture Upload Fails:

Everything works fine right until the very end with an FTP login error.

Please read through this and you’ll get it fixed:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

Let us know if you need any help.

@tesparza If the upload failed, the failed image would be in /images/dev. Also, if your images is on the same partition as the OS (bad practice), then the space the OS is using would be in the graph too.

@dpotesta50 said in error parsing pcc subspaces from pcct:

While loading the PXE boot files that error appears.

In that case, we really need a photo of the error. Please ensure the photo is high enough resolution for us to read the text, that it’s well focused, and does not have some huge glare on it (I am particular because all those things have happened).

@Moderators @ipxefoguser change the default login credentials for the fog server please - anyone can log in with the defaults.

@hvaransky Most likely not a fog problem, just so you know. You should start with general Linux troubleshooting - and focus on network.

There’s a utility for linux called ethtool that you can install & use to see the configuration of the local NIC of a linux OS. Run ethtool on your fog server and see if it’s configured at 1Gbps. Also, make sure the link between the fog server and target host is 1Gbps all the way through. A bad/kinked/broke/borked patch cable can cause a 1Gbps link to be derated down to 100Mbps or even 10Mbps. There’s another tool called iperf to test network thorughput between two linux boxes - install that, and live-boot the target computer using a Ubuntu Desktop disk or something - run some iperf tests to see throughput.

@flipwalker This is what you’re looking for: https://forums.fogproject.org/topic/8151/pxe-quick-registration-w-a-hostname/2
If you need further help, just ask.

@bartont126 Read through this: https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

@bigchief Sounds like a mismatch of bios/ueif to me. A UEFI system can sometimes have the feature to optionally legacy boot (bios). What mode is the firmware in? (bios/legacy or UEFI)? So figure that out - and then dig through the firmware settings to make sure no optional Legacy modes are enabled.

Also, could be something as simple as turning off the HDD’s RAID mode in firmware and enabling AHCI mode.

@imagingmaster21 I would suggest that you should move the old settings file out of the way because it’s likely not correct somehow - and rerun the installer to see if that fixes it.
mv /opt/fog/.fogsettings /opt/fog/.fogsettings-old

Here is some documentation about the fogsettings file:
https://wiki.fogproject.org/wiki/index.php?title=.fogsettings

Here is some documentation on changing the FOG Server’s IP address:
https://wiki.fogproject.org/wiki/index.php?title=Change_FOG_Server_IP_Address

Here’s a tool that will fix everything on the FOG Server after you change the IP at the OS level:
https://github.com/FOGProject/fog-community-scripts/tree/master/updateIP

@chris-whiteley I think this is possible, here are some things I found while searching:

• https://unix.stackexchange.com/questions/34116/how-can-i-limit-the-bandwidth-used-by-a-process
• http://lartc.org/howto/

@msi If I remember correctly (because I’ve asked before), this has not been implemented yet. Until it is implemented, you just need to manually delete those.