I reset the permissions of /images and everything under it to 777 (again), and also set the owner and group to root. This seems to have fixed the problem. Not sure why it didn’t work with the first couple of images I created, but it seems to be working now. Thanks for your help everyone 🙂

solved, the problem is that on dhcp server the 067 option filename is changed, now is undionly.kpxe, not pxelinux.0

the “boot memdisk iso raw” method won’t work with linux disks, typically
on the other one’s, you might be able to get some hints from this page [url]https://gist.github.com/robinsmidsrod/2234639[/url]

The records are stored in the imagingLog’s table, and I only recently as in 1.x.x started copying the records displayed on the home screen from this table, where prior it was pulling from the tasks table entirely.

the tftp service failing to start automatically is a known problem with some linux distro’s especially ubuntu, the answer is on the forums somewhere. rerunning the installer every boot is NOT the solution to this problem.

yes i have checked nfs server is running
I just found out that i cannot mount filesystem of share of ubuntu server to any of the linux machine.
i got same error

[quote=“PdsNick, post: 30732, member: 24454”]Hey cbirch,
I don’t know if this helps you at all, but I was able to fix my problem of a blank FOG configuration page by ignoring my FOG server IP address in the Lightspeed content filtering appliance that is in-line in our network. Apparently it was blocking the download of certain files during the ./installfog.sh portion of my installation, resulting in the core GUI being there, but not the pages associated with the FOG configuration page. I would make sure you bypass any firewall/content filtering services you have on your network if you are having this issue.[/quote]

Thanks for posting your fix. This worked for us too!

Found this gem while researching more over the weekend:
[url]http://fogproject.org/forum/threads/cant-view-fog-configuration.10756/[/url]

The site I was assisting with the FOG installation did have lightspeed running and it was blocking the contents of the page from loading. Setting an exception in lightspeed fixed it instantly. Thanks for all you guys do!

Update. Client will now boot successfully after running the startup repair utility from the windows 7 install disk.

o_O

Ey3

What is in the file:

/tftpboot/default.ipxe

A similar thread to this seemed to die - if these are broken, the wiki should be updated with that…

Hey, konw I know lots more about fog than i used to know, and i use it since 0.30 or so 😉

So here is just a feedback : you were totally right !
The problem causes now very low speed while imaging on some machines ( record : 22 MB/min !!! ) and as soon as I connect the machine on another switch, the speed increase frankly. I’m not victorious because I didn’t isolate the faulty swith ( there are many interconnected … ) even if I suspect one ( but reboot it doesn’t change anything.
So I don’t bother you and ask more as it is clearly a network issue and not a FOG one, but when I found a solution ( I hope so … )
I will post it here …

Thank you again !

No idea ?

[quote=“Julianh, post: 39299, member: 24986”]I had this, drove me nuts. Believe it or not the solution was to do a “fast wipe” of the disk before imaging down.

Hope it helps[/quote]
I’ll be avoiding Black Friday crazies and tossing together a test fog server at home instead. I’ll give this a shot and post my results. DarkEnergy, i can’t even image the same system I did an upload from

We found the Problem, see here:

[url]http://fogproject.org/forum/threads/clone-upload-fails-with-invalid-partition-data-error.11594/[/url]

Delayed start tried, but no joy there either I’m afraid.
I’m going to go through the guide and start fresh with a new, simple image, despite it working fine for the last few years. Just to make sure nothing on the machine could be interferring with anything.
Failing that I might have to try a completely fresh install on a new server hard drive. Something somewhere is stopping the machines from talking to each other since updating.

Thanks

James

I’d actually tried Yumi but must have only used the Syslinux ISO access. It worked with the GRUB access. Thanks.

Probably not worth it to use PXE if I can’t use the router’s DHCP.

Thanks.