[url]http://en.community.dell.com/techcenter/os-applications/w/wiki/2545[/url]

So, good news on this…

We were eventually able to image the system (probably luck), but we wanted to change something on the image and upload a new one.

So, we made our changes and tried to upload again… it just wouldn’t work. Kept saying failure 0 or something… I think it’s HDD related. We messed with this for quite a bit, and I decided to update FOG because Tom said he changed how hardware was detected in the latest svn.

We’re running r3277 now and it started uploading on the 1st try.

Should be.

You’ll need to re-install and just choose DHCP this time.

There is an answer file somewhere that the FOG install script uses, it’ll try to pull answers from that.
You might need to delete that file. You might want to try modifying it first.

To use DHCP, change that option from 0 to 1

Here’s an article saying where the answer file is: [url]http://fogproject.org/wiki/index.php/Upgrading_the_FOG_Server[/url]

Indeed it did the second time I rebooted the machine it’s on. Thanks!

I know this is a bit old but I just wanted to send off a “Fixed my problem” message. I had moved my /images from a directory on the root partition to a new larger partition mounted to /images. When I made the cp -a it did not, for some odd reason, copy either of the .mntcheck files in /images or /images/dev. After creating and setting permissions on those two files everything started to work again. Thanks much!!

Nice, thanks! I didn’t know that setting existed. Everything loads okay now.

What do you mean?

FOG Doesn’t magically delete files from the system. There is the slight potential of losing [b]AN[/b] image based what we can tell on the size of the file and the length of time it takes to copy the old and the new back over. But it would only delete the image that you are currently working on uploading anyway. FOG does not randomly delete images from your server. The few things I can think of,

First, the /images is not a local disk system on the server but rather a mounted disk that mounts to /images, potentially by a USB connection. Maybe the USB lost access due to standby? This would cause the mount point to no longer exist which would appear as if your images are lost.

Second, the /images is local but there’s a problem with the main drive it’s loaded on? It stops being able to be read, which would give the impression of the drive no longer existing. This would assume you have two hdd’s on the system, one that’s hosting your OS, and one that’s dedicated to your images.

Ah ok I understand now - brilliant this has resolved the issue I wasn’t aware that specifying the default OU would have a knock on effect.

Thanks again for your help

They are non-impacting. Ignore them.

Those DB commands are related to upgrading from much older versions of FOG, for backwards compatibility.

So yeah, you’re ready to get Fogging.

Yes, if I go to /images it takes me to the mounted /images volume.

Ok lol, sorry

Yes, the machine I am using to image is an Ubuntu Desktop 14.04 and machine that is being imaged is an Ubuntu Server

The file is here: /etc/dhcp/dhcpd.conf

Here is my reference: [url]http://askubuntu.com/questions/221329/how-do-i-configure-dhcpd[/url]

If FOG has configured DHCP for itself, it’s almost surely correct. Also, if FOG is doing DHCP, you only need option 67 configured for it, which should already be done.

Please do a TCP dump on your FOG server.

Taken from another post by Uncle Frank:

[CODE]sudo tcpdump -w issue.pcap -i eth0[/CODE]

You might need to change the interface name in the above command, seems like I have never had an interface named eth0 in Linux… This command will list all available interfaces. Pick the right one.
[CODE]ip link show[/CODE]

Run the above capture command on the FOG machine, then start the remote target host. Wait till it fails, then stop tcpdump (ctrl+c), transfer the PCAP file to your PC and examine it using wireshark. After the capture is completed, please use the MAC address of the target host as the filter for sender & receiver. This address will filter out ALL traffic that isn’t coming from or going to the target client.

Example Filter (change the MAC addresses):
[CODE]eth.dst == 00:0C:CC:76:4E:07 || eth.src==00:0C:CC:76:4E:07[/CODE]

Please also post this PCAP file so we can look at it and see what’s going on. And if you don’t filter the file for us, we will need the target host’s MAC as well so we can filter it.

#LetsMakeScripts

Looks like installing the SVN the first time when it added MySQL Connection Type: MYSQLI_ASYNC to the .fogsettings it corrupted the entry for sqluser placing the local host in that place and losing a semicolon. Fixing that and restarting sql fixed it. This is the threads that lead me to it [url]http://community.spiceworks.com/topic/564935-fog-database-error[/url] and [url]http://fogproject.org/forum/threads/fog-is-inoperable-after-server-reboot.11460/[/url]

I solved the problem by creating missing task* tables using a new instalation db as example, worked like charm. Would be great to have sql code to regenerate tables in case of this.
Thanks for your time and advice!

[quote=“SalvadorGilbert, post: 45503, member: 29401”]Hey guys!

[FONT=arial][SIZE=13px]Are there any free or paid devices which can repair SSD bad sectors or, some way or another, read the data in these bad sectors during a clone/image/recovery process?[/SIZE][/FONT][/quote]

[url]http://lmgtfy.com/?q=Recover+data+from+SSD[/url]

Try that.

Hi Jimmyboy, regarding the docker container you mentioned: Could you please have a look at [url]http://fogproject.org/forum/threads/create-a-docker-container.12747?[/url]

Hello people!

Recently I had a similar problem. My FOG solution is:

FOG version 1.2.0 revision 3246 Ubuntu Desktop 13.10 i386

Working with Hosts Management section, creating a host, erasing this host and again creating the host with same MAC I had the trouble that FOG said me that this hostname already exists. In the Host Management section did not appear the host.

The solution is like Tom says. Thank you Tom!!

For me, deleting the registers in fog database with the [I]wrong[/I] host ([I]wrong[/I] means the created, then deleted and then tried to create) in [I]host[/I] and [I]hostMAC[/I] table was the solution.

I searched how to manipulate fog database. I used phpMyAdmin (searching directly with Ubuntu Software Center). Then I configure to get access to the fog database (I used blank password in mysql). Edit /etc/phpmyadmin/config.inc.php
[INDENT=1]Uncomment this line:[/INDENT]
[INDENT=1][COLOR=#3366ff][SIZE=4]$cfg[‘Servers’][$i][‘AllowNoPassword’] = TRUE;[/SIZE][/COLOR][/INDENT]
[INDENT=1]Save file.[/INDENT] Finally, search the tables [I]host[/I] and [I]hostMAC[/I] and delete the [I]wrong[/I] host registers.

I hope it helps. See you,

T. Capablo.

I doubt that OS update is changing file permissions in /tftpboot or /var/www but hey, you never know… 😄

updates use the settings you chose the first time you ran the setup and reuses the same password