[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]

I just talked to someone on the iPXE IRC channel and got some helpful information. The RTL8153 should be supported as both the USB NIC and iPXE support ECM! Please try enable more debugging to see what’s going on ‘DEBUG=usb,xhci,usbnet,usbhub’…

And there is another (old) thread here: [url]http://fogproject.org/forum/threads/realtek-8153-usb-network-adapter.10302/[/url]

I suppose you’ve set ‘Legacy only’ in BIOS…

You can configure several MAC addresses for one host! Maybe that helps…?

Awsome that you got it running now!

Have you talked to iPXE devs too?? Or do you mean FOG devs? I am just wondering because maybe iPXE devs would be able to help out fixing the driver itself. But if this is working for you, you might just leave it like that. Unfortunately I neither have the time nor the hardware to help with this any further although I’d love to help to get this properly fixed. 😉

Problem was with the available free space (it was combination of virtual disk setup and linux installation). Creating my first image now, seems ok so far. Thanks you all for pointing me to right direction.

3081 :
[Fri Mar 06 10:21:03 2015] [error] [client 192.168.123.125] PHP Fatal error: Call to a member function get() on a non-object in /var/www/fog/lib/pages/PluginManagementPage.class.php on line 289, referer: [url]http://192.168.123.6/fog/manage$[/url]

and still the same problem 😕

edit : and i clear cache, i try with another browser, and with another computer 🙂

What kind of image is this? One of the biggest changes from before 1.x.x is the os Is set on the image rather than the host. Make sure the image definition has the proper settings such as image type (resize,multipart,raw),os, and partition (everything). My guess is the image is supposed to be resize but is currently set to multipart which would be why you’re getting the message about mbr.

if you’re not in the working copy directly, or explicitly telling it where the “working copy” is, it assumes the CWD.

For example:

You have terminal-ed in to: /root or /home/jhales

If you run svn up from here, but the working copy is in /root/svn or /home/jhales/svn it will give the error:

[code][jhales@localhost ~] $ svn up
svn: warning: ‘.’ is not a working copy
[/code]

if you cd into the proper directory as such:
[code][jhales@localhost ~] $ cd svn
[jhales@localhost ~/svn] $ svn up[/code]

You shouldn’t have any issues.

Or explicitly set the “working directory”
[code][jhales@localhost ~] $ svn up svn[/code]

You shouldn’t have any issues.

Maybe this would’ve helped… [url]http://fogproject.org/forum/threads/could-not-boot-exec-format-error-2e008001.12001/[/url]

You can find selinux on or off with[code]sestatus[/code]

[COLOR=#000000][SIZE=3]Under Storage Management it’s listed as Max Clients and under Fog Settings you need to have Fog Configuration > Fog Settings > [FONT=Ubuntu]FOG_QUEUESIZE needs to be higher then Max Clients.[/FONT][/SIZE][/COLOR]

You might fix this by truncating the snapins db there is a post about it when first installing svn.