I didn’t update kernel. it still working for me.
Thanks,
I didn’t update kernel. it still working for me.
Thanks,
I can confirm that the issue was in new FOG version. after i installed 1.5.4 version i am able to image same E73 desktops which didn’t work in new version. FOG team should look at what’s wrong in new version.
Thank you all for help. Please mark this resolve.
Thank you. your instruction helped me fix the issue. Please resolve this.
I have FOG setup in isolated network verison 1.5.4. when i tried to deploy image directly FOG gets stuck at “Erasing current MBR/GPT tables” option. it doesn’t seems to go past this option. please help.
i have setup new fog server identical to the one that is working with same hardware. everything is same except FOG version.and it still not working with E73 desktops. it is now proven that issue is not with E73 NIC but it’s FOG problem.
FOG Team, how can i get version 1.5.4 ? i am certain that this version of fog won’t give me trouble. Please help me get it.
Our working FOG server is 1.5.4 version. isolated FOG server is 1.5.6 (one in question)
Here is Details about working FOG
Hardware : Lenovo M91p desktop
Running as VM in Vmware ESXi version:6.7.0
Desktop is connected to Linksys switch ( i sent you link about it earlier) which is than connects to Netgear managed switch.
DHCP is handled by MS windows server. Gateway is sophos firewall where options 66 & 67 are also setup.
we usually connect computers directly to Linksys switch where fog is connected and get them imaged.this is fastest way as transfer rate is much higher. sometimes we image them at some random location. but in both situation we have no issue imaging any type of computer. we maintain standard here so all our computers are of Lenovo brand. models are different and they changes every year. E73’s are the most in use here across offices.
The reason why we are setting up isolated FOG is to send it to our remote offices and get their computers imaged to win10. we tried doing this over WAN but failed. option 66 and 67 was setup correctly at one office but when computer boots up it doesn’t talk to FOG server which is here in our main office even though we have VPN tunnels in place.
Hope this helps. let me know if you need additional info.
Not sure why same E73 works in another FOG server which is in our network.The only difference is that DHCP is handled by our own DHCP server.the process of NIC going down and coming back up is same across all computers. I have feeling some service in FOG not working as it should in this isolated setup. just not able to point which one it is. if you guys think this isn’t FOG issue. feel free to resolve this post.
Thank you all for quick responses.Appreciate all help.
@Sebastian-Roth switch is not the issue.i tried all different switches, network cables even tried 3 more E73’s but still same issue. than i tried E72 model which is one generation older than this and that one worked. so its model specific issue.i just posted NIC description of E73 in earlier post. please check to see if there is any issue with that.
This is the Nic port specs of E73 desktop. “Ethernet : Gigabit ethernet port, Realtek RTL8111GN, Wake on LAN”
does that help in finding solution to this issue ?
i don’t mind setting static non routable IP in centos but only doing because this guide of your tells us to do it. it says you need internet connection. if installing FOG doesn’t require internet i will just set static IP in centos.
https://wiki.fogproject.org/wiki/index.php/FOG_on_an_Isolated_Network
@Sebastian-Roth Here is screen shot from FOG installer. FYI the enp2s0 is set to DHCP right now.we change it to static ip 172.31.1.10 (same as fog server) when we are using fog in isolated network. and back to DHCP if we need to update anything that requires internet connection.
fog doesn’t detect is all it says 'would you like to change default network interface from ? "
centos has named it enp2s0 by default fog doesn’t see that does it need to be changed to eth0 before i run fog install?
hey Guys i am setting up new fog server on centos 7.its in minimal installation.
Nic port is named as ensp03 by default by centos. when i ran fog install it asked me if i want to change default interface from ? but fog is not detecting the port. is there an issue here ?
Same E73’s works when imaged using in network Fog server. which is in Vmware VM. and connected using same old switches. we are going to replicate same setup with same hardware but in an isolated network.
After trying all kinds of options we tried removing patch cable and re connecting it back when FOG was showing "starting eth0 interface " it worked for that moment and than we re tried it worked again for same E73 desktop but when we tried completely different e73 we are back to same issue. sound like it is some type physical issue. but can’t seems to figure it out. different patch cable were tried as well.
anyways Thank you guys for all your support and quick replies. please close this thread. i will just create another Fog server hopefully it won’t give me this trouble.
anything to do with Ethernet port name ? in centos 7 port is named as eno1 and that is what FOG picked up.