@astrugatch You’ve probably read through this?! Fairly easy to setup. Though if you really only need UEFI then you can go ipxe.efi “single handed” and you should be all fine.

@plegrand Tom always has a bunch of different iPXE binaries compiled from the newest source. You find them here: http://sourceforge.net/p/freeghost/code/HEAD/tree/trunk/packages/tftp/

Here you can read about the different binaries - at least some of them: http://etherboot.org/wiki/gpxe_imagetypes

The ipxe.krn binary is actually in the format of a linux kernel. I am still wondering why this is working for you but the others don’t. If you are keen you could capture the boot traffic using tcpdump/wireshark and see what’s going on while you see “sending discovery loop”

There are several other threads about Surface Pro 3 in the forums (https://www.google.com/?gws_rd=ssl#q=site:fogproject.org+surface) but non of them is talking about HDD problems I wonder.

AFAIK there is a SSD drive in the Surface Pro 3, right? Please add the device as a new host with it’s MAC address by hand in the webinterface. Then boot it up in a debug session (Host -> Basic Tasks -> Debug) and issue the following command:

dmesg | grep sd

What do you see?

As we see in what moses posted (https://forums.fogproject.org/topic/6856/replication-has-stopped-after-ugprade) there seams to be an issue with the interface detection in that script. Testing this on my system I find that NFS_ETH_MONITOR on line 7 in bandwidth.php cannot have the correct value as this whole PHP script is not called from within the FOG framework but as URL (like an external call) from dashboardpage.class.php (line 91).

So the whole line simply defaults to ‘eth0’ in most cases because ‘NFS_ETH_MONITOR’ is not defined and ‘dev’ is not sent as request parameter either:

$dev = trim(($_REQUEST['dev'] ? basename(htmlentities($_REQUEST['dev'],ENT_QUOTES,'utf-8')) : (defined('NFS_ETH_MONITOR') ? NFS_ETH_MONITOR : 'eth0')));

As already suggested to Tom I’d vote for a complete rewrite of this PHP file to get rid of executing external tools as well… Proposal coming soon!

@cmurray139 First thing that comes to my mind is SELinux possibly not being disabled in CentOS. Please follow instructions here: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

About the blank page. It’s probably easier to take a look at the apache error logs (see my signature on where to find those)!

If you still want to check the packages then take a look at the FOG installation logs. Those are placed in the same directory where the ./installfog.sh script’s been run. As well you can check /var/log/yum.log for a list of packages.

By the way, which version of FOG do you use?

@Killklli Is this in the web interface or when a client boots up? Sorry but I just can’t imagine what you mean. Maybe a screenshot or photo would help.

What about this:

dmesg | grep ATA

Sorry, this is just guessing in the dark so far. Probably best if you could upload the whole output so we can have a look. Again, boot into debug mode and then:

mkdir -p /mnt
mount -o nolock <your-fog-server-ip>:/images/dev /mnt
dmesg > /mnt/dmesg.txt
umount /mnt

Edit: Just for the records, here is what dmesg on a Surface Pro 3 might look like: https://gist.github.com/altercation/30776be1078eac2b0cc6

<?php
function getInterface() {
    $dev = trim($_REQUEST['dev'] ? basename(htmlentities($_REQUEST['dev'],ENT_QUOTES,'utf-8')) : 'eth0');
    $sys_interfaces = array_diff(scandir('/sys/class/net'), array('..', '.'));
    $interfaces = array();
    foreach ($sys_interfaces as $iface) {
        if (trim(file_get_contents(sprintf('/sys/class/net/%s/operstate', $iface))) === 'up') {
            array_push($interfaces, $iface);
        }
    }
    $interface = preg_grep("#$dev#",(array)$interfaces);
    $dev = @array_shift($interface);
    if (!empty($dev)) {
        $rx = trim(file_get_contents(sprintf('/sys/class/net/%s/statistics/rx_bytes', $dev)));
        $tx = trim(file_get_contents(sprintf('/sys/class/net/%s/statistics/tx_bytes', $dev)));
        return array('dev' => $dev,'rx' => $rx,'tx' => $tx);
    }
    else {
        return array('dev' => 'unknown', 'rx' => '0', 'tx' => '0');
    }
}
header('Content-Type: text/event-stream');
echo json_encode(getInterface());
exit;

@dpotesta50 Alright, got that. See here: https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

And what about ‘cat /proc/partitions’?? Maybe try ‘fdisk -l’. Just thought I point you to gdisk in case you have GPT on your disk…

Did you download the new init and kernel files before testing?

@Wayne-Workman Shall we have a false case for those statements like:

[[ $(validip $routeraddress) -eq 0 ]] && echo "    option routers $routeraddress;" >> "$dhcptouse" || echo "    option routers-seams-to-not-be-a-valid-ip $routeraddress;" >> "$dhcptouse"
[[ $(validip $dnsaddress) -eq 0 ]] && echo "    option domain-name-servers $dnsaddress;" >> "$dhcptouse" || echo "    option domain-name-servers-seams-to-not-be-a-valid-ip $dnsaddress;" >> "$dhcptouse"

This would cause the DHCP server to fail on start I’d say!

Beside that I wonder why you had the full isc-dhcp config string in your .fogsettings file. Cannot find anything in the scripts that might cause this. Cannot reproduce either. Added by hand?

@gwendallecoz What version of FOG do you use? Which version of Windows do you have?

FOG does actually rename Windows hosts after deploying an image. Mostly works but maybe there is an issue in your case. As well there is the fog-client software that can be installed on the client before capturing and deploying an image. When the client comes up after a deploy the clients checks the hostname and will rename the client to match the name configured in FOG for this host.

@mjcrane Just stumbled upon this interesting article: http://jpmens.net/2011/07/18/network-booting-machines-over-http/
Checkout his dnsmasq configuration. It’s not proxy mode so better do not just copy&paste this whole config. But take a closer look on what he does with matching. Pretty good I think. It might help in your case too?! In case it does not help I would be interested in getting a packet dump when the client boots up. Best would be to use a network hub just in front of the client to be able to capture all the traffic. Or a dump on the FOG server could also be of help if time is sparse.

# iPXE sends option 175; make a rule named IPXEBOOT to match requests
dhcp-match=IPXEBOOT,175

# if the request does not (#) match the IPXEBOOT rule tell the client
# (most likely standard PXE client) to boot iPXE
dhcp-boot=net:#IPXEBOOT,undionly.kpxe

# Set "next server" for iPXE to boot from this URL
dhcp-boot=http://192.168.1.10/ipxe/boot.php

@Wayne-Workman More and more I think there is no way around a proxyDHCP implementation for FOG. But we still need to discuss about language… I reckon.

What does it look like on the original system?? If this is a real RAID controller you shouldn’t see the two disks in Windows! A real RAID is not configured in Windows/Linux but has it’s own (BIOS-like) configuration. You’d have to configure the RAID on the target system before cloning. This cannot be done by FOG!

Login incorrect -> FTP credentials screwed? https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

@thatrandomaustralian said in booting iso’s?:

i assumed there was but when i try to use the forums search engine i just get a blank google page

Forum search is working great for me. Though if you can’t use it try google foo. Open normal google.com.au or whatever and search for site:fogproject.org whatever you wand to search for
This way you should get all the results from our forums and the wiki.

@giolnl I guess your /etc/exports on OMV should look like this:

/export/backup 10.21.0.0/16(rw,subtree_check,secure)
/export/images (rw,subtree_check,secure)
/export/images/dev (rw,subtree_check,secure)

# NFSv4 - pseudo filesystem root
/export 10.21.0.0/16(ro,fsid=0,root_squash,no_subtree_check,hide)
/export (ro,fsid=0,root_squash,no_subtree_check,hide)

Maybe even add the NFS parameters originally used by FOG (see ch3i’s post).

Re-reading your post and trying to find out a bit more about the RAID in Optiplex 9020 I noticed that I was totally wrong, sorry! This is not a real RAID but a fakeraid (as you already said in your first post ). It is Intel ICH8R (82801HR) southbridge which they call a ‘firmware RAID’. After setting it up properly on the target machine (http://www.dell.com/support/article/us/en/19/SLN153494/EN) you still need to address this in linux as well.

Do you have ‘Host Primary Disk’ configured for those hosts? FOG is not intelligent enough yet to find out about (fake)RAID setup and use the correct device just by itself! You might be fine not setting ‘Host Primary Disk’ for the host you are getting the image from as /dev/sda should be equal to /dev/sdb (FOG uses /dev/sda as default). But you need to set this to /dev/md0 to make FOG properly deploy to your RAID.

By the way: “Multiple Partition Image - All Disks” probably won’t help you as the RAID array won’t be in sync if it is not properly deployed through the correct device file AFAIK.

@Matthieu-Jacquart The /opt/fog/.fogsettings file is only an answer/config file for the installer. If you make changes to that you need to re-run the installer. Possibly you have the password in the .fogsettings file different (e.g. changed password within FOG after install). If you re-run the installer then (with different password set in .fogsettings) it probably changes what you have set in FOG.