Posts made by RogerBrownTDL

@george1421 Outputs are as follows. I’ve not expanded the VHD yet

root@tie-fogdeploy-01:~# lsblk
NAME                      MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
fd0                         2:0    1     4K  0 disk
loop0                       7:0    0  61.9M  1 loop /snap/core20/1328
loop1                       7:1    0  61.9M  1 loop /snap/core20/1405
loop2                       7:2    0  55.5M  1 loop /snap/core18/2344
loop3                       7:3    0  67.2M  1 loop /snap/lxd/21835
loop4                       7:4    0  67.8M  1 loop /snap/lxd/22753
loop5                       7:5    0  43.6M  1 loop /snap/snapd/15177
loop7                       7:7    0    11M  1 loop /snap/nmap/2608
loop8                       7:8    0  44.7M  1 loop /snap/snapd/15314
sda                         8:0    0   127G  0 disk
├─sda1                      8:1    0     1M  0 part
├─sda2                      8:2    0   1.5G  0 part /boot
└─sda3                      8:3    0 125.5G  0 part
  └─ubuntu--vg-ubuntu--lv 253:0    0  62.8G  0 lvm  /
sr0                        11:0    1  1024M  0 rom

root@tie-fogdeploy-01:~# df -h
Filesystem                         Size  Used Avail Use% Mounted on
udev                                16G     0   16G   0% /dev
tmpfs                              3.1G  1.1M  3.1G   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv   62G   24G   35G  41% /
tmpfs                               16G     0   16G   0% /dev/shm
tmpfs                              5.0M     0  5.0M   0% /run/lock
tmpfs                               16G     0   16G   0% /sys/fs/cgroup
/dev/loop1                          62M   62M     0 100% /snap/core20/1405
/dev/loop0                          62M   62M     0 100% /snap/core20/1328
/dev/loop3                          68M   68M     0 100% /snap/lxd/21835
/dev/loop2                          56M   56M     0 100% /snap/core18/2344
/dev/loop4                          68M   68M     0 100% /snap/lxd/22753
/dev/loop5                          44M   44M     0 100% /snap/snapd/15177
/dev/loop7                          11M   11M     0 100% /snap/nmap/2608
/dev/sda2                          1.5G  109M  1.3G   8% /boot
tmpfs                              3.1G     0  3.1G   0% /run/user/0
/dev/loop8                          45M   45M     0 100% /snap/snapd/15314
root@tie-fogdeploy-01:~#

@george1421 Within Hyper-V I gave it a 127gb harddrive, within Fog management the file system info is showing the following:
Total Disk Space 100.04 GiB
Used Disk Space 24.19 GiB
Free Disk Space 75.84 GiB

On the dashboard for Fog storage node it shows
34.68gb free…

So 2x things here really, if I expand the VHD within hyper-v by 100gb, will Linux and thus Fog automatically see that and if so, how do I get the Fog storage node to grab that 100gb more space (I’ve got 1TB of physical space to play with on the host so expanding the VHD of linux wont be a problem)

@george1421 Bingo!!! I’m up, just a couple of additional questions and this topic can be closed. Once i’ve captured my image, if I deploy that to a target machine will it wipe the drive and put my image on? (I want it to do that rather than just adding/appending the image to the drive) - Sounds a stupid Q I know.

Last question is can the storage node be increased past 50gb or is it a case of when that node is full I have to create more?

Cheers for your help so far mate, its been invaluable

@george1421 Done the same commands, it tells me 8packets captured, 8packets received by filter and 0 packets dropped by kernel. This is the PCAP https://1drv.ms/u/s!Aoxev2npVk1SiWzNGWOy_w0bkejb?e=KPl8z5

@george1421 I will try run PXE on 2x machines which may give more to go off. The one I sent was the PCAP for a local VM running on the same host that the Ubuntu server is running from. I will run it on a physical machine on that same LAN and get the output

@george1421 Hopefully this makes more sense to you than me fella https://1drv.ms/u/s!Aoxev2npVk1SiWpaTnty3O3t5xkG?e=aKd03S

@george1421 Yes same subnet/VLAN
DHCP = Watchguard 192.168.15.254 with option 66 set to 192.168.15.251 and 67 set to undionly.kpxe
FOGServer= 192.168.15.251

@george1421 It is indeed, 192.168.15.x/24

Target/machine I want to register and capture gets an IP but then doesnt do anything and just boots into windows after that. Coincidentally, I just tried skipping doing the physical machine and just spinning up a test VM and trying to PXE from that, again it gets an IP address but it gives a timeout “pxe-e32: TFTP Open Timeout” error.

@george1421 Yup, tftp “ip” get undionly.kpxe works and brings it down to my windows box

@george1421 I’m using a Watchguard for DHCP from a segregated build LAN, the target gets a DHCP lease but doesnt progress to the PXE menu, just continues booting into windows.

Hi All,
Bit new to the world of Linux but was looking for an alt solution to archaic MDT. Low and behold I found the FOGProject which seemed perfect. However, I have run into an issue with the very first thing I want to do.

I’ve managed to get FOG installed with no problems but I’m unable to PXE from it to register hosts/capture images. I’ve set my DHCP option 66 to the IP of my FOGServer and I have changed the option 67 between the options of Undionly.kpxe, ipxe.efi and undionly.kkpxe but still unable to PXE. I’ve got secure boot disabled on my target that I want to capture, i’ve turned the firewall off on the Ubuntu server but still unable to get it to play ball…

I was doing some reading earlier and I’m unsure if it’s related but I can’t TFTP to the server from the LAN but I can TFTP from itself.

Do I have to do any config work for the undionly or ipxe to work or should it just work straight off the bat when installed

Thanks in advance
Roger