Yes, background image is different issue I have learned from previous problem. Again, thank you for your helping with this netmask and IP range problem. Without your help I probably go crazy, LOL.

@Wayne-Workman nope not a parsing issue more likely it was an importing issue that failed to set up the macs for the host. It has been , as far as I’m aware, been fixed for at least 5 days though.

@tom.langenfeld Your fogguiuser and fogguipass fields are completely separate from the username/password fields as defined in the fogsettings file. Those new fields are ONLY relevant to the GUI itself.

Well, I’m not sure what happened but I tried to restart it yesterday and then it wouldn’t boot up. Something about no controller. Anyway, I guess CentOS 7 gives you the ability to boot from a last known good configuration and when I did that everything worked. I updated FOG and Apache2 went through without a hitch. Sorry to waste your time, thanks guys.

@Tom-Elliott Sure does. Thanks for the help!

@Wayne-Workman:
The GPT was the issue. I am now able to capture the image from the M72z. Thanks for the help.

-Roy

Thank you so much that worked and fixed my issues too!

Running very latest svn 5829, client 0.11.2 on Win 7 32 bits. Framework 4.0.

dmidecode is not available by default in OSX it seems. I started the fog debug mode and got the following:

# dmidecode 2.12 # SMBIOS entry point at 0x8cd15000 SMBIOS 2.4 present. 51 structures occupying 2746 bytes. Table at 0x8CD14000``` The message " Invalid entry length (0). DMI table is broken! Stop." only appears at the end of the dmidecode command.

Thank you I wasn’t able to find similar posts.

@Wayne-Workman I did. I think I’m good for now, I just deployed an image and it worked quickly and perfectly on SVN vs when I tried with 1.2.0 earlier. Thank you guys for your help and building this wonderful tool.

@Sebastian-Roth @george1421 After setting up a fresh install of Ubuntu 14.04 Server and FOG Server 1.2.0 I have finally got it working on a isolated network - only thing now is that the switch I want to use has to have STP disabled (waiting to get a console cable). Thank you all for your help.

@Tom-Elliott Thanks Tom! All is working great. You and the rest of Fog team are the best! I truly appreciate all the great things you do.

I did a fresh install again and did sudo -i and installed if from that prompt the first time, and everything worked now. It is currently up and running, thanks for all the help.

Maybe checkmark boxes in the image definition to tell the inits to move the start sectors? Could be I guess 5 checkboxes, for 5 partitions. Some may have more partitions than that but I think 5 would cover most.

@Tom-Elliott

The group settings change in the update fixed the problem!

Thanks!

Updated to 8341, this seems to be fixed. had me freaked out, as my 4th of july weekend involves imaging 1200 machines…

This may be a good time to mention the custom web-based isc-dchp thing I made specifically for fog?
https://github.com/wayneworkman/fogDHCP

Ok just an update, I got the issue fixed. To do so I had to delete the entries manually from the MariaDB for Fog. (Mysql)

[root@localhost ~]# mysql -u root fog Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 29 Server version: 10.0.23-MariaDB MariaDB Server Copyright (c) 2000, 2015, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [fog]> delete from hosts where hostName NOT LIKE ' '; Query OK, 51 rows affected (0.00 sec).

So basically

mysql -u root fog delete from hosts where hostName NOT LIKE ’ ';

As a note the second line as I used it deletes all hosts, if you have a problem with only certain hosts then you would want to alter that.