@Sebastian-Roth WhatsApp Image 2019-05-04 at 15.35.11.jpeg WhatsApp Image 2019-05-04 at 15.34.44.jpeg
25 an 36 PC in Multicast

@george1421 That was the problem! Thanks!

@Sebastian-Roth said in FOG unable to capture/deploy resizeable images correctly.:

@dambron Yeah, Quazz is totally right. We have updated the init files and I totally forgot to ask you to try out the most current ones (32 bit and 64 bit). Hope this will fix the issue for you.

Thanks so much to both of you. I replaced the init file and everything is now working properly. Many thanks for your time and efforts.

@Sebastian-Roth
My apologies for not being clearer in my message. I realized here in the past hour that the files were missing after running the terminal commands that removed the old web data. I put the files back and our links are now working again. All issues are resolved and we appreciate your assistance in making it happen.

@nvdp2002 The last we see in the log is Is the MySQL password blank? (Y/n) - how do you answer the question? Do you know the password of your database? Is it blank or set?

@Sebastian-Roth Thanks for taking a look. I lowered the max bandwidth that the replication can use so it would not crush our link and allowed it to run all night. The images have replicated and traffic has dropped off. again thanks for the help. I think everything is working now.

@george1421 @Sebastian-Roth thank you for your answers!

I will try it out, but I think its much easier du do a VM with the .iso and image it.

Ok. I’ll pass that along. Thanks

@loosus456

I understand what you’re requesting, and I think @Sebastian-Roth understands as well.

I’m not saying we shouldn’t or couldn’t be asking the storage location, just that there are ways to do what people want even if it’s not blatantly obvious. That’s why we’re here. To help people do what they want and show how to do so. Even if it could be handled in a better way.

Please understand that trying to code for every potential question and option is nearly impossible and in many cases will appease some and disgrace others regardless of the optional route chosen.

We are a very small development team. Trying to dedicate time for some things can be hard. That’s the brunt of what @Sebastian-Roth was trying to say, I truly believe.

I don’t think he is attempting to hurt anyone’s feelings. He’s just trying to say, if you (generalized to mean anybody I believe) feel something should be added, try to add it and make a pull request. We are often working with people to implement new items and fix bugs from others who have added suggestions and code.

I am making this a normal thread as this is not a real FOG problem that can be just solved. Please follow up in the feature request topic here: https://forums.fogproject.org/topic/12506/client-inventory-option

@guilux Sorry I’m late to get back to this thread, but I’m glad you found the troublemaker!!

I was going to tell you that now you have the mac address you can go to your network team and have them look at the mac tables to find out what port that device is connected to. That is the way to track it down. But you find it, so great!

@tripleh You can define the target hard drive in the host configuration. Just define /dev/sda in the parameter. If you need to target the second hard drive then you will need to update this parameter.

@george1421 Brilliant! haha. thanks. yup, my fog server is isolated so I just copied it from my windows workstation into notepad and transferred not thinking anything of it…

@dwightbot Edit /tftpboot/default.ipxe on your FOG server to correct the IP.

Make sure you read this and even better use this script when changing the FOG server IP!

@Sebastian-Roth This worked, you can mark this as solved. Thank you for your help.

Hi George,

Thank you for your reply. My system is Ubuntu 19.04 so I just took the output from terminal, hope that’s ok?

The image was taken from /dev/sdd and I am wanting to deploy it to /dev/sdb

In case its relevant I specified “/dev/sdd” as Host Primary Disk to prevent FOG taking Windows as the image.

See here:

https://forums.fogproject.org/topic/13042/how-to-edit-drive-cloning-options

