Ok this is resolved. I was able to unbox another new machine and build out the image and capture it from that machine. I then deployed the image to the other 11e that would not capture without error. Thanks All for the help

@moses well its more of a band-aid than a solution. I’m glad you got passed this issue. From what I’ve found this is a in kernel issue with some hardware that dates back to 2009. You might want to see if there is a firmware update for this hardware, or, you just might want to take this kernel parameter as a WIN and move on.

@fry_p Once you’re into MySQL CLI - you can copy all the SQL commands at once.

The “permanent” fix for the virtual box issue is to use the ipxe.pxe boot file.

@george1421
from information on the other topics that match this new error that you showed me how to find, i was able to boot back into windows use diskpart and chkdsk to mark the hidden system drive as clean, sysprep again, and then the image capture went through. Thanks for the help. 🙂

First I feel I should clarify, “Sectors 5-7” is always going to be in regards to the disk. I’m not aware of any system that refer’s to “Sectors” on a “partition” basis. Sector 5-7 will remain Sector 5-7 irrespective of the partition those sectors may reside in.

Perfect! Thanks that worked!

Joe

@george1421 @Tom-Elliott

I may have a new way to do this, strange as it may sound I forgot one of my NAS boxes can also handle my DHCP, so i need to reconfigure the network when i get some free time

@Tom-Elliott clearly i have posted this in the wrong thread :0

@Tom-Elliott you’re a gentleman and a scholar. I won’t believe the things they say about you again. Lol.

@Wayne-Workman I ran

chmod 755 ./installfog.sh

and it works now. Thanks for pointing that out.

@kylebeth94 the client does not follow 301 / 302 http codes (redirects). I run one of my development servers on https, and with a webroot of /. You’ll need to configure your webserver to serve out / without using redirects. You can redirect http to https traffic if you desire, but just make sure the client is set to use https then.

Ok, thanks @URfog that put me on the right track. My fog web server is not a storage node. I added it to the list of storage nodes with a max clients of 0 and I can boot normally now.

@george1421 Idiot moment. Sorry for all of the trouble but I had the 66/67 settings done in the server options and didn’t realize that the old FOG server settings were done in the scope options. That’s why is was overriding and sending pxelinux instead of undionly. Again, sorry for the trouble and thanks for your help. Issue is resolved and registration works great now.

Looking at your pcap file I would say you have 2 dhcp servers on your network (not a good option).

One is 192.168.5.1 and one is 192.168.5.200.

192.168.5.1 appears to be a router that is passing out an IP address but no pxe boot information. 192.168.5.1 is passing out a client address of 192.168.5.80 to the client.

192.168.5.200 appears to be (maybe) a fog server running either dnsmasq or isc-dhcp server (probably). 192.168.5.200 is passing out a client address of 192.168.5.10 to the client. 192.168.5.200 is sending out a boot file of undionly.kkpxe with a next server of 192.168.5.200.

This seems to be confusing the clients because one time they accept the IP address of the router and sometimes they accept the ip address from fog (which is not providing enough information, but does provide pxe booting information).

Course of action:

Disable the isc dhcp server on the FOG server. Install DNSMASQ to provide the pxe boot information without providing a ip address to the client.

@John-L-Clark if an entry is made properly in /etc/fstab it will mount on boot, else it wont. Reboot and see. This is something that needs dealt with immediately - don’t wait.

@cnkpadobi well that is sure one way to fix the issue!! Thank you for the clarity.

@royg706 I would verify the credentials - them seeming to appear correct isn’t good enough, they need tested. Here are two articles that explain how to test the FTP credentials and remote MySQL credentials properly - if there are problems with any of this, you’ll find them during testing.
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL

@Tom-Elliott

Hi Tom

Running the installation again with sudo-i worked

Thanks for your help

Kind Regards

Lawrence

@Tom-Elliott
ok.