Проблема с grub

[slawa.jad]

Good afternoon, after rolling out the Debian system image, a grub rescue error occurs. When creating the image, I used the settings for the image type - Single Disk - Resizable and Multiple Partition Image - Single Disk (Not Resizable)
Usage:
Ubuntu server: 22.04
FOG Project: 1.5.10

[Tom Elliott]

@slawa-jad I suspect your grub file is referencing the disk in GUID format, and you should change the guid to the position of the boot drive itself:

/dev/sda vs (383838383-7837-8737-8376-373789091234)

[slawa.jad]

@Tom-Elliott Please tell me how and where to do it

[slawa.jad]

@Tom-Elliott I looked at the error again. I have a mistake - symbol. ‘grub_is_lockdown’ not found

[Tom Elliott]

@slawa-jad I don’t think grub_is_lockdown is the issue, just the message presented.

If you’re able to load up the original machine you captured the image from, look at your /etc/fstab file.

I suspect you’ll see something to the effect of:

UUID=a2476193-12cf-4601-a38d-6c798fc42708 /boot                   ext4    defaults        1 2
UUID=AACD-BEFE          /boot/efi               vfat    umask=0077,shortname=winnt 0 2

If your file.

This is where things are breaking down.

Change the UUID= portion to the actual drive name.

The boot efi part, I’m not 100% certain what to change it to, but I would suspect probably

/dev/sda1 /boot                   ext4    defaults        1 2
/dev/sda2          /boot/efi               vfat    umask=0077,shortname=winnt 0 2

This is just my guess. I would not make these changes on the “originally captured” machine but rather make it on one of the machines that you deployed to and fix it there. Once it’s fixed, I’d then suggest re-capturing the image from that “now working” machine and deploy as freely as needed.