[quote=“Thomas Rucker, post: 40196, member: 1970”]So, it’s not the GPT or MBR, but FOG has a limitation, because of how Lenovo loads their machines.

I guess I have to live with the RAW image then, correct.

I have to say, it works very well, but it’s very slow, thank you for your thoughts.[/quote]

If you have 6 primary partitions it’s GPT.

[url]http://en.wikipedia.org/wiki/GUID_Partition_Table[/url]

Still did not work. What is odd is that the image was working just fine until I set up fog correctly for renaming the computer and joining it to the domain. Kaspersky is not even attempting to install. It just skips right over it and goes straight into windows. I am at a loss. Need a day to think.

Thanks, that seems to have fixed it.

Since Fog uses several servers and other components that use usernames and passwords, and since it seems that the installation script doesn’t set them all correctly, is there any documentation for Fog that explains how to set them all up correctly?

Hah! I tried your command and got the error Host is blocked because of many connection errors; unblock with ‘mysqladmin flush-hosts’.

We ran that and voila! Our FOG server is back.

You guys are truly wonderful.

Tom, sorry if this confused you. The initial set up was already tested on local (Ubuntu 13.10 VM) and was working. nothing really has changed besides putting the master Node on a freenas (with FTP & NFS) and giving full control of the loaction to the fog user (which was put as the user to use in the node management on the GUI)

Since then, everything is still working fine, comunication between Fog and the node is fine, image uploads are going to the dev folder then after upload is finished it’s being transfered to the main /images folder. the ONLY issue is whenever we try to proceed a download from the host management page, it fails automatically giving out the error I posted above. BUT using the quick download from the host list in task management works.

Do you need more information?

Linux beginner here; While I have been using FOG for about 3 years now, messed up and fixed several things using your forums, I have what appears to be the same issue mentioned above. I can go into the webpage and force the images to happen and they work just fine, otherwise even though no other images are actually in progress they will sit and display “Waiting for a slot, 0 PCs are in front of me. (x min)”

What do I need to do to look at the mysql database and check these entries? I apologize for my newbiness ahead of time. Just can’t seem to find the answer to editing the database, and appreciate wonderful UBUNTU commands and ideas to add to my ever growing understanding of UBUNTU.

Running .32 still on UBUNTU 14.04

Thank you.

Because the OOBE experience is actually required for windows to properly adjust to a machine’s hardware, if you want to add software to a windows machine fresh out of the box without even going through with OOBE (which keeps your re-arm count from going to high) I HIGHLY suggest going through with the windows install until asked for a computer name and username, at this point if you hit CTRL+SHIFT+F3 your system will reboot into AUDIT mode, Sysprep will pop up when windows logs in. At this point choose “Enter system audit mode” for the first option and “quit” for the second and hit OK, Sysprep will take a few moments to close and once it’s gone you can do with the system what you will (Drivers, Software, even populating C:/Users/Default/Desktop with any shortcuts the client may need). At this point you can run windows updates (IT IS OK IF YOU NEED TO RESTART YOUR PC FOR UPDATES THIS WILL NOT DAMAGE ANYTHING AS LONG AS YOU CHOSE QUIT IN SYSPREP AS I STATED ABOVE, YOU WILL ONLY HAVE TO REPEAT CHOOSING AUDIT MODE AND QUIT EVERY TIME THE PC RESTARTS) after finishing with EVERYTHING you would like to exist on the computer restart once more, now that we have everything we need we can set it to run OOBE at last, Sysprep will pop up as always under System cleanup action choose “Enter System out-of-box-experience”, and check the generalize box, and for the second option choose reboot and hit OK, the computer will now reboot when the BIOS starts hit whatever key you need to access the boot menu, queue your host to upload the image in the FOG web GUI and boot it to the NIC, this SHOULD pull the image just fine and negate MOST issues everyone seems to be having! Apologies for the multipost…

Since it’s a VM, take a snapshot. Then issue the dnsmasq removal command:

[code]sudo apt-get remove dnsmasq[/code]

See if you can Ping internally, if so test the internet. Reboot the VM, turn off your dhcp service again and see if internet is still available. If any of this breaks your ability to connect to the network, then you need to restore your snapshot and disable both the dhcp and dnsmasq services on boot when you need to connect to your home network.

Junkhacker, thank you! I didn’t even think about this. I had it bound to the 10.x.x.x address. Changed to the 192.168.x.x and the FOG menu is now booting.

