@quinniedid Sure!

Base steps were I created a new image in GPT format.

Afterwards, on the FOG server itself I edited the config file located at /var/www/fog/service/ipxe/refind.conf

Below are what I have the values at. This was after some troubleshooting so some may be back to their default values.

timeout -1
scanfor internal,external (I also have both lines commented out at the moment)
uefi_deep_legacy_scan is uncommented
scan_delay 5

From my memory that is all that is changed. After the imaging is completed in UEFI, it will boot straight to the OS instead of pushing itself through FOG and/or rEFInd.

Hope this works for you!

I’d recommend running nothing except FOG on your FOG server. We’re not able to troubleshoot integration with other 3rd party software, that’s on you.

Yes, I also think that this stick is faulty. I posted this question here hoping that it was not the case.

Anyway, thank you very much for the answers guys.

I’ll just use this PC for some other project. Thank you all again.

Bye

@george1421 Your suggestion worked! Thank you very much.

@george1421 George, thank you. The issue has actually been resolved. For some reason, checking what was using .1.25 did not cross my mind. As soon as I did a scan of our network, I found that someone had booted up our old imaging server which was located at 1.25. Once I turned it back off, Fog returned back to normal.

Issue has been resolved!

I have 1.5.2 version

@sebastian-roth it’s working now. I had the wrong bootfile Name in option 67 on my DHCP server.

@sebastian-roth I disabled legacy. It works. thanks.

@sebastian-roth Thanks Sebastian!

Unset the dhcp option 60. If you have a proxy dhcp server it sets dhcp option 60 to indicate it exists to the client. Your error message 4011 is caused by dhcp option 60 being set without having a proxy dhcp server running.

@szeraax Open a new thread up the next time you want to do something to get some suggestions. This is a benefit of a project with an active community.

@tom-elliott Awesome, working like a charm, thank you.

This is now working thanks to @george1421’s help. What happend was that I had two versions of dnsmasq installed causing this issue. I was able to remove the 2.75 version that came with the OS and recompile and reinstall 2.76. Now everything is working as expected.

@drapalsfj Once you have 2.76 then you need to use my config file for 2.76 or later. Once you have that you can pxe boot both firmware types. But if you are installing 2012 dhcp server that is a better longer term solution. If you need to circle back to dnsmasq let me know and we can finish your setup.

@sebastian-roth ok after fixing my error to the multicasttask.class.php I ran the 3 tests you suggested

do not turn off any of the clients to see if it still is reliable

pull the network cable of one of the clients while multicast is on for 5 seconds - see if that is enough for it to be dropped already

turn off one of the clients while multicasting and see how long it takes for it to drop

During the first test, multicast worked normally and the new argument added to multicasttask.class.php was reflecting in the logs. During the second test pulling the network cable did not appear to drop the disconnected host, but upon plugging the network cable back in the session returned to normal speeds. During the last lest of powering a client off during a session, the multicast session came to a near halt and is only transferring at around 100 MBpm. I’ve left the session going all night and the session is still active and moving at the throttled pace.

@zacadams Glad you got this figured out.

@thebrennan47 The 500 error indicates you have an issue in your php.

You might want to review the apache error log to see if it will give you a clue to the issue.

@george1421 said in Fog storage node on mounted NAS:

@shad0wguy I can tell you setting up nfs was the hardest bit of getting the nas to work as a storage node. I need to look back at my post to find what was the key to make it work. It was simple once I learned what was needed.

For testing I can give you some tips.

Login to your fog server. Then run this command.
sudo su -
Then find out who you are
whoami
If you are root then good. You can test your nfs mounting by
mount -t nfs <nas_ip>:/IT-Files/Images /mnt
When that mount command works then you know you have the nas nfs setup correctly. Also watch your case, you are dealing with linux which is case aware.

On the nas you need to have nfs v3 enabled. FOG doesn’t support nfs v4 yet.

I found the issue. I needed the full path of the nfs location from root rather than just the root of the share.

That helped! that and after talking to my boss and he telling me that he was trying out a new web filter on the subnet i had the server in… thanks a lot!

@george1421 Cool. Thanks a lot for all of your help.