We have Two raid in our server, 1 for Ubuntu and 1 for the images.

We just create a link between /images and our storage raid.

And it work really fine.

Can you attempt putting it into Bridged mode.

Host-only, as I understand it, makes the device as if it’s going through the host machine. This sound’s like it’d be a good thing, except the VM still has to process the information as if it is its own device. So, when you choose Host-Only, the device suddenly becomes processed by two CPU’s.

It’s just a theory and one that I think deserves a good ol’ college try!

Change out of host-only to Bridged NIC and maybe things will work better?

When I was changing the folder name it was giving me an error. The name was not getting change.

Yes, I have the fog client installed on both images I have. I have the correct server IP address and hostname changer is enabled. I’m not sure what the fog.log has in it. Tomorrow I’ll try to deploy an image to another machine and see what the fog.log file says about joining.

I’m confused.

Have you tried uploading an image?

That seems to have fixed the GUI. Thanks!
Only problems I see now is that under the active directory settings when I put in the encrypted password and tell it to save. After saving the settings the encrypted password changes to a much larger string that does not resemble what I entered.

me helped booting from dvd and doing a chkdsk (is not the same as doing it from a booted operation system

[LIST=1]
[][COLOR=#000000][FONT=Arial][SIZE=15px][COLOR=#000000][FONT=Calibri][SIZE=13px]windows 7: boot mit windows 7 dvd - bei language / time / keyboard weiter - repair modus - system recovery options - next - [/SIZE][/FONT][/COLOR][/SIZE][/FONT][/COLOR]
[][COLOR=#000000][FONT=Arial][SIZE=15px][COLOR=#000000][FONT=Calibri][SIZE=13px]bei windows 8: boot mit windows 8 dvd :language / time / keyboard weiter - repair modus - erweiterte optionen - Eingabeaufforderung[/SIZE][/FONT][/COLOR][/SIZE][/FONT][/COLOR]
[*][COLOR=#000000][FONT=Arial][SIZE=15px][COLOR=#000000][FONT=Calibri][SIZE=13px][/SIZE][/FONT][/COLOR][/SIZE][/FONT][/COLOR]
[/LIST]
[COLOR=#000000][FONT=Calibri][SIZE=13px]command prompt [/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Courier New][SIZE=13px]chkdsk d: /f /r /x[/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Calibri][SIZE=13px] (because c is the 100MB Partition)[/SIZE][/FONT][/COLOR]

Greetings Michael[COLOR=#000000][FONT=Calibri][SIZE=13px][/SIZE][/FONT][/COLOR]

An update for those viewing this post. Tom Elliot has advised me that we now see just the bandwidth info for the node selected in the disk space piechart. So bandwidth information is no longer shown for all nodes at once.

Some more questions :
When I use the recovery disk and I look at the size of the partitions, the primary partion 0 is 449 GB when I do a list volume with Diskpart. However, during the deployment of that partition from FOG, which is indicated as /dev/sda4, the Device size is indicated as 482.2 GB.

Furthermore, the recovery fails on both the recovery disks I made on the two separate Laptops. So not sure if we have a disc failure. It resets until about 78% and then just stops saying there was an error. On both repartition and just restore files.

Hey there,

sorry for letting you wait this long. Today I found some time to test a little bit and things look a lot better meanwhile.

I did another fresh install from the current svn and now the iPXE boot works without any flaws! I will now test to Up- and Download some images. I will keep you up to date!

See my previous post.

Can you upload your fog install log? It is located here:
[CODE]/var/log/foginstall.log[/CODE]

I got the same issue - but unfortunately, creating a new image and pulling it from the client does not work either. It is just going through the check stuff and reboots the client.

System Ubuntu 12.04
FOG 1.2.0

Still the same error ;(
root@v1fog:/images# service nfs-kernel-server status
nfsd running
root@v1fog:/images# ufw status
Status: inactive
root@v1fog:/images#

Update: This is resolved.

There were 2 issues:

I had the wrong mysql username/password in Config.class.php on the nodes. During the node install, I had given it a generic root account but found out earlier today that I specifically needed the username/password for storage nodes, which I found under the storage node section in settings on the main server.

Second: I realized the nodes couldn’t even connect to the main database, and I was able to narrow that down to the my.cnf file on the main server. It had the bind address set to 127.0.0.1. I commented that line out, restarted mysql, and then they were able to connect.

After I verified everything was talking correctly, I restarted the FOGImageReplicator service and everything instantly started copying. The fogreplicator.log file on Node1 shows Group #2 as I expected it might.

This also fixed an issue that I never really cared about enough to fix… On the main fog dashboard page under disk information, It always told me “Failed to connect to” when I selected Node1 or Node2. that’s fixed now and I can see the disk usage for them.

Thanks for the help!

Turns out the problem is with the dc7900 and ipxe. It looks like according to [url]http://www.fogproject.org/wiki/index.php/WorkingDevices[/url] page that there is a known problem with the dc7900. We have a high percentage of those around here yet, so I’m just going to back rev to .32 until I can get the ipxe thing figured out on the dc7900. The other site had dc5800s and Optiplex980s which both worked fine with 1.2.0 I was able to get the 800 G1 to go fine with the 3.8.8 kernel.

Is there anything showing in your apache2 error log when this client tries to connect?

Stop the fog service on the client
[CODE]net stop “FOG Service”[/CODE]
Follow the apache2 error log via a terminal to the fog server:
[CODE]tail -f /var/log/apache2/error.log[/CODE]
Start the FOG service:
[CODE]net start “FOG Service”[/CODE]
Watch the error log, if any entries show up, please post them here.

Sorry, meant to get back to you sooner. The kkpxe didn’t change the situation. I just upgraded to 1.2.0 today and noticed it set the menu back to the original… so I had to go in and edit the file again. Glad I posted here, made it a lot easier to re-locate it. 🙂

Something with the video chip in these 320s just doesn’t like that bg.png file… I can add a video card to a 320 and it works fine. The built in video appears to be the problem.

Great, thanks again. I saw an older thread about automatically associating the pending MACs with a host, so you don’t have to open each host and click + to add the wireless MAC.

Is that actually possible and/or could you point me in the right direction? Because it seems like it would be a time-saver…

Thanks,
D.L.

It’s OK