GRUB configurations generated by deploy and delete-generations differ, interfering with boot process

Tomas Volf wrote 1 months ago

Recipients:(address . bug-guix@gnu.org)

Message-ID:878qqwihgp.fsf@wolfsden.cz

For some reason the generated configuration by `guix system deploy'

differs from the one generated by `guix system delete-generations'. The

one from `delete-generations' is missing the extra-initrd, interfering

with the boot of the system.

From `guix deploy':

Toggle snippet (6 lines)

menuentry "GNU with Linux 6.12.11" {

[..]

initrd /disk/key.cpio /gnu/store/id8k7j24c4ijxiw1pgfsp0pg2ws52wkd-combined-initrd/initrd.img

}

From `guix system delete-generations':

Toggle snippet (6 lines)

menuentry "GNU with Linux 6.12.11 (#42, 2025-01-27 11:54)" {

[..]

initrd /gnu/store/id8k7j24c4ijxiw1pgfsp0pg2ws52wkd-combined-initrd/initrd.img

}

Ignoring that the menuentries are differently named (which is bit weird,

but does not really matter), notice that the `initrd' lines differ.

Reproduction is simple:

0. Configure system with bootloader with extra-initrd configured.

1. Run `guix deploy' few times.

2. Look at first menuentry in /boot/grub/grub.cfg.

3. Run `guix system delete-generation $OLDEST'.

4. Compare first menuentry in /boot/grub/grub.cfg to step 2.

--> Notice the differences (name, initrd, ...).

5. Run `guix deploy' once more.

--> Notice it got fixed again.

Workaround is to always run `guix deploy' once more after deleting

generations, even if there is nothing to deploy. It will still

regenerate the grub.cfg, fixing things up.

But it would be great if it "just worked".

Have a nice day,

Tomas

There are only two hard things in Computer Science:

cache invalidation, naming things and off-by-one errors.