@jmason You seem to get into the details of FOG fairly quickly! Well done. It’s great to see people reading the docs and forums and making their way. Let’s see, where shall I start.
PartImage - switches on its own to Partclone Gzip after I attempt to deploy a captured image.
Partclone Gzip is definitely the better choice. I know we still had an issue in FOG 1.5.5 which made it default to Partimage on a fresh install. You don’t really want that legacy stuff. Use Partclone Gzip oder Zstd.
but there is no OS Dropdown selection item for a multisetup
Absolutely right and I’d really like to add that at some point in the future. But it makes things a lot more complex and therefore we have not added it yet. In very many cases one or the other OS choice is working for multisetup but sometimes needs a bit of adjustment. That said, it’s still possible that FOG is not able to handle your setup (combination of boot loaders, partition layouts and all that) yet but if we find out what’s wrong I am happy to add a fix!
So during the deploy PXE boot with Linux(50) selected as the OS, I receive: …
Let’s try to tackle this. Please schedule another debug deploy task. Start up the client and fire up
fog when you get to the shell. Step through and when you are back to the console after the error please type
sgdisk -gl /images/DELL7730_Win10_Centos7/d2.mbr /dev/nvme1n1 (most probably returns an error as well. Please take a picture or copy&paste the error message if you are connected via SSH to the client)
When selecting Windows as the OS for the image it appears to get further…
That’s kind of interesting. While I have not had the time to actually look through the scripts to figure out the difference I find it funny that it proceeds but later on seems to have restored the partitions but is failing to actually push out the contents of the image files to those partitions. This part might be harder to debug so I’d stick to OS=Linux (50) for now. Let’s see how far we get.
OS=Linux (50) should handle Linux legacy BIOS (MBR) boot loaders a bit better by the way. You say you think it’s true UEFI. So maybe this stuff is not much relevant at all. Well, let’s see what you get from the debug session mentioned above.