Could have been the kernel – but what I ended up doing was a clean install of 1.0.1 – and all is working well with the newer devices. Just have a few path issues to work out since I have the images folder on a separate drive.
Thanks.

I have updated the wiki to avoid further confusion. The 192.168.1.1 that you chose at the beginning of the install IS the ip you want to use, not 192.168.1.5.

Make sure to put
[QUOTE][FONT=monospace][COLOR=#000000]/fog/management[/COLOR][/FONT][/QUOTE]
after the ip or you will just get a “It works!” page from Apache(the web service).

the ghost boot image.

We used ghost and i discover fog, and we migrated. but we have 250 images to transfert (and fog don’t allow to make usb restauration key) and i need to load first in ghost to create image in fog after.

That did it. I did set a different mySQL password other than the default and I forgot to go back and change it in there.

Thanks so much.
Andrew

do you have a bluetooth device plugged in to this computer?

Okay, here’s my crude but functional workaround…

Since I figured the problem is that the mysql service was being locked out of a file it needed, and restarting the service completely fixes the issue, I changed my Ubuntu server to stop and start the mysql service after boot up. Fairly simple procedure, just do the following:

[CODE]sudo nano /etc/rc.local
[/CODE]

In this file, above “exit 0”, type “service mysql restart” (no quotes).

Ctrl X to exit, Y to save, Enter to save to same file.

From that point forward, every time your server reboots, it will automatically bring down and up the SQL service, solving the “Unable to connect to database” error.

Hope this helps someone out there, let me know if anything is unclear!

the kernel refers to a part of the fog system that is used for creating and deploying images. fog uses a 64bit kernel now, for hosts that support 64bit. this does not require any changes to the hosts being imaged.

unfortunately, the easiest way to do that would probably be directly in the database. fog database, hosts table, hostKernel column, i think
(i use phpMyAdmin for these kinds of tasks, but someone better at command line stuff could probably tell you how to do it with a single command)

Yeah I have had experience even with the same manufacturer of hard disks being just a little bit off as well and had to send them back.

the error is just telling you that it failed to load the driver for a device you almost certainly don’t have in your computer. the first “error” has nothing to do with the next problem.
what version of fog are you using? (an svn release, 1.0.0, 1.0.1)
what kind of download task did you use? (unicast or multicast)
what is the image type?
the more details you give, the more likely we can help you.
btw, those links are not work as direct links to images.

Glad you got it working.

Merci 🙂

You can use the debug mode of FOG to issue some commands and actually use linux tools to delete and create partitions.

In this guide I create ntfs partitions on old linux hard drives so I can image them with Windows 7.

[url]http://fogproject.org/forum/threads/quick-format-to-ntfs-with-fog-for-noobs.10349/[/url]

You can do something similarly if you like by issuing commands to format the drive in fdisk.

it works thx. on 14.04 it didn’t work.

Greez

We continue to face hurdles, but 12.04 with FOG 0.32, grub (not grub2) seem to work with DL360e Gen8, although we now have to figure out how to avoid eth0 disappearing after cloning.

Did you install the DHCP form the install script? If so, rebuild your server NOT using fog as the DHCP server. I can only assume that some settings are clashing.

If you want to have FOG dole DHCP that is fine but you won’t need DHCP.

If you want to use DNASMASQ to leave your DHCP setup alone and pxe boot via proxy dhcp, don’t install the dhcp, the two will clash settings.

We would be willing to help you to troubleshoot your issues, but you need top choose a path and stick to it. I would start by commenting out the line
“pxe-service=X86PC, “Boot from network”, undionly” some networks don’t need to be told to boot, and some do.

Are you not able to edit your DHCP settings to include your FOG server and Boot file name?

Hi[URL=‘http://fogproject.org/forum/members/wolfbane8653.3362/’] Wolfbane8653[/URL][I], please disregard. i did a fresh installation in Ubuntu 14.04 and is now working perfectly. [/I]

Sorry, I missed your signature, but I just tried now but sadly I still have the issue. Thanks for your effort; however, I’m going to have to call it a night now.

Cheers.

PS - We didn’t get the issue with 0.32, but sadly it doesn’t support ext4.

I figured out what I was doing wrong. I had the wrong operating system set in the image management portion of the webpage.