I’ve only seen this behavior when upgrading and i forget to kill outstanding tasks or the server reboots during a host edit/add.

[quote=“Joseph Hales, post: 43676, member: 18131”]when you wiped the drive does it still have an mbr fog expects a format drive and errors on a raw blank.[/quote]

I have an ISO image of DBAN on the server to make sure that the drive is properly wiped.

I finally had a chance to look at this project again - I wiped the disk, re-installed a ‘blank’ ubuntu and re-installed FOG. Nothing special, and now it seems to work. Via dumb switch, and via smart switch.

But, thanks for all the help thus far!

[quote=“Junkhacker, post: 43718, member: 21583”]my point regarding the fact that i use a non-GUI version was simply to say that it shouldn’t be an issue.
Chris Wells may have found something that might be relevant [url]http://fogproject.org/forum/threads/not-a-problem-just-a-solution-i-found.12575/[/url][/quote]

I followed these steps and it resolved my problem. I was able to get the FOG software successfully installed, and am now able to connect to FOG manager. Thanks to all for your assistance.

Looks like this on my installation. But please be careful with this as I am not sure about what your offsite FOG nodes will do if the master is empty…

[CODE]# ls -alR /images/
/images/:
insgesamt 32
drwxrwxrwx 7 root root 4096 Feb 3 23:00 .
drwxr-xr-x 28 root root 4096 Feb 15 12:46 …
drwxrwxrwx 2 root root 4096 Mär 7 13:48 dev
-rwxrwxrwx 1 root root 0 Jan 17 10:11 .mntcheck
drwxrwxrwx 2 root root 4096 Jan 17 10:11 postdownloadscripts

/images/dev:
insgesamt 36
drwxrwxrwx 2 root root 4096 Mär 7 13:48 .
drwxrwxrwx 7 root root 4096 Feb 3 23:00 …
-rwxrwxrwx 1 root root 0 Jan 17 10:11 .mntcheck

/images/postdownloadscripts:
insgesamt 12
drwxrwxrwx 2 root root 4096 Jan 17 10:11 .
drwxrwxrwx 7 root root 4096 Feb 3 23:00 …
-rwxrwxrwx 1 root root 233 Jan 17 10:11 fog.postdownload[/CODE]

Correct, the old system didn’t always check null vaues.
The server will need to be upgraded to handle the new client. After that though, the clients can perform in-place upgrades.

It does screw with the logs. It should only need to be done after import/upgrade from 0.32 and even then, only if you’re having problems I think.

Thanks Tom! That did it!

I had database issues with the restart, though. It wanted me to update the database (as during initial installation) and when I clicked it, I received a long list of errors due to the database already being there. I followed some of the fixes on modifying the config.class.php and .fogsettings with no luck. I re-installed FOG which required me to do some dnsmasq changes as well. FOG is working again, but I’ll continue to restart and try more fixes.

Thanks again!!!

in my experience, this happens when i set up a VM as a “windows 8” computer, but not when i set it up as a “windows 7” computer in the new VM wizard. there are no settings i can find after VM creation that make it usable, but you can always install windows 8 on a “windows 7” VM

