Topics created by mmoore5553

i have resolved this issue. I am not sure but when i was looking into ubuntu it did not update the images correctly. I moved them again and this time it was working correctly

i used FTP software , filezilla , to see the files where not on the ubuntu server but the gui was saying it was there .

@mmoore5553 Good to hear you were able to make it work. Just a few comments on what you said:

I ran the setup again in the vm and finally go the error setting up and starting dhcp server - no router address found - no dns address found.

The router and DNS addresses are only used by the FOG installer to set those in the DHCP configuration to be sent to clients requesting IP (and router/DNS information) from the DHCP server.

if i want a VM to connect I have to change my VM to Nat and not bridged.

Hmm, I would think you can set all VMs to bridged and should be able to PXE boot VMs and physical machines then.

@mmoore5553 said in drive not expanding fog 1.5.9:

@scott-b yes it is . Windows 20h2 . I finally got it resolved by the moderator. I had to go into my image and delete the recovery drive. Then it acted correctly.

Just wanted to put that out there if someone else had the same issue

Thank you for letting me know. I’m having the same issue so I’ll give that a shot.

Issue resolved over chat: The root of the issue is that something happened to the dhcp server configuration file and it was damaged. Once dhcp server config file was updated the target computers pxe booted and imaged again.

@mmoore5553 Not a clue since I don’t have one to test with, sorry.

@Sebastian-Roth Yes it was on the iPXE side. During testing we booted FOS Linux off a usb flash drive and it imaged fine. Well with some clarity, it imaged fine once we added nvme_core.default_ps_max_latency_us=0 to the usb/grub boot parameters. SO that kind of points to ipxe/hardware/uefi firmware that had a conflict with this specific nvme disk.

The issue ended up being a configuration problem with the dhcp server. Once that was straightened out the target system pxe booted like expected.

Thank you everyone for your help. I had networking team move to same vlan and it worked fine. Then i had them move to seperate vlan and use wireshark. I found out we had sccm pxe setup. This was done long time ago. No one removed the forwards on the router.

Now we have it working once we removed the entries.

i have finally figured out how to get vm workstation working with no problems. My computer is plugged into real network at the time. I have to plug into the isolated network. When it pulls an IP address I then go and disable the adapter and enable it again. it then gets the ip address again. I then run ipconfig /flushdns.

After i do that and only then will i start VM workstation. i will go to the vm and go back to my snapshot. before i open it i always make sure the settings are showing bridged. I then power on the vm to the saved stated and run a ipconfig to make sure the computer and vm have actual same IPs in the subnet. Then run a flushdns on the vm. Then i sysprep and then boot to firmware on the vm. Then i pick network boot.

This has worked 7 times with no issues. I am sure i could cut out some steps but it is real easy for me to do all of it real quick. I only check to make sure it is bridged mode once.

Once i started to do this vm workstation work everytime and even on VM reboots.

I hope this helps someone else out.

Oh and i disable wireless first if you are using that.

With a quick teamviewer session this issue has been resolved. The issue was just the sequence of install and ensuring eth0 was up before installing FOG.