root@Ubuntu19:/home/mike# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 35.3M 1 loop /snap/gtk-common-themes/1198
loop1 7:1 0 3.7M 1 loop /snap/gnome-system-monitor/77
loop2 7:2 0 143.5M 1 loop /snap/gnome-3-28-1804/23
loop3 7:3 0 53.7M 1 loop /snap/core18/941
loop4 7:4 0 14.8M 1 loop /snap/gnome-characters/206
loop5 7:5 0 1008K 1 loop /snap/gnome-logs/57
loop6 7:6 0 3.7M 1 loop /snap/gnome-system-monitor/70
loop7 7:7 0 151M 1 loop /snap/gnome-3-28-1804/36
loop8 7:8 0 4M 1 loop /snap/gnome-calculator/406
loop9 7:9 0 91.1M 1 loop /snap/core/6531
loop10 7:10 0 53.7M 1 loop /snap/core18/782
loop11 7:11 0 89.3M 1 loop /snap/core/6673
loop12 7:12 0 14.8M 1 loop /snap/gnome-characters/254
loop13 7:13 0 1008K 1 loop /snap/gnome-logs/61
loop14 7:14 0 4M 1 loop /snap/gnome-calculator/352
sda 8:0 0 596.2G 0 disk
└─sda1 8:1 0 596.2G 0 part
sdb 8:16 0 1.8T 0 disk
sdc 8:32 0 931.5G 0 disk
└─sdc1 8:33 0 931.5G 0 part
sdd 8:48 0 1.8T 0 disk
├─sdd1 8:49 0 512M 0 part
└─sdd2 8:50 0 1.8T 0 part
├─ubuntu–vg-root 253:0 0 1.8T 0 lvm /
└─ubuntu–vg-swap_1 253:1 0 976M 0 lvm [SWAP]
sr0 11:0 1 1024M 0 rom
nvme0n1 259:0 0 232.9G 0 disk
├─nvme0n1p1 259:1 0 232.3G 0 part
├─nvme0n1p2 259:2 0 100M 0 part /boot/efi
└─nvme0n1p3 259:3 0 502M 0 part
root@Ubuntu19:/home/mike# fdisk -l
Disk /dev/loop0: 35.3 MiB, 37027840 bytes, 72320 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop1: 3.7 MiB, 3821568 bytes, 7464 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop2: 143.5 MiB, 150470656 bytes, 293888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop3: 53.7 MiB, 56315904 bytes, 109992 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop4: 14.8 MiB, 15458304 bytes, 30192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop5: 1008 KiB, 1032192 bytes, 2016 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop6: 3.7 MiB, 3846144 bytes, 7512 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop7: 151 MiB, 158343168 bytes, 309264 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/nvme0n1: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 970 EVO 250GB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 09583A20-4CD6-11E9-B903-C97FD46B0FAF

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 487161329 487159282 232.3G Microsoft basic data
/dev/nvme0n1p2 487161856 487366655 204800 100M EFI System
/dev/nvme0n1p3 487366656 488394751 1028096 502M Windows recovery environment

Disk /dev/sda: 596.2 GiB, 640135028736 bytes, 1250263728 sectors
Disk model: WDC WD6400AAKS-0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0000a7b9

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 1250263039 1250260992 596.2G 83 Linux

Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD20EFRX-68E
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EZEX-00M
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 1A9126E1-F57F-4FD8-B67C-35B6AB0A5AF0

Device Start End Sectors Size Type
/dev/sdc1 2048 1953523711 1953521664 931.5G Linux filesystem

Disk /dev/sdd: 1.8 TiB, 2000315023360 bytes, 3906865280 sectors
Disk model: MARVELL Raid VD
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 70FAF413-B8D4-4AD7-BEB0-ACEC78095D8B

Device Start End Sectors Size Type
/dev/sdd1 2048 1050623 1048576 512M EFI System
/dev/sdd2 1050624 3906865151 3905814528 1.8T Linux LVM

Disk /dev/mapper/ubuntu–vg-root: 1.8 TiB, 1998749433856 bytes, 3903807488 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/ubuntu–vg-swap_1: 976 MiB, 1023410176 bytes, 1998848 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop8: 4 MiB, 4218880 bytes, 8240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop9: 91.1 MiB, 95522816 bytes, 186568 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop10: 53.7 MiB, 56315904 bytes, 109992 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop11: 89.3 MiB, 93581312 bytes, 182776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop12: 14.8 MiB, 15462400 bytes, 30200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop13: 1008 KiB, 1032192 bytes, 2016 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop14: 4 MiB, 4214784 bytes, 8232 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
root@Ubuntu19:/home/mike#

@IT-Knight said in FOG issues on Ubuntu 16.04 LTS:

First, I had set up the fog server and captured an image. I then tried to multicast that image to 2 computers as a test. The capture seemed to work, but after multicasting, I ran into an error when booting the clients. I kept getting an error that said “Invalid Partition Table!” While troubleshooting this, I attempted to reboot the server computer and my network changed my IP Address, causing the server to get all messed up.

First let me say that you should/must set the fog server to a static IP address before installing FOG. FOG does not support dhcp supplied IP addresses. If the fog server changes IP addresses after FOG is installed you will have a very unhappy FOG server. There is a process to resync the fog configuration, but I would get your fog server configured for a static IP address before going through the process.

The clients were now unable to communicate with the server when PXE Booting so I was unable to connect the clients, capture images, and multicast.

The pxe boot settings in your DHCP server need to be updated to the actual (new/current) IP address of your fog server.

Also, I seem to be having some strange networking issue in Ubuntu. When I connect the ethernet cable to the network port, it gives me the up and down arrows to show that it is connected. But when I then connect the ethernet cable to the switch to do the PXE Booting, the up and down arrows do not appear and the computer seems to constantly be searching for a connection.

I would say lets get your IP address issue resolved with the fog server first. Then we’ll need you to clarify “when I then connect the ethernet cable to the switch to do the PXE Booting, the up and down arrows do not appear and the computer seems to constantly be searching for a connection.” Is the fog server doing this or the target computer?

@kafluke The problem seems to have only affected a small number of users. Thanks everyone for trying to help. I’m marking this solved.

@vanopy I’m still thinking its a disk error. You may need to boot it back into Windows and run some disk repair utility to see if 1. you can detect the error in the OS and 2. repair the error. The fog suggestion that disk space on the server is the issue is incorrect.

@Sebastian-Roth OK. I just didn’t wait long enough sorry to rattle your cage. Thanks for the help it did the hash just waited a while and it’s working now.