@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.

@luis-acacio said in Filesystem check error after capturing W10 image.:

I’ve tried to follow these tutorials but they are missing a lot of information… they’re just awful. Specially the one in the wiki.

I feel as if I may need to clarify something for you. I understand you may be frustrated, but the FOG Project is an open source solution that is not only free and designed/maintained completely by a small group of very intelligent volunteers, but also has top notch support on these forums that rivals paid support contracts.

Admittedly, the wiki is outdated. This is because these few developers are working on continuously improving fog and running a full fledged helpdesk for free, so it is understandable that the knowledge base takes the back burner. I assure you that every issue I have ever posted about in these forums was solved in an appropriate time-frame.

I don’t speak for the project and the only way I am involved in it is solely as a user, but I hope you now have some insight into the reasons behind the shortcomings of the wiki and I hope your issue is resolved soon and to your liking.

Thanks for the suggestions, George, that sounds reasonable. I’ll do some testing on that when I get a moment! 🙂

@george1421
nothing for grep BUT I started to read messages…
FIGURE IT OUT
My raid controller is the problem. I don’t have two m.2 and I have two sata. The controller managed all 3 drives. Because the raid controller said it only has one raid AND that is it in fogs logs. windows knows how to deal with it because the drivers were load in during install.

I turn off raid mode and rebooted. Found all 3 drives. Now because of my setup, I am going to unplug those sata drives from the board. upload the image. THEN Grab a new one and restore with raid off. Then plug the drives back in. Should just work.

@kafluke You’d want to checkout dev-branch.

Working is more or less a stand in for Alpha RC’s now.

Dev-branch is a bug fix branch

@russel0901 Well lets dig a little deeper into what the pxe booting client is being told. Please follow the instructions here to create a network capture of the pxe booting process. This tcpdump command will only collect pxe booting traffic. Please run the commands and then upload the pcap to a file sharing site (google drive, one drive, etc.) and post the link here or IM myself or Sebastian the link so we can take a look at what the pxe booting client is being told.
https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

Your amazing! That worked! Thanks so much! and the quick response
#FOG4LIFE
until next time.

@Solo509 Best if you take a picture of the exact error on screen and post here.

From what you wrote so far I would imagine that iPXE is not having the right driver for your USB-to-Ethernet or USB-C adapter. Which iPXE binary do you use? undionly.kpxe, ipxe.efi, snponly.efi, intel.kpxe, realtek.kpxe?? Take a look at /tftpboot/ on your FOG server to see all the different ones you can try.

@Sebastian-Roth I am now, as what I expected is the case.

@Sebastian-Roth Okay so I just did a complete fresh install on a brand new server. Dev version 1.5.5.3. Absolutely no logs for me to look at inside the log viewer. Weird.

@Sebastian-Roth Thanks for your reply. Interesting to know, how FOG is starting up. As mentioned before, I think the issue was, that DHCP-Server couldn’t hand out a dynamic IP. So one of the last two requests seem to request with the wrong MAC address, as my DHCP has fixed reservations for the right MAC and should have delivered the right IP. Anyhow, as also mentioned before, the bug (or feature) is not occuring anymore as i freed up some space for dynamic hand out. So sorry, but I can’t provide additional Screenshots/Informations…

@Franklyn I am not sure I get the point of verifying the images right after the transfer as image replication is a constant loop that does a check and re-transfer (if size and or checksum don’t match) of all the image files.

Which versions of FOG do you run on the master and the storage nodes? Is it all surely 1.5.5???

Just for the notes: I pushed a fix for populating the “Working with node” column properly. But still I don’t think this is causing @TheDiskDrive’s issue. Please post a picture of the error you see and we should be able to help.

@Sebastian-Roth said in Issues after changing server IP:

Hint: I think the great changeIP script does not handle dnsmasq config changes as this is not a standard setup.

Correct, it doesn’t.