I’ve got the same problem, the task appears under Active Tasks but not Active Snapin Tasks and never runs. I’m running Centos 7 64bit and fog 4471.

@cml IT WORKED GREAT! Thanks again.

@cokewithvanilla said:

yes, you can consider this solved. Thank you all for your help. You guys have been great. And I must say that FOG has come a long way since I started using it in ,29 (at least for my uses).

I’m just throwing this out there - but I know Tom recently created a plugin for the latest FOG Trunk that allows for customization of individual tasks… I’m not writing a WiKi just yet on it… but you might play with making a task that includes a DBAN wipe then Image.

Ask @Tom-Elliott for details. 🙂

I finally got back around to working on this, I did have legacy mode enabled and secure boot was turned off, but it was still doing the same thing, I decided to switch from netmasq to just running my dhcp on the fog box and now everything works perfect.

I put the FOG server on a VM, and then have storage on my NAS.

Most NAS’ can function as a storage node if you configure it correctly, I normally use FreeNAS.

diskpart, select volume 1, extend

no ?

I’m confused.

What is the problem?

What version of fog? Latest version means something different things to many of us that actually frequent the forums. What version exactly? I’m assuming you mean 1.2.0?

I was able to get approval to order a different adapter to try can anyone suggest one. I tried to search but was unable to find a particular one. any suggestions would be grand

I can script in command line mostly, I know a little bit of power shell (Enough to be dangerous)
I can do stuff in linux as well I am not very versed but my co workers do have knowledge…

The log files should, hopefully, start appearing again, though there’s no guarantee as I don’t know all particular setups. Hopefully they just work though.

@Clifford-Raymond Look at that line…
Mount: mounting 10.10.0.235:/media/fog/images/images on /images faild: permission denied.

you should start right there.

Is that where your images directory actually is? /media/fog/images/images that’s very confusing.

Go into Storage Management -> Your storage node & look at the image path. The image path should exactly match where the actual image directory is. I’d get rid of the /images/images thing because that’s very confusing.

After changing this, you might want to look at your NFS exports file to confirm it matches. that’s here: /etc/exports

You also need to have 777 permissions set on the /images directory recursively for troubleshooting purposes.

This article talks all about that stuff: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_NFS

Please continue to use git as that version is up to 4193 and the svn is at 3799. Tom is currently working on repushing the versions up.

Again Tom will release an announcement when svn is up-to-date.

What WiKi page did you follow?

Thank you for your reply. I will give it a shot.

Greg

@Scott-Adams Yup.

It’s called a “raw” image type. But, I’d really recommend against that… really strongly… using a raw image type is 99% of the time not necessary and also ridiculous.

When you come into the FOG world, you need to re-learn how you think of imaging.

Today I have installed svn 3783 which uses client 0.9.4 and the service error has gone.
Another issue that remains is in host login history, where you can read logins/logouts but not username info.

as Wayne said it’s not built-in oob but it’s easier to implement, you can even use postscripts which is very powerful - only restriction is your creativity 🙂

https://forums.fogproject.org/topic/4278/utilizing-postscripts-rename-joindomain-drivers-snapins

@Hanz Please check your messages, I left a few for you.