@Whitespire-tech @Taspharel Yeah, this is kind of strange. I checked to fog-client code and it definitely uses the domain information and shouldn’t need “domain/username” notation. Hmmmmmm. Maybe that depends on the OS you have? Which client OS is this?

@jemerson93 Usually when the “update database” fails you get an error in the apache and/or PHP-FPM logs. See my signature on where to find the logs and post here.

when it does expanding drive dev/vda4, it states fixed size.

Quite possibly yes! Can you please post the contents of the following files you find in the image directory on your FOG server: d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions

@jemerson93 said in Error after sysprep and capture (FOG related):

The only other difference I was testing on this was using a writeback cache on Proxmox instead of no cache. Would that cause it by any chance to capture the entire size of the drive?

Probably not. Have you made sure BitLocker is disabled? Did it say NTFS or RAW in the blue partclone window when capturing?

@quinniedid That definitely is strange. Can you check /etc/nsswitch.conf when you get to the shell? Please post its contents here.

@quinniedid Did you ever get to check what’s in /boot.log as suggested in the pictures?

@EduardoTSeoane This is UEFI though.

@mcturnan87 You can try using realtek.efi instead of ipxe.efi…

@george1421 The boot doesn’t get to the Linux kernel. It fails in iPXE already. See the picture below.

@jemerson93 I’ve found a bug in the resize scripts just two days ago. It only effects machines with NVMe drives…

Download the latest init files here: https://dev.fogproject.org/blue/organizations/jenkins/fos/detail/master/88/artifacts/ (init.xz and init_32.xz)

Put those in /var/www/html/fog/service/ipxe/ - rename the original ones to have a backup copy of those. As well go to the FOG web UI -> FOG Configuration -> FOG Settings -> FTP Server and increase KERNEL RAMDISK SIZE from 127000 to 275000.

@mcturnan87 said in iPXE boot Lenovo m725s:

Would a switch with spanning tree between DHCP and fog/workstation throw this error as well?

Depends on the switch model and network card but very likely yes.

I failed to mention that FOG is not running DHCP, this is run by a Windows server.

Good you mention this. Is this a failover setup with two DHCP servers? We have seen very strange issues when a DHCP cluster is not in sync.

@mcturnan87 Please download an earlier version of iPXE (https://github.com/FOGProject/fogproject/raw/c3f2e63307033a8a6b0e1c4bda27a4d646c163d6/packages/tftp/ipxe.efi) and put that in /tftpboot/ directory on your FOG server. Rename the original file so you have a copy of that too. See if booting with that makes a difference.

I think we’ve had another user the other day who had an issue with the lately updated iPXE UEFI binary as well.

@mcturnan87 Fairly sure this is a spanning tree issue. Try George’s suggestion.

@tgidwani Wow. Really glad you figured that out. I have done a lot of networking but I wouldn’t have expected the gateway setting to cause such an error. In theory the gateway information is only ever used when the host tries to connect to a machine that is not within it’s own subnet. So gateway shouldn’t play a role here as long as both were in the same subnet.

Are you able to replicate the issue when putting the GATEWAY= line back into the config??

Ok, solved that. Seemed like another one of those spanning tree issues…

@mcturnan87 Which version of FOG do you have? Please take a picture of the error on screen and post here.

@Olduser I’d suggest you update Ubuntu first. Make sure you have a full backup before you start just in case you hit any major issues. Update to 16.04 and possibly even to 18.04!

Make sure you read this as well: https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy

After that update FOG - version 1.5.6 is the latest stable as of now.

@paravane Probably best we chat, see the speech bubble in the top right corner…

@paravane What the client does at this stage is that it tries to connect to the FOG server via HTTP. Are you sure the firewall on the FOG server (or possibly some sort of layer 7 switch) is not blocking incoming HTTP port 80 traffic?

@BSZAdmin As far as I can see there is no /datastore/images/dev directory. Not sure if that information was lost while poyting only the first few lines.

See what you get from ls -al mkdir /datastore/images/dev and if it tells you that it doesn’t exist, then try manually creating the directory and files needed:

mkdir /datastore/images/dev
chmod 777 /datastore/images/dev
touch /datastore/images/dev/.mntcheck
touch /datastore/images/.mntcheck
chown -R fogproject:root /datastore/images

@paravane Is the IP address of the FOG server 10.223.254.110? Just want to make sure.

Is the switch a managed one? Is spanning tree enabled? See if you can connect FOG server and client using an unmanaged dumb mini switch that doesn’t do spanning tree at all.

@EduardoTSeoane Good point. We’ll look into this.