I swear i had switched this earlier and tested, but apparently it did not save the change (please read: [U]I[/U] failed to save the change)

did you try changing the linux password for the user “fog” and setting the storage ftp password to the same?

That worked! Thank you very much!

[quote=“Tom Elliott, post: 39810, member: 7271”]Also,

Maybe try:

initrd http://${fog-ip}/fog/iso/clonezilla/clonezilla.iso
chain memdisk[/code][/quote]

This works! It appears that memdisk ISO is not necessary and causes the squashfs errors. I have tested this on clonezilla livecd and parted magic livecd so far and will report back if run into problems with other livecds.

Thanks for your help and I hope others find this information.

UPDATE! It works!

Turns out the issue was all of my ISOs after all. Somewhere along the line of transferring them via ftp from my windows IIS server the data ended up being cut off; which I assume is why the “MEMDISK: Image appears to be truncated” message was there.

This is what happens when I try to cut corners on a terminal-only linux box… 😞

Thank you for your help, and sorry to be a bother.

It’s working with the latest SVN version, thank you very much!

It was indeed not having partitions on the drives and on some computers the SATA cables were in different order than other drives. After following your fdisk drive and making all the computers have the same SATA order everything worked.

I went one step further and copied the partition layout and size byte for byte during fdisk of a working computer. I wasn’t sure if that step was necessary, but it worked nonetheless.

Thank you.

I believe I found the culprit. I noticed that the USB 3.0 drivers were missing and after installing those and reimaging, everything seemed to work.

It was still odd that this only happened after registering the computer to FOG though. The keyboard and mouse were these: [url]http://www.newegg.com/Product/Product.aspx?Item=N82E16823129036&cm_re=cm_storm--23-129-036--Product[/url] . They have back lights, but other than that nothing special.

I don’t know what you mean, “why fog not accept the same usr and psw when i select “quick image ?””

The only password that matters for the “login” is the GUI username and password. If it’s not accepting it, then something is either misconfigured, or you’re typing a wrong character. My guess is a key that you’re using as your password is passing incorrectly as my guess English is not your first language?

[quote=“Ashley Rimmington, post: 39862, member: 27226”]Sorry for the misunderstanding on my part! Glad to say it worked like a charm!
Thank you so much for your help guys. 🙂

Just a thought here:
Might I suggest making this a part of the default install for a windows environment install? I say this because my server is available for me to configure (which made me think that the link above didn’t apply since mine wasn’t “unmodifiable”) but when following default install procedure the system didn’t work in the end. With this dnsMASQ setup it works beautifully though!

It just feels to me that this may be a required step for a windows server based DHCP setup.

Thanks again![/quote]

You are quite welcome!

But not necessarily true. Every environment is different. Most have the ability to edit the DHCP scope and have their file delivered correctly. Sometimes users don’t have access to the DHCP Scope because it is managed by someone else, or a third party and this is where DNSMASQ shines. Sometimes the file is not delivered completely and DNSMASQ helps to resolve the issue (I suspect this is the issue you actually faced.)

A Further problem I see, is that Ubuntu 12.04.4, 12.04.5 and 14.04, 14.10 have started including dnsmasq-base in the installation to help with dns resolution. This is a poor decision by conical, IMHO, and has lead to issues with installing and starting DNSMASQ. This would lead to causing FOG installation to fail unless you render your internet useless and try to install FOG… no wait FOG needs the internet to download modules for installation, this sounds bad already 😕

What I think was happening in your environment, is probably what is happening in mine. The file was not being passed entirely and DNSMASQ has helped to resolve this issue. I think DNSMASQ would be a good default module to install with FOG by asking a few questions and creating the file according to the responses, but having FOG install DNSMASQ and use it by default could be nasty and ugly.

I’m glad DNSMASQ worked for you though 🙂

Partition one is your Windows system, partition two looks like it’s the start of your linux system, but what volume is partition actually formatted in?

First things first,

How is this fog’s fault? What I mean, if you put the Video card in and the system can’t boot network, wouldn’t that indicate there’s something wrong with the motherboard? There’s nothing I can do for that.

Second,

When you task the system, does it perform the tasking and you just can’t see the information? I mean, that would indicate a kernel driver problem, but seeing as the problem (seemingly) starts before this, it once again leads back to the system motherboard of video card being problemattic. If the case is that imaging tasks and such actually are operating, I’ll request that you attempt making a custom kernel, but from the information I got from this very short post, this probably isn’t going to fix the problem.