[quote=“jbrabhamMSD, post: 24822, member: 22901”]Tom, should the link to the bzImage file have the fixes you made? And where do I go to change pxelinux.0 to undionly.kpxe? Thanks for your help on this.[/quote]

You will want to update your DHCP server information, specifically Option 67. You will want to update your DHCP server to point to the undionly.kpxe file instead of the pxelinux.0 file you used with FOG 0.32.

If you use a dnsmasq proxy service, you need to edit the ltsp.conf information and update the pxelinux.0 listing in there to point to the new undionly.kpxe as well.

Also the link provided is the most up to date version of the kernel and includes all fixes up to this point.

Currently, I’m only testing on one machine at a time. And I’ve tested on several machines of the same model with the same results.

There’s around 100GB of free space (SATA disk) on the server for storage.

Hi noelpd,

I know it’s late and you might have resolved your problem, but I have come up with a cause and solution (at least in my case).
[LIST=1]
[]In order to schedule tasks, whatever it is the task, you must assign an image to the host/group you are trying to send the task.
[]The server from which you are sending the task must be the group’s master node. I realised that, in WebUI > Other Information > Log Viewer > Scheduler, the server wasn’t the group manager and it wasn’t scheduling tasks.
[/LIST]
I hope this helps.

That is exactly what I do 🙂

I fixed the Problem. After I tested imaging with a other machine (win7) and this worked I only changed the OS entry in the fog web ui at the XP machine wich was unable to image. Now it works. 🙂

I tried bzImage32 but it does the same thing. The disk is set to IDE in the VM so not exactly sure what is going on.

Glad I could help, and thank you for using the search button!

That’s my oldest Daughter in the picture, my girl snapped a picture of us once while we were napping 🙂

I changed the kernel, and now at the menu screen I select “quick registration” and nothing happens. The only option that works is boot to HDD. Should I try a new kernel?

[quote=“BPSTravis, post: 24665, member: 22444”]install php my admin and delete the host out of the hosts table.

Or run the sql query:

“DELETE FROM hosts WHERE hostID=”" OR hostID=“0"”[/quote]

OMG! thanks!!!

That error is because it does not have internet access, all that does it contact the website here and check the version/number of sites.

See if you can log into mysql from a terminal window as root with whatever password you used to set up the fog server.

IF that password works, update i in /var/www/fog/commons/config.php

If not, then you need to reset your mysql password and your issues will be resolved.

Another thing to check is if the users password got changed, logins are stored in the users table and the password is encrypted with md5.

I’d recommend taking a look at the ftp server configuration on the NAS. It seems, to me, that the configuration of FTP is just making the FOG user’s Home directory as /volume1, so when the first login happens, the root of it is the root of volume1 which leads you to /images /images/dev.

Maybe, if you can find the configuration and make the home for the fog user the / of the drive, this can be resolved. I can code in this stuff as well, but don’t think that that’s the solution proper. It’s much easier to make one change to a configuration file rather than make code changes to the core of how fog operates. While it can be done autonomously, it’s not the norm.

As we found out earlier, you can’t nfs share an nfs shared volume. My solution was to use another mounting medium such as ceph or glusterfs, but don’t know if this would work in the case of NAS’.

Its loading drivers, you can try building a custom kernel and include ONLY the drivers your machines need.

There is a guide on this forum about creating custom kernels. That is the only way I know of to speed up a kernel load.

what is the usual cause of corruption in the images? over the last 6-8 months we have had a few go bad, I would just recreate them if it was a one off, but this seemed to be a bunch so I wanted to make sure it was corruption before reinstalling.
We are running identical hardware (both with the same redundancy/mirroring) at another school and have had zero issues.

They’re configured under FOG Configuration->FOG Settings. FOG_TFTP_PXE_KERNEL should be set to bzImage32 and FOG_PXE_BOOT_IMAGE should be set to init_32.xz

They’re stored in {fogwebdir}/service/ipxe/

Hope this helps.

Well, this isn’t necessarily the case. Depends on the layout.

If you create an image as multipart non resizable off of a fresh cd install of windows 7, the d1p1 and d1p2 files, for all purposes, are rec.img.000 and sys.img.000 respectively. So you could, potentially, switch this image from non-resizable to resizable. However, if you create a resizable image, you are kind of stuck. This is because the mbr is not available.

If you were to go from multipart to resizable, you’d need to rename the d1p1.img and d1p2.img on the server.
Rename d1p1.img to rec.img.000
Rename d1p2.img to sys.img.000

I hope this helps.

What?

If it passed the first time, but not the second, then something would possibly be wonky within the BIOS is my guess. There’s no changes made to the system or kernel during the registration phase.

and those problems were solved with…? replies without answers are worthless. (my statement isn’t in a mean tone)

The best way I found is to export the appliance, unfortunately. Unless you only want to make copies in which case cloning would be the best solution.

I use an external drive to store all my Virtual Images on so I don’t actually “export” them I just set up the appliance with the current files at my other locations. This allows me to have the same image and upload to the different servers (I chose stand alone servers instead of Nodes… not really sure why, I was just new at setting FOG up and I never re did the set up I know it’s going to change when I upgrade to 0.33 version but for now I just have multiple servers.)

I am partial to the snapshots feature. That and I use fairly antiquated technology, the ones that are on the phase out, for my imaging so I never had a GOOD server to build ESXi on, so the bad taste left in my mouth may be my own fault, but I never had good luck with VMWare.

Which Revision of Ubuntu?

I can confirm that 13.10 works fine. There are ALWAYS issues to over come when launching FOG in each environment, everyone has different switches and hardware. I know you want to blame Ubuntu, and I will admit that the latest revision of Ubuntu have needed some adjustment to work perfectly with fog. But I can also confirm that each one of my test servers is at the latest revision. So I don’t think this is a problem with Ubuntu.

I also want to note that I am able to boot, and image to my servers on 13.10, but I am using the Beta version of FOG.