Upgrade to 1667 and let me know if you still have issues.

Thank you,

[quote=“Tom Elliott, post: 26911, member: 7271”]That is correct.

Sorry I didn’t get a chance to be of assistance, and I will have to create a WIKI to add these minor changes.

XZ requires a small portion of encryption.[/quote]

This is my procedure for changing that file.

cd /var/www/html/fog/services/ipxe xz --decompress init.xz mount init ./tmp -o loop -rw cd ./tmp/tmp touch resolv.conf echo “nameserver 8.8.8.8” > resolv.conf echo “nameserver 8.8.4.4” >> resolv.conf cd …/… umount ./tmp xz -z -9 -C crc32 init

I then told my test bench to reboot in debug mode through my Fog server. The machine shutdown windows and rebooted me to a Linux command prompt. Although the link for resolv.conf was in /etc, the file I created in /tmp didn’t exist. When I tried to ping google.com I got the response “ping: bad address ‘google.com’”. After I ran though stops 4 to 6 from above while in the debug console my “ping google.com” then ran successfully. Next I tried rebooting the debug console to see if the resolv.conf I created in the debug console was still there… no luck. 😞

-Craig

Is MySQL running? If no password is set my guess would be that MySQL failed to start for some reason.

My guess, as to the particular issue herein, is that php-mysql is not the correct file to be installed. Check the lib/ubuntu/config.sh file and change the references of php5-mysql to php-mysql

I don’t know if this will work then.

Host Primary Disk, is telling the system what DEVICE to look at. Device labels in linux are /dev/sd[a-z] or what not.

Partions are what usually labeled as /dev/sda1 /dev/sda2 etc…

So in the most literal of senses,

You’re telling the system to look at DEVICE called:
/dev/sda1,

The FOG System is going to try looking for a partition on /dev/sda1 as /dev/sda11

If you created the ubuntu VM without a swap partition, that would explain MySQL faltering (assuming it’s running out of memory). The mysql logs under /var/log/mysql will help more than my best guess though.

When using Centos during centos install select basic server.

I will try that and let you know what happens. Thanks.

Found solution, Dell 5000 series uses same kernel as 3000 series. To put it short Dell 3440 worked with this solution 32 bit kernel!@
[url]http://fogproject.org/forum/threads/dell-latitude-e5440-fog-32.10267/[/url]

Yes this is very possible with fog. Fog even has the ability to function as the DHCP server. I don’t recommend using it as the DHCP server unless you intend to use fog off the main network or you plan to disable the DHCP server temporarily while you image.

If you have sites that you want to keep linked together and use the same images at your other site… You can also set up FOG as a storage node. This will allow you to have multiple servers in locations that can synchronize with your central server to get images for the networks they are attached to.

Thank you both for your responses!

Wiping the system and installing Debian 7.5 allowed the FOG 33 1.0 SVN install to complete without incident.

Found where I needed to plug in the mysql password to get the database connecting, and have the schema installed so I can get in and get started with the program itself. I’ll test it out in the next couple of days and see what happens.

For whatever reason fog needs to be connected to the internet or you will get that error. since I have sonicwall doing dchp it doesn’t support option 66 with IP address only hostname.

Since I had to image using fog dhcp I removed the PC and server from the reset of the network… It didn’t like that.

Once it began copying the image I connected it back to the rest of the network with internet access and it didn’t have issues anymore.

Good post. I ran 0.32 under Debian 7.4 for a while. I did have to do the first three modifications, but I never ran into the ‘Unable to Mount NFS Volume’ issue.

That being said, after I switched to Fog 1.0.0 and did a clean install, I did not have to make any modifications to get it to work. So good news for Debian users as we move forward.

downloads of partimage format images are supported for backward compatibility, but all uploads are done in partclone format. partclone uploads can be sped up by reducing the compression level on the settings page.

// Proxy
if ($Proxy)
{
$ContextOptions[‘http’][‘proxy’] = ‘tcp://’ . $Proxy;
$ContextOptions[‘http’][‘request_fulluri’] = true;
}
This what line 3506 looks like in /var/www/fog/commons/functions.include.php

[quote=“falko, post: 26602, member: 48”]Just wanted to chime in and say I install windows 7 as default from disc (ie. 100mb partition + Second partition as OS) and for years I have always used [I][SIZE=12px]Windows 7 image that was "Single Partition (NTFS Only, Resizable). [/SIZE][/I]

[SIZE=12px]Never had an issue[/SIZE][/quote]

I’m also to guess that you were sysprepping/generalizing your images first?

My init.gz fixes the problem for 0.32, if anyone else needs a copy send me a message.

thank you, this helped… now I do have the problem that the machine is not booting into PXE… I will look up the forum and wiki…

I just wanted to add my findings to this thread. Ubuntu 14.10 fresh install, fully updated, downloaded Fog .33b via svn. I got this error repeatedly until I installed it from my user account and not the root account. So if you have enabled and are using the root user via being logged in, it can give this error. Took me WAY to long to figure it out. I don’t know why as I’m not a Linux user but that was my solution.

Updated bios to A18 on those and still same issue.