@mikmatcr ok what I would do is run fdisk from command prompt sudo fdisk /dev/sdb d p 2 d p 1 w e Note it may be q to quit and not e to exit. I did that from memory. That should delete both partitions and write them back to the disk. Now you can start with the instructions https://forums.fogproject.org/topic/11048/moving-fog-s-images-files-off-the-root-partition-2017-edition up to and including step 7. That will create a new partition and then format it. Once you have it formatted then we can go through the steps to copy the files over and then remap the drive.

@greichelt You can reply to this thread as long as its in the same concept as the title. Just be sure to tag me so I see it.

@george1421 George, at @Sebastian-Roth 's request, I am opening a new topic for this. To answer your question, we install no drivers in our golden image, not even VMware tools. Whatever drivers are installed are included in the Windows 10 1803 base install.

@thennessey said in Error Trying to Restore GPT Partition Tables: I swapped out the files in the google drive link for the ones that are associated with the win10UEFItest image that I originally had questions about. I see you swapped those out (numbers in the files are different) but I still cannot reproduce the issue as reported. The numbers seem ok and I can deploy using those files to a 100 GB size VM disk perfectly fine…

@kburns Yes, George is probably right. Take a look at /tftpboot/default.ipxe text file and put in the correct IP. It’s important you read this wiki artikle: https://wiki.fogproject.org/wiki/index.php/Change_FOG_Server_IP_Address

@tunatoksoz Hmmmm, thanks for joining the discussion here! Seems like you are making progress on this more than we have. :-) May I ask you if this is on Lenovo 300e as well? As you are saying yours has a build in NIC plus one on PCI I kind of doubt you have the same machine. Can you be more specific on what make and model you see the issue on?

before you capture with fog either use sysprep to power off the computer or issue shutdown -s -t 0 to power off the computer. In windows 10 the shutdown button is really a fancy sleep mode and not really a close everything and power off kind of shutdown.

@cammykool It can do remote execution, printer management, power management, login recording, and other things. I’ve used it to run scripts, deploy software, and other things. Check out these wiki articles below, they might help you understand the capabilities. https://wiki.fogproject.org/wiki/index.php?title=FOG_Client https://wiki.fogproject.org/wiki/index.php?title=Snapin_Examples https://wiki.fogproject.org/wiki/index.php?title=SnapinPacks There’s also a ton of stuff on the forums about printer management. Here is one with some detail: https://forums.fogproject.org/topic/8051/printer-deployment?page=1 though there’s probably hundreds of topics about printers.

Updated the URL in the official code (ref).

@doubleve Do you have fast boot disabled in Windows before you started the capture task? Sure the machine is not hibernated or anything? Did you see any error message in the blue partclone window that has been on screen hust before the screen we see in the picture?

@Quazz Not sure from the top of my head. Thanks for finding this!! I will take a look later on.

@ITCC Switch your DHCP config to point to ipxe.pxe instead of undionly.kpxe and the issue should go away.

@george1421 Changing the settings in the default.ipxe file worked! Man this community is great! I’m going to update my documentation to make note of this so in the event we move subnets again we can tackle this same day!

@doubleve You only need tftp if you want to boot from the nas. If you have a real fog server on the same network you can use that. For a storage node you only need NFS and FTP service.

thanks, i figure up what’s the problem, i’ve add corrupted lines on /etc/fstab. thanks for everything. everything is working now. :)

@Beyondlimitation said in PXE Client tries to find wrong file: By the way, if i copy “undionly.kpxe”, paste it in directory “/tftpboot” and rename it to “undionly.kpxe.0” pxe boot successfully works While I see you have it sorted out, requiring the boot file to end in a “.0” was a requirement of DNSMASQ before 2.76 (as well as syslinux). With 2.76 and later its just the file name. The “.0” requirement was removed since that is a bios related thing. What version of dnsmasq are you running (i.e. dnsmasq -v)

@george1421 @Sebastian-Roth I reverted everything back and switched the Sata mode to AHCI and everything is working great again and both the NIC and storage passed the compatability test! Big thanks to both of you! Hopefully the big companies will start releasing open-source drivers so Linux can thrive

@wreckignize The rest of the setup should be the same, just how it gets installed is different.

@kwisher Well life may be better on the dev branch. Why I asked if you were on 1.5.7.55 or later, stay there. FOG 1.5.8 is almost release. 1.5.7 had a few bugs where 1.5.7.55+ in the dev branch fixed.

@Spicoli Thanks! RAID to AHCI worked for me.