unless you installed a 2nd FOG server, then you have no other storage nodes. A storage node in FOG is another FOG server running in (S)torage mode.

If you just added a new disk to the existing machine, you’re only about halfway to adding more storage to FOG.

Well, It says “free space: 94%”.

I am about to reinstall a new server so, it should resolve my problem.

I think there is another spot in the php.ini file that needs to be updated. Also, FOG keeps me logged in for days if I stay at a screen that refreshes itself, like the home page showing the bandwitch graphs, or the active tasks screen.

If I leave it on something like the hosts listing, it times out after a few hours.

Ooops !

My problem is solved… It was a password problem.
Before my post, just to be sure, i resetted all passwords :

fog linux account vsftp fog account fog settings (other information folder)

But i forgot to reset the one on “storage management”.
Maybe this can help others too !

Now, all seems to work just fine.

Sorry for bandwith…
Patrick

You’ll have to install and configure DHCP server on the FOG server if you want to image from an isolated switch. Basically, when you install FOG, say Yes to DHCP, the defaults should work for an isolated switch.

I have successfully imaged and deployed windows 7 pro 64 bit. I did nothing different than 32 bit, because FOG doesn’t care about the 32/64 bit part of the OS. Fog does have problems with OEM hidden/recovery partitions, so I either install fresh or use gparted to remove that partition and recover the space.

I do not use FOGPREP or SYSPREP before I image. I do sysprep early on during the image creation process, but only to copyprofile. I then finish installing programs and changing settings, then remove from the domain and upload the image without sysprepping or fogprepping. Most of the time, I don’t even have to chkdsk or defrag.

The one thing I do is use a mutliple partition - single disk image type because that’s how it got it to work and all machines I image have the same size or larger HD as the one I took the image from.

FOG is free and we are all volunteers on the forums, trying to help when and where we can.

Depending on the type or problems you are having will probably determine what you want to backup and what you want to discard.

You can export most of the host, images defs, group, and other information from the database. You can backup your /images directory to another location, and you can copy your .fogsettings file so you know what you chose during the install.

look at the column names and the values for user. Make sure you are specifying the correct column name and value for uName.

If worse comes to worse, use something like phpmyadmin or NaviCat lite to edit the values using a GUI.

open your dhcpd.conf file and make sure you updated the “next-server” line with the new IP of the FOG server.

there is a WIKI article explaining how to do what you need. There are also many threads explaining how to do this command by command. Use the search feature and you’ll probably find it quickly.

I have experienced the same problem, besides, a username and a password didn’t appear when finishing the Storage Node installation.
What I did to get it working is to change the password in the Storage Node at the /opt/fog/.fogsettings as well as in the main FOG server at the WebUI -> Storage Management -> All Storage Nodes -> “Your-Storage-Node” -> Management Password, so that both match the local user’s password. I can’t say if it is the Storage Node’s or the main FOG server’s local user, as I have the same password in both machines.
I think it is the same solution as wpsd’s, but instead of changing the local user’s password to match the one at .fogsettings I have changed it in .fogsettings to match the local user’s password.

I’ve seen reboot=bios solve some cases of machines failing to reboot after completing the image task, but I’ve had better luck with reboot=pci.

I tried again using multi-partition, all disks and it worked. Unfortunately, I need to fit this on a couple of machines with smaller disks. Too bad I didn’t build the image on one of those machines. Is there anything I can do?

Overall I would prefer to be able to use resizable mode. Any thoughts on why that didn’t work?

I figured it out. went into fog setting through the web management and changed the TFTP password from there and everything started working fine.

NOTE: I HAVE fixed the issue myself. Turns out I forgot to set the fog server as a dhcp server as well! oops…

[B][SIZE=7][COLOR=#ff0000]case solved!!![/COLOR][/SIZE][/B]

Look at: [url]http://www.fogproject.org/wiki/index.php?title=SVN[/url]