FOG needs to be able to resolve the name you defined as a host name in fog to the target system using DNS. So if you can open a command prompt and ping Win10_AT and it works then you have everything setup and fog should resolve and show these systems as up. The only other thing is FOG doesn’t use the icmp ping command to check status but FOG tries to connect to udp port 445 on the target computer. So you need to make sure that udp port 445 is enabled in the target computer’s firewall.

So to restate this in list form:

The hosts to be able to be resolved by name by DNS The host have udp port 445 open in the windows firewall.

This is only informational (green or red mark in the host list) and does not impact the function of fog if you choose to ignore it.

@JerJer said in Trouble with booting to windows:

@george1421 the computer names are nifferent from fog names. Would they all have to be changed manually?

If you want the fog errors clear when you list the hosts then you need to have the fog name match the real system name and fog will need to be able to find the systems using dns lookups.

@ErwinBullen said in Imaging from Storage node fails:

I tried to mount and extract the image, but do not get beyond this error

Sorry for that. Please try this:

mkdir -p /mnt/images mount -t nfs 192.168.100.32:/images /mnt/images zcat /mnt/images/B-Blok-v18-v4/d1p2.img | partclone.ntfs --restore --restore_raw_file --ignore_crc -N -f 1 -s - -O /tmp/d1p2_deployed.img

Hint: Again make sure you do this on a system where you have enough space in /tmp or where ever else you have enough room to dump the extracted image for testing. Maybe best to mount an empty extra disk in /mnt/test/ and write the output file there.

As well please run ls -alR /images on your storage node and post output here.

@franck25 So we were very close in my early posts. I’m glad you now have a solution!!!

@jrm Enabling HTTPS means that you need to recompile the iPXE binaries as well to add your local CA certificate. We added that functionality to FOG in 1.5.5 and fixed it in 1.5.6. I am sorry but we can’t put much effort into backporting those changes to 1.5.2 as we have way too much to do with current changes and requests.

Let me suggest you look into the current version of the iPXE compile script that comes with FOG 1.5.6. Maybe download and try this: https://github.com/FOGProject/fogproject/blob/master/utils/FOGiPXE/buildipxe.sh

But as well you probably need to adjust apache configs manually.

@MFuchs135 Please run the following commands and post a picture of that here:

sudo -i cd /home/user/FOG-Imaging-Server/tmp ls -al cat binaries1.5.6.zip.sha256

Hi George and thank for your attention 😉

We get the error each time computer should reboot or shutdown if we mark the option in the deploy/capture task and yes, you are right, we even get the error executing ‘reboot’ command at FOS.

It’s exactly the same issue that @sudburr describes here:
HP ProBook x360 11 G1 EE Notebook PC succeeds but fails at exit
But, as it was an old thread, i’ve opened a new one.

This is the error I get: https://ibb.co/mhYpyG1 Which is exactly the same as @sudburr’s video. I think it’s still online.

I have tried all options i could, but i’m getting out of ideas

Thanks!

@Sebastian-Roth ok done 😉
https://forums.fogproject.org/topic/13329/1-5-6-small-local-disk-and-the-rest-unallocated

@Sebastian-Roth
Upgraded to 1.5.6 as you suggested.

It seems to be a bit faster, but i need to do the corrections on the server with the same values.

Now i’m experiencing another issue posted as https://forums.fogproject.org/topic/13328/fog-snapins-not-ordered-on-launching-time

Hi Sebastian,

With all of the other posts I had up, this was related to my unattend script and completely unrelated to FOG. This is resolved!

Thank you for the help.

@george1421 said in Change the boot order automatically:

But we do it this way to make sure we don’t reimage the CFOs computer by accident (again) if everything was automatic.

That must have been a bad day.

Sebastian,

I was able to Register Windows10 Host and it is working. What a fantastic jobs, all of you people are doing.

Thank you for all your hard work.

Olduser.

@Sebastian-Roth

Hi,

Thanks works better with TCP port 445. I was referring this wiki :

https://wiki.fogproject.org/wiki/index.php/Troubleshooting_Host_Management_Showing_Hosts_as_Down

It’s solved.

@Scott-B Pleas run find /var -type f -name "*fpm*log*" and post results here.

Ahhh, forget about that. Ubuntu has the errors in apache error log as far as I remember. Please take a look at /var/log/apache2/error.log and maybe paste the whole log messages from yesterday and today here.

Hello
we changed the rights for the /images folder as followed
root@fogserver:/datastore/images/dev# chown -R fogproject:www-data /datastore/images/
Now it works :)))
Greets
JT

@Quazz Such a simple mistake and yet so hard to see. Thanks for seeing it for sure.

the php dont request the needed memory, it request for the next block. So:
When i has 256M it request another ±20M.
Then I increase to 512M. Then the system claims for another 20M.
Then I increase to 1024M and then the system claims for another 20M

I repeat the actions to accure memory size to 1536M.

If it’s necesary to increase the memory a lot then maybe it’s necesary increase the TimeOut and ProxyTimeout httpd.conf paramenters.

@george1421 Trying to read up on this topic I figured that this is not new. Samsung itself has been involved since March 2017!! But seems like this is still the case even with newer kernel versions and other Samsung drives: https://bugzilla.redhat.com/show_bug.cgi?id=1624611

As far as I understand it the lower you set the value of default_ps_max_latency_us the more power is consumed. Not sure if we want to set this by default for everyone.

@jlthompsonpsd Can you please post the exact machine model you have as well as run smartctl -i /dev/nvme0 in a debug capture task console and post a picture of the output here?