Issue with FOG Deployment - Disk Not Bootable After Deployment (Debian 12)

[DzOnizuka]

Hello,

I’m currently facing an issue with FOG when deploying a Debian 12 image to a target machine. Here’s the situation:

1. I captured the image of the source machine using FOG with Partclone as the imaging tool.

2. The image deployment to the target machine completes without errors.

3. However, after deployment, the target machine is not bootable. It seems the bootloader (GRUB) is not correctly configured or missing. It boots from the FOG menu when I choose to boot from the HDD, but it seems like some kind of live boot because when I reboot, it is no longer possible to boot from the HDD. I have tried several actions in the BIOS/UEFI menu.

I suspect the problem lies in Partclone not handling the bootloader (GRUB) installation properly during the image deployment process, especially in an EFI/UEFI environment.

Verified the mode of boot (UEFI/Legacy) is consistent on both source and target machines.

My questions are:

1. Is there a way to configure FOG to properly handle GRUB during deployment, especially for UEFI systems?

2. Would switching the imaging tool in FOG from Partclone to DD help in this case, or is there another recommended approach?

3. Can a post-deployment script be used in FOG to automate GRUB reinstallation? If so, how can this be implemented effectively?

I’d appreciate any guidance or solutions for this issue, especially tips to ensure a seamless bootloader setup after deployment.

Thank you in advance for your help!

[Tom Elliott]

@DzOnizuka I dont think it’s grub specifically but rather the fstab.

Debian, and Ubuntu, tend to set the /etc/fstab to use the drive’s UUID to indicate which drive to load the OS from. I’ll bet if your drive layouts are consistent at least (like for like) if your replace the uuid and point specifically at the device name (/dev/sda1, /dev/sdb2 etc…) things would work perfectly fine.

[DzOnizuka]

@Tom-Elliott Thanks for your reply. Should I disable the “Reproduce ?” in the image options?

[Tom Elliott]

@DzOnizuka No you’d have to change your OS /etc/fstab to use the device names over the UUID’s.

Otherwise what you’re capturing is an FSTAB of the “golden” machine, then putting it on a different machine, who’s UUIDs are not the same thing.

[DzOnizuka]

@Tom-Elliott Thank you Tom. I change the UUID’s by the devices names on the /etc/fstab on the “golden” machine before I capture a new image and I redeploy it, but apparently it doesn’t change anything