Skip to content

GRUB still looks for grub.cfg on previous subvolume after snapper rollback #722

@geckolinux

Description

@geckolinux

Hi there, on distros that are not based on openSUSE I keep running into an issue where the GRUB menu stops updating after a snapper --ambit classic rollback because GRUB is apparently looking for the /boot/grub/grub.cfg on the previous subvolume where grub-install /dev/XXX was performed. The workaround is to run grub-install again after rebooting into the new default subvolume that Snapper set. But this isn't ideal for end-users. Is there a distro-agnostic way of working around this? Or is there some fundamental concept about Btrfs and/or Snapper that I'm ignoring? Thanks for the help.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions