@Amélie What version of FOG?

I’d say try to partition it using Linux. I have some instructions here but they are for Fedora.
https://wiki.fogproject.org/wiki/index.php?title=Fedora_21_Server#Formatting_.26_mounting_a_2nd_SATA_drive

@Jbob Hello
In first sorry for this long delay
I just made the test today with the latest client. Everything seems to work fine !!

@krishnakulkarni said:

how to upload existing captured image of CentOS on FOG?

I’m not sure if that’s a typo or poor English… no offense.

You can not upload an already captured image of anything to fog, unless the capture was done with another fog server.

If you’re simply asking how to capture an image of a CentOS machine, this is pretty basic. Network boot the machine, register it with FOG. Create a image definition in the web interface. Assign that image to the just-registered host via the web interface. in the host’s basic tasks area, choose upload. Then network boot the host again.

Version: 6122 6128
bzImage Version: 4.4.0
bzImage32 Version: 4.4.0

Edit: Just updated to check. Still no go. Rebuilding that machine from scratch and i’ll take a new reference image i guess.

@Tom-Elliott Thank you again Tom. The installer script successfully completes. All appears to be running, now to test.

I should do a better job of explaining things. I just reread what i put and it was pretty vague. TY @Wayne-Workman for being much better at this than me. 🙂

Ok, thanks to everyone answering my noob questions 😉

@Wayne-Workman its not just inside VMWare. I have had multiple physical servers with just CentOS 7 installed fail with this update.

@Wallae said:

I’ve tired uploading the DBAN.iso(16MB) to the server but the limit of 8MB is stopping me from doing so.

What are you using to upload? Where is there an 8MB limit?

Ok thanks so i will write a expect script to install fog automaticly

@bakgat As far as I can tell the options 66 and 67 in the bootp.plist are base64 encoded. Trying to decode (e.g. www.base64decode.org) I only get a sensible result for option 67 (‘undionly.kpxe’) but not for opt 66.

The other thing I notice is that the packet you posted is a request (‘Message type: Boot Request (1)’) from a client machine. You don’t see the options in a request only on replys. See if you can find the answer from the server. DHCP goes like this: Client-Discovery, Server-Offer, Client-Request, Server-Ack (https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol#Operation)

So you should actually see at least four DHCP packets! If you don’t see any reply DHCP packets from the server I am wondering if the bootp service is actually started?!

Here you can find a discussion (https://forums.fogproject.org/topic/6074/extending-a-file-system-on-redhat-base-distros) and wiki article on this topic (https://wiki.fogproject.org/wiki/index.php/Add_%26_Extend_a_2nd_Virtual_HDD).

Depending on your setup (you haven’t told us anything about that yet - OS, version, virtual/physical, partition layout, free space or second hard drive?) you probably need to adjust most of the tings mentioned there. But this should give you a good starting point. For further assistence we do need more information!

@erkax https://forums.fogproject.org/topic/6154/selinux-policy

Using the CloudOS from Neverware. I successfully installed it on a computer and imaged it successfully. I think you would classify it as Chromium OS but it has been modified with more driver support and other things. I am using the free version not the paid for one with Google Apps support.

I used the Linux with multiple partitions single disk.

I was actually able to install this on several different hardware models with no issues as long as the hard drive was the same size or larger than my original test machine.

Optiplex 360.380, and 390
Lenovo X130
Inspiron Duo

Might be able to extend some of the old hardware this way.

Ok so here is the result, I got it working thanks to a person on this forum named aaoyagi.

When I followed his instructions my Linux distros booted without fail via my fog server over the network!!!

In case anybody wants the steps:

First in your /etc/exports add this line:
/var/www/fog/iso/15.04_64 *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)

Then restart your nfs server. If you’re running Ubuntu it’s sudo service nfs-kernel-server restart

Next, extract the Ubuntu iso to a direcotry named 15.04_64 in your /var/www/fog/iso directory.

In your Advanced menu use this:
:MENU
menu
item --gap – ---------------- iPXE boot menu ----------------
item ubuntu15.04_64 Boot Ubuntu 15.04
item return return to previous menu
:ubuntu15.04_64
set path /fog/iso/15.04_64
set nfs_path /var/www/fog/ISO/15.04_64
kernel http://${fog-ip}${path}/casper/vmlinuz.efi || read void
initrd http://${fog-ip}${path}/casper/initrd.lz || read void
imgargs vmlinuz.efi root=/dev/nfs boot=casper netboot=nfs nfsroot=${fog-ip}:${nfs_path} ip=dhcp splash quiet – || read void
boot || read void
goto start

Hopefully it works for you too. You don’t have to set the variables. I just did it that way in case I ever have to change where the iso directory lives.

@Killklli Are you still working on this? I have done a lot of testing and I am pretty sure that dnsmasq is not able to boot most UEFI devices as it uses DHCP option 43 which they don’t like (see here: https://www.mail-archive.com/dnsmasq-discuss@lists.thekelleys.org.uk/msg09233.html). I am working on a node.js proxy DHCP to support BIOS/UEFI and Mac OS X. But will be still a while I suppose - BIOS works pretty good and UEFI is not far either but the code is still a big mess.

Follow this thread: https://forums.fogproject.org/topic/5870/dhcp-proxy-for-fog

yes, /etc/hosts as told in my post indeed, and /etc/resolv.conf as well. All information required to be fetched a way or another. Be it by a custom client or something else.

@Uncle-Frank @Wayne-Workman 4848 solved my extended partition problem. Thanks a lot!