📖 ~1 min read
Table of contents
Symptom & Impact
After `snapper rollback`, the next boot still lands on the previous default snapshot.
Environment & Reproduction
Seen on UEFI SLES 16 systems where GRUB2 default entry was overridden manually.
Root Cause Analysis
`grub2-mkconfig` did not regenerate the default-subvolume entry after the rollback.
Quick Triage
Inspect `/boot/grub2/grub.cfg` and confirm the active subvolume with `btrfs subvolume get-default /`.
Step-by-Step Diagnosis
Compare `snapper list` default flag with `grub2-editenv list` saved entry.

Solution – Primary Fix
Run `snapper rollback ` then `grub2-mkconfig -o /boot/grub2/grub.cfg` and reboot.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Use `transactional-update grub.cfg` on transactional systems instead of regenerating manually.
Verification & Acceptance Criteria
After reboot `snapper status` shows the chosen snapshot as default and read-write.
Rollback Plan
Re-run rollback to the prior snapshot if the new default introduces regressions.
Prevention & Hardening
Avoid manual edits to `/etc/default/grub` outside the configuration management workflow.
Related Errors & Cross-Refs
Often co-occurs with `efibootmgr` showing the wrong boot order.
Related tutorial: View the step-by-step tutorial for sles-16.
View all sles-16 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
Snapper rollback workflow and GRUB2 integration on SLES 16.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.