How did change to the root environment? Make sure you use sudo su - (check the man page on what ‘-’ is for) or sudo -i

@nbuursma The version you can see in the blue cloud on the web interface. Probably a number between five and six thousand. I doubt you see 1.2.0 in that cloud. Right?

Edit: Yeah, so you are running trunk version (will be 1.3.0 when finally released but is still under development right now). Probably best if you upgrade to the very latest version (update the checkout code and re-run the installer) and see if it works for you.

Why did you decide to use fdisk instead of lsblk? From my understanding of linux and those tools I’d say that fdisk might cause more issues than lsblk would. Thinking about GPT and minor hickups in a partitioning schema. lsblk is more likely to show the partition names without doing much checks on them before.

@Toby777 Could you please run a debug session on this device (WebGUI -> Host -> Basic tasks -> Debug) and run lsblk. What do you get?

Are you sure it said /dev/nvme0n1 when trying single disk resizable?? Asking because this would be the whole disk instead of the first partition. In RAW mode nvme0n1 is fine.

@wwarsin Looking at the last few lines of output it seams a bit like FOG doesn’t find any partitions on your device. It says “Saving Partition Tables (GTP)” and then “Task complete” straight way.
Can you please run a debug session on the surface and see what you get from lsblk

@Tom-Elliott Have you looked into using some of those options yet?

What does the partition table look like on the client you are trying to capture from? What kind of client and what kind of HD is it? Which image type do you want to use?

@Julianh WOW! Not something I’d have ever come up with. Thanks a lot for reporting back. I am really glad that we don’t need any kind of special kernel patch to make this work.

@FlareImp Can you upload a screenshot of this. I have a really hard time understanding what you mean by “but now when our clients PXE Boot at either SVN site there are now two entries in our DHCP server”. Two entries? Are those generated automatically?

@mitzayapa Looks like PXE information is being sent by your cable modem as well as dnsmasq. Please read through this post - from start to end (!): https://forums.fogproject.org/topic/6355/dnsmasq-proxydhcp-tries-to-pull-ipxe-default-from-wrong-ip

We’ve been working on updating the embedded iPXE script and I thought we’ve got this solved by some checks. By the looks of your screenshot I guess that you don’t have the latest iPXE binaries installed. Just try downloading the latest undionly.kpxe on your FOG server:

cd /tftpboot
sudo mv undionly.kpxe undionly.kpxe.orig
sudo wget -O undionly.kpxe "http://sourceforge.net/p/freeghost/code/HEAD/tree/trunk/packages/tftp/undionly.kpxe?format=raw"