Is there a way to have the .fogsettings file update the parts that have changed since my last install like the storage location?

Just curious to see if I can reduce the things I have to check before updating to trunk.

Awesome, thanks I am up and running again. Glad it wasn’t something I did.

Hmm… I am thinking I should have reformatted this external Drive. It is formatted with NTFS and the chmod isn’t taking.

I am going to go out on a limb and make a suggestion. If you can use the same image in a different LAB and the FOGService is able to connect then you should compare the Network path between each Lab to the FOG Server. It sounds like something is different.

Okay so I had to do a combo of Way 1 and 2. I had done Way 1 yesterday when I updated to 3431 per Tom’s forum post. Then to fix the issue that 3431 caused I updated to 3432. Since I didn’t check immediately not sure if the password never took in the Storage Node or not. I repeated Way 1 today then checked the Storage Node in FOG and found that I had to manually change the password there. Maybe you need to stop and start a service in FOG after changing .fogsettings?

Anyway it is fixed.

Refreshing with Shift+F5 did not work. Just for transparency I did what Tom said and that fixed Apache. I did not do what Wayne suggested.

Per a chat with Tom, here is a picture of the output of fdisk -l from my Test system in Debug Mode, with one of the non-functioning Images tied to it.

Tom has fixed the issues and I am 100% up and functioning

@mmiat What FOG version are you running? What Linux Distro? Where are you getting the error above? i.e. are you getting to the normal FOG Boot Menu then choosing Advanced Menu fails?

I had this happen and had to restart mysql.

I think the command is: sudo service mysql restart

I will update to the latest SVN.

I have a generic syspreped image that I use for my imaging and as I said everything was fine before I had updated FOG, I didn’t need to add anything extra.

I am running SVN 4290 on Ubuntu 14.04.

I was running svn 35?? and not having any issues. Two days ago I updated to 4290 and the two systems I have imaged since required me to go into Disk Management and expand the main partition.

What do I need to look at to fix this?

Is there a way to have the .fogsettings file update the parts that have changed since my last install like the storage location?

Just curious to see if I can reduce the things I have to check before updating to trunk.

Is Sourceforge backup? Just want to check as I am still getting the same error as above and want to make sure it is not me.

Okay so I set the default Kernel to 3.0.1:

But now I get this when I try and do a New Registration on teh Win 8 VM:

I have the Virtual Drive set to IDE should I try SATA?

How do I check that it is in fact setting it to default.? The FOG Configuration Screen shows 4.0.4 as the Default Member and none of my Hosts have the Kernel set.

I see where I can download older Kernels and where I can assign a specific one to a Host, but how do I tell FOG to use a specific Kernel for unregistered machines?

When I download an older Kernel FOG Configuration doesn’t change and I can’t figure out where to change it.

Just as an FYI, I am having the same Kernel panic issues with a VM and Win 8 that others on the forum are having, but since the panic happens when I try and register the Host I can’t use the Host screen to specify using the 3.0.1 Kernel.

Make sure your permissions are all set correctly and look at this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP#You_must_first_upload_an_image_to_create_a_download_task

@Wayne-Workman That is great! I will try it and see if it works thanks.

That is what I did. I will say I haven’t rebooted in a while so not sure if it worked for me but that is what I did.