Latitude 7202 FOG PXE menu freezes

[dwcoleman]

@george1421

Thanks, I was able to pull an image this morning. I’m having an issue restoring it to another tablet, I’m getting a partition error about an unclean mount. I"m working my way through that issue.

Would using UEFI be easier you think?

I also tried ipxe.pxe, it wouldn’t even boot to the menu.

Thanks

[george1421]

@dwcoleman said in Latitude 7202 FOG PXE menu freezes:

I was able to pull an image this morning. I’m having an issue restoring it to another tablet

Did you sysprep the image before you captured it?

The unclean mount (I feel not the correct error) we see with windows 10 if its not shut down correctly before image capture. Remember with Win10 shutdown is an enhanced sleep mode not a true shutdown.

If you use sysprep before cloning, then have syspre power off the computer. That will properly close the disk for cloning.

[george1421]

@dwcoleman said in Latitude 7202 FOG PXE menu freezes:

I also tried ipxe.pxe, it wouldn’t even boot to the menu.

If you want uefi mode, two things.

1. Make sure that secure boot is disabled or you WILL have an issue with cloning.
2. If ipxe.efi doesn’t work try the older kernel ipxe7156.efi That kernel does seem to work on the MS Surface Pros better than ipxe.efi.

[dwcoleman]

@george1421

You’re right, that was the issue. I don’t have a lot of experience imaging UEFI.

The FOS solution should work for us, I’m booting a second tablet currently that I imaged and it seems fine.

Thanks so much for the help.

Darren

[george1421]

@dwcoleman said in Latitude 7202 FOG PXE menu freezes:

You’re right, that was the issue

Please clarify what was the issue for others that might find this thread.

And great on being able to image.

[dwcoleman]

I just needed to sysprep the Windows 10 image and I was able to image it successfully.

[dwcoleman]

So I created a new permanent VM for my Ubuntu installation. I then added a second volume and moved /images successfully, mounted it, and it works fine for ipxe clients.

I can no longer USB image the 7202 tablets though using Fog 1.4.2 on the new server. To prove this out I fired up my local VM and updated grub.cfg and I’m pulling an image using Fog 1.4.1.

Error is below. I’m pretty much a newbie to Fog, do I need to update my Fos USB image

Thanks, Darren

[Sebastian Roth]

@dwcoleman Re-creating the USB FOS image is a good idea. Could be that the addition of ZSTD compression is causing an issue here?

[dwcoleman]

Just recreated the image using @george1421 's excellent instructions, same error persists.

https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image

Thanks

[Sebastian Roth]

@dwcoleman Do you have enough free disk space on your new server (/images partition)? Please post the output of df -h and ls -al /images on your FOG server here in the forum.

On the other hand… why would it fail that early (calculating bitmap…) if disk space is an issue? Exit code 141 I read means broken pipe. Why would partclone fail to read /dev/sda1 and not be able to deliver data trough the pipe? (just thinking out loud here)

[Quazz]

Afaik 141 is a pipe issue. Meaning that while partclone is still piping data, the compression manager has already exited (assuming). As to what caused it, I have no idea.

[george1421]

@Sebastian-Roth said in Latitude 7202 FOG PXE menu freezes:

On the other hand… why would it fail that early (calculating bitmap…) if disk space is an issue?

FWIW: The disk space issue is a bit misleading, we discovered it basically means that partclone failed for some reason and there is no way to trap the error programmatically.

[dwcoleman]

See below. /dev/sdb1 was my second 700GB volume that I added to the system. I thought it was the problem at first but verified it wasn’t.

I might downgrade to 1.4.1 again at this point since I"m running out of ideas.

[Quazz]

@dwcoleman What imagemanager do you use for this image? (on the image definition page)

[dwcoleman]

Partclone Gzip

I have two other images captured via PXE using Partclone Gzip that worked.

[Sebastian Roth]

@dwcoleman Do you still see this issue? Have you tried on different devices? Always the same problem?