Thanks. With the advanced boot configuration it works fine.

If somebody doesn´t want to search, here is my solution:

open /var/www and create a directory called (for example) isos put your isos into it go to advanced options an add your personal menu, for example

:MENU
menu
item --gap – ---------- My boot menu --------------
item Hirens Hirens Boot CD
item return go back
choose --default return --timeout 10000 target && goto ${target}

:Hirens
initrd [url]http://${fog-ip}/isos/hirens.iso[/url]
chain memdisk iso raw ||
goto MENU

:return
chain [url]http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac}[/url] ||
prompt
goto MENU

autoboot

Sweet thanks for the info.

mary,

verify if the [SIZE=13px][FONT=Ubuntu][COLOR=#555555]FOG_PXE_IMAGE_DNSADDRESS has the dns address, I had the same issue and now itś downloading the main.cvd file. This configuration are in Fog setting -> TFTP Server[/COLOR][/FONT][/SIZE]

Ok I had to work on the MBR used FixParts and everything seems to be working now.

Fog web gui upload and check debug.
then start task when command line comes up type fixparts[space]/dev/sda
then y, w, y, fog [enter] until prompts it stops.

[SIZE=13px][FONT=arial][COLOR=#262626][code]fixparts <device>[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626]y[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626]w[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626]y[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626]fog[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626][Enter] 400 times[/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626]reboot[/code][/COLOR][/FONT][/SIZE]
[SIZE=13px][FONT=arial][COLOR=#262626][/COLOR][/FONT][/SIZE]

The attachment you posted doesn’t work. So I can’t really help with whatever error you’re seeing. Please try posting the error again.

And, if you’re quick-registering hosts AND using the FOG client, then the computers will get named with the MAC address.

If you full-register a host AND use the FOG client, and then hit enter through every prompt, the computers will get named with the MAC address.

I’d highly suggest you don’t just blaze through registration. It’s there to make your life easier. FOG will name computers FOR YOU, and can join them to the domain FOR YOU if you simply give the host a proper name during registration, or give it a name later on in FOG’s web management console.

I had to chain boot pxe to ipxe using the pxelinux.0 but not the pxelinux.0.old but one that was provided by ibm in the pxedir folder.

It boots to the ipxe.krn and launches the grub.cfg which then loads img2a and img3a.

(From our conversations) akwan stated this. It’s quite convoluted, but it works.

Right now I am trying another computer with a different image to see what happens.

Ok thanks Guys appreciate the help.

Turns out that even thou the machines are the same. The hard dick are made by two different manufacturers. That explains it.

sql_mode=STRICT_ALL_TABLES is not default for either mysql or mariadb to my knowledge.

I have had to accept defeat for the time being and I have gone back to Fog 0.32 to get me around the Kernel issues. It has caused a back log of stations needing to be imaged.

Can I ask if anyone has any tutorials or links I can read up on to see about compiling fog kernels for 1.2.0, im a complete Ubuntu numb nuts and struggle with getting my head around the commands etc.

Thanks all

[url]http://en.community.dell.com/techcenter/os-applications/w/wiki/2545[/url]

So, good news on this…

We were eventually able to image the system (probably luck), but we wanted to change something on the image and upload a new one.

So, we made our changes and tried to upload again… it just wouldn’t work. Kept saying failure 0 or something… I think it’s HDD related. We messed with this for quite a bit, and I decided to update FOG because Tom said he changed how hardware was detected in the latest svn.

We’re running r3277 now and it started uploading on the 1st try.

Should be.

You’ll need to re-install and just choose DHCP this time.

There is an answer file somewhere that the FOG install script uses, it’ll try to pull answers from that.
You might need to delete that file. You might want to try modifying it first.

To use DHCP, change that option from 0 to 1

Here’s an article saying where the answer file is: [url]http://fogproject.org/wiki/index.php/Upgrading_the_FOG_Server[/url]

Indeed it did the second time I rebooted the machine it’s on. Thanks!

I know this is a bit old but I just wanted to send off a “Fixed my problem” message. I had moved my /images from a directory on the root partition to a new larger partition mounted to /images. When I made the cp -a it did not, for some odd reason, copy either of the .mntcheck files in /images or /images/dev. After creating and setting permissions on those two files everything started to work again. Thanks much!!

Nice, thanks! I didn’t know that setting existed. Everything loads okay now.

What do you mean?

FOG Doesn’t magically delete files from the system. There is the slight potential of losing [b]AN[/b] image based what we can tell on the size of the file and the length of time it takes to copy the old and the new back over. But it would only delete the image that you are currently working on uploading anyway. FOG does not randomly delete images from your server. The few things I can think of,

First, the /images is not a local disk system on the server but rather a mounted disk that mounts to /images, potentially by a USB connection. Maybe the USB lost access due to standby? This would cause the mount point to no longer exist which would appear as if your images are lost.

Second, the /images is local but there’s a problem with the main drive it’s loaded on? It stops being able to be read, which would give the impression of the drive no longer existing. This would assume you have two hdd’s on the system, one that’s hosting your OS, and one that’s dedicated to your images.

Ah ok I understand now - brilliant this has resolved the issue I wasn’t aware that specifying the default OU would have a knock on effect.

Thanks again for your help

They are non-impacting. Ignore them.

Those DB commands are related to upgrading from much older versions of FOG, for backwards compatibility.

So yeah, you’re ready to get Fogging.