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

Thanks Tom S

@Sebastian-Roth I will try this in about ten days when we are back in session. Thanks!!

@Joe-Schmitt Yep I had bat for some reason…No idea how because I used to have.cmd

@george1421
The image transfer is complete!

I had to touch the .mntcheck file to the /images and /images/dev directory. But other than that, I’m up and rolling again! Woo Whooo!

I can’t wait to start fresh with Debian and clean up my server a bit. That’ll be next month’s project!!

Thanks everyone who’s contributed!! I appreciate all the advice! 😄

Cheers,

Joe Gill
Townsend K-12 Schools

[SIZE=6][B]newbie here[/B][/SIZE]

[SIZE=6][B]How do i change the fog server ip in 1.2.0?[/B][/SIZE]

It was not a problem of Timeout FTP…But it doesn’t matter, i can do cp -a /images/dev/@MAC /images/name 🙂

[QUOTE]What user does the FreeNAS use? [/QUOTE]
I’m only one user of FreeNAS

The download is ok to the new client.

I will write the tutorial ! 🙂

We were able to get the stuff figured out. YAY!

The connection is now operational. FOG Interface displays properly.

@Scott-Adams

We are requesting that all community members who have Surface Pros to please do a packet capture, to capture the DHCP conversation the client sends out at boot time via the ethernet dock, and upload the capture here. The intent is to gather more information about the Surface Pro, so fog can better support network booting it.

Thanks,
Wayne

@dureal99d Your welcome. I’m glad in the end it was just a simple reboot that finally resolved the issue.

We had a hour or so chat session to work through this issue pulling apart the dhcp/pxe booting process frame by frame.

@sebastian-roth said in Linux kernel:

Just not sure if it’s worth sending it around the world as I am located in Germany.

His org could just buy you one and have it shipped to you. Of course you are deserving of much more than a crap hardware model, Sebastian. 🙂

@george1421 Thanks for all your help!

@wayne-workman said in Boot File Testing for SR:

@george1421 said in Boot File Testing for SR:

@psycholiquid Pssst… to adjust the small font size try this FOS kernel parameter vga=792

vga=792 should be 1024x768x24 video mode, and clean your monitor, please!!! 😛

ref: https://unix.stackexchange.com/questions/71231/grub2-and-kernel-vga-parameter/114980

#wiki worthy

LOL I don’t think you should wiki me having to clean my monitor… LOL I kid.

@Sebastian-Roth said in Replication Issue:

max_per_ip=200

Changes in the conf done, will let the rep job running 2 full rounds and edit this post with the results.

“Seems like the default of 50 is not enough for the amount of images you have” yeah, as I said in the chat, here we use fog A LOT, bout 7 diferent images in frequent use and others 4 used from time to time. F* good tool indeed. hahaha

Edit: Hell yeah! running like a charm! 3 rounds of rep job so far, no mismatch, no max conn reach… beautiful

tks dude! Appreciate ur suport!

Alright, I call this solved (eventhough it really isn’t). We’d be very happy to hear if someone can reproduce this so we are able to fix it. For everyone running into this: see post #39 in this thread on how to solve the issue yourself!

@george1421 said:

@gwhitfield said:

I stopped being prompted for the IP address and I hope that’s a good thing, I’m pretty sure that happened when I changed the DHCP policies.

wiki hint: Under efi booting, if we are getting the ipxe kernel being delivered to the target computer but the ipxe kernel either doesn’t get the next server, boot file, or possibly an IP address we should dig into what architecture is being requested and what the dhcp server’s policy is configured to deliver. @Wayne-Workman

Added a note: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Step_3

NOTE: I moved all the posts about testing the iPXE binaries: https://forums.fogproject.org/topic/10789/boot-file-testing-for-sr

@imt_fog If you boot the machine in question in debug mode, you should be able to run parted -l manually and check the flags.

I don’t think this is caused by such, however, but interested in seeing the results.

Worth noting that partitions that go through the checks but fail to resize get marked as fixed size as well (to prevent issues during deploy)