@alireza
I suppose you’d mount the ISOs for those as read only using the DBAN example I mentioned in the other thread, and then locate the kernel and init, and just chain to it using the fog boot menu.

@Uncle-Frank I remotes in with Joseph last night. We fixed the issue. Basically he had a link in www and www/html. They both pointed at each other which was causing the problem.

@Tom-Elliott said:

You are running legacy client, so you would have to update all of the clients to receive these new configs?

set the interval for checkin
reinstall the legacy client on a computer.
copy C:\Program Files (x86)\FOG\etc\config.ini
push that file out as an update…

There is an option here:
Service Configuration -> Client Updater

This area will allow you to push out the new config.

@mike4realz Look through this thread: https://forums.fogproject.org/topic/5998/new-server/5

The senior dev posted commands to set the permissions correctly.

Beyond this, we need details… like OS, Version of FOG, and any other relevant information.

@Joseph-Hales I agree with the plan to solve the thread but not for the reasons you describe, rather for the fact this was likely somewhat related to the issues found earlier.

@Tom-Elliott Almost there actually…The errors mentioned are no longer present; however all nodes show options like server (ie. Multicast,Image/Snapin Replication etc.) and all present “no data to read” when chosen.

Thanks for the hard work, I’ve mentioned it before, but I feel it needs said again. I really appreciate your help.

I’m thinking it was cache related as a refresh got it fixed.

Please ensure that if you are not using resizable image types, that the source HDD for the image is smaller or exactly identical to the destination HDD.

You cannot change the image type and it simply take effect. After changing the image type, you must re-upload.

If this does not work, use DBAN or other boot and nuke programs to quickly “zero” the source HDD, and then recreate the image and re-upload.

I was really strongly wanting to see this thread solved…

I apologize for the delay in this. I am not only managing the bench but am testing the imaging software solutions as well. We have found that FOG will not work correctly for our environment and had to pass on it. There is no problem with the software, it simply does not fit our environment. Thank you for your replies and for the FOG project!

@Tom-Elliott Sorry for the delay in posting an update on this. On a whim, I pressed the “upgrade” option on the system update page to take it up to 14.04. Didn’t really think it would work, but if I’m going to start over, why not try. You were right. The newer version fixed the problems I was having. Downloaded the latest trunk version, and we’re off and running. Thanks again

@Rusty Great to hear that you got things sorted. I am marking this solved for now. You are more than welcome to post a more detailed article about this here. Or get in contact with us so we can add this to the wiki! Thanks.

@OvandHo Issue solved?

Marking this thread solved as I’ve tested netbooting virtualbox with version 5.0.0 and there seams to be no issue. Problem probably with older versions of virtualbox.

hmmm, maybe this was an issue with a previous svn. i just made a test iamge and deleted it and it was removed from the disk.

problem solved 🙂

@Asthea I have it working right now. Thank you everyone for the assistance. I have no idea if the fetch command is even needed. I will test with it out and continue to clean it up. But I am grateful that it is working. Hi-5 all around.

:UBUNTU kernel http://${fog-ip}/fog/service/ipxe/ubuntu/casper/vmlinuz.efi initrd http://${fog-ip}/fog/service/ipxe/ubuntu/casper/initrd.lz imgargs vmlinuz.efi boot=casper vga=normal root=/dev/nfs netboot=nfs nfsroot=${fog-ip}:/var/www/fog/service/ipxe/ubuntu/ fetch=http://${fog-ip}/service/ipxe/ubuntu/casper/filesystem.squashfs initrd=initrd.lz locale=en_US.UTF-8 keyboard-configuration/layoutcode=us mirror/country=US boot || echo failed to boot prompt goto MENU

I’ve seen this happen too at work.

I was messing with the grub exit style though. It only happened once.

Good morning, Tom. The .msi file for Google Chrome is roughly 43 MB. Although I did follow the wiki on editing the php.ini file and increasing the “memory_limit”, “post_max_size”, and “upload_max_file_size” to 1900 M.

Could I have screwed up the php.ini file and it’s causing this issue somehow? I (of course) didn’t make a backup before editing it, but i’m sure I can find a default, out-of-the-box php.ini to replace it with.

Providing a link in this thread for future readers to a similar problem on a later revision: https://forums.fogproject.org/topic/5928/r4930-fedora-21-unable-to-ignore-mac-for-imaging

@Hanz Glad you got it fixed.

For others future reference, This command:
SELECT hostID from hosts WHERE hostID NOT IN (SELECT hmHostID FROM hostMAC WHERE hmPrimary=1);

can be changed into a command to delete all that it returns by simply changing select to delete like this:

DELETE hostID from hosts WHERE hostID NOT IN (SELECT hmHostID FROM hostMAC WHERE hmPrimary=1);