the new version 1.2.0 the old [SIZE=5][COLOR=#212121]maybe 0.32 no remember[/COLOR][/SIZE]

[quote=“michieru, post: 43559, member: 3086”]Which version of FOG you are using? I am on 1.2.0 and I don’t see these options under image management.[/quote]
Hmmm that’s interesting. As you didn’t mentoin the FOG version in your first post I just searched the source of 1.2.0 and SVN version. FOG 1.2.0 doesn’t have any “Skipping partition” messages in the code as far as I could find. That’s why I suggested the setting.
Are you absolutely sure you use 1.2.0 on that server?? Maybe you updated kernel and initrd at some point??? Maybe check md5sums to see if you still use kernel/initrd coming with FOG 1.2.0
[CODE]$ md5sum fog_1.2.0/packages/web/service/ipxe/init*
27e9244f944ca596c0345f163f31cd22 fog_1.2.0/packages/web/service/ipxe/init_32.xz
87cb38f8f5d5636ca22a5bc6fa0d6684 fog_1.2.0/packages/web/service/ipxe/init.xz[/CODE]

Hey, it was that i had Active directory settings in there, changed them in the main config for FOG,
But the password located on the host machine pass was not encrypted… once i changed that it worked fine.

Love your software man. Great Work.

Ok waited till everyone was done imaging today and ran it and no change so I went back to the forums and truncate table snapinJobs; truncate table snapinTasks; which solved the issue.

Wow that was easy…need to explore the web interface more it seems
FYI, prior to FOG I used Novell Zenworks, which is another linux based imaging system. So trying to learn new ways. 🆒

[quote=“Wayne Workman, post: 43563, member: 28155”]Not a problem at all.

So, the “r” means revision (at least in my head, it works, I’m not changing).

Revision versions are newer than the latest release. The latest release is 1.2.0. The current latest revision is 3096 (but knowing Tom, it won’t be for long, probably within the hour).

You’ll find lots and lots of bug fixes, feature implementations, performance increases, and a wider range of supported hardware and Linux distributions with the latest revision. You may also find bugs that aren’t known about, but also keep in mind that it’s very unlikely that a unknown bug would prevent you from imaging, and wouldn’t result in any information loss.

To update to the latest revision, it’s pretty easy. Look at this wiki page: [url]http://fogproject.org/wiki/index.php/SVN[/url]

I use Fedora 21, and the exact steps I take to update to a specific revision are like this:

[COLOR=#000000][FONT=monospace][FONT=Tahoma][COLOR=#141414][CODE]yum install svn[/CODE][/COLOR][/FONT][/FONT][/COLOR]
[FONT=Tahoma]You only need to install svn once…[/FONT]

[FONT=Tahoma][COLOR=#000000][FONT=monospace][FONT=Tahoma][COLOR=#141414][CODE]svn co -r 3096 [URL]https://svn.code.sf.net/p/freeghost/code/trunk[/URL] /opt/fog_trunk[/CODE][/COLOR][/FONT][/FONT][/COLOR][/FONT]
[FONT=Tahoma]And, for whatever revision I want, I’d just change the number in this line.[/FONT]

[FONT=Tahoma][COLOR=#000000][FONT=monospace][FONT=Tahoma][COLOR=#141414][CODE]cd /opt/fog_trunk[/CODE][/COLOR][/FONT][/FONT][/COLOR][/FONT]
[FONT=Tahoma][COLOR=#000000][FONT=monospace][FONT=Tahoma][COLOR=#141414][CODE]cd bin[/CODE][/COLOR][/FONT][/FONT][/COLOR][/FONT]
[FONT=Tahoma][COLOR=#000000][FONT=monospace][FONT=Tahoma][COLOR=#141414][CODE]./installfog.sh[/CODE][/COLOR][/FONT][/FONT][/COLOR][/FONT]

[FONT=Tahoma]If you’re not using Fedora, I think the only thing that changes is the “yum” command. You’d instead use that apt-get thingy to install svn. So, for Ubuntu, you’d use something like this to install svn.[/FONT]
[FONT=Tahoma][COLOR=#000000][FONT=monospace][FONT=Tahoma][COLOR=#141414][CODE]sudo apt-get install subversion[/CODE][/COLOR][/FONT][/FONT][/COLOR][/FONT]

[FONT=Tahoma]When you run the installer, it should just carry over all of your current settings. It does for me at least. You’ll also be asked during the install to update your database schema. You do that by going to FOG’s Web GUI and just clicking the update button, and waiting for it to get done. There might be some errors from updating the database, but they are non-impacting and are related to supporting upgrading from much older versions I think.[/FONT][/quote]

Wayne,

Thank you very much for the detailed information. I will give this a try and let you know if it fixes the issue or not.

fixparts is a very powerful tool and can cause damage too. So please make sure you read about those things [B]before[/B] you proceed!! The web is full of information about it, e.g. [url]http://www.rodsbooks.com/fixparts/[/url]

I would edit the file /etc/NetworkManager/NetworkManager.conf and remove the line
dns=dnsmasq

or comment it out.

Alright forget about the firewall things I wrote… Switches can be so mean! :mad:
Thanks a lot for reporting back. It’s good to know, so maybe I can point to this earlier next time if someone is having a kind of similar issue!!

There are settings on the client (when you install the FOG client service) AND on the FOG server (service settings for this particular host)! Are you sure you set both? Maybe reinstall the client just to make sure!

The other thing that comes to my mind: Do you have SSD hard drives?? If yes you need to change the startup type of the FOG service on the client to “Automatic (delayed)”. See here: [url]http://www.coretechnologies.com/WindowsServices/FAQ.html#DelayedStart[/url]