Hello,
I recently crammed in a OpenSUSE TW into an SSD that has W10 and (ext4) LEAP 15.1. So far, I like almost everything except how clutter the bootloader looks. I used the grub-customizer to clean it up a little bit but there is still one entry that I will never use but I cannot get rid of.
“Start bootloader from a read-only snapshot”
Do you have a suggestions on how to remove this entry from GRUB?
Thanks.
-SJL
Hi
Are your running btrfs and snapper configured to take snapshots?
For my TW installation, I think so, I think those were on by default. This is the first time I am installing BTRFS.
Hi
It is needed if you want to recover to a previous snapper snapshot?
I see. Honestly time will tell but I may or may not use the snapshot feature at all. Is there a way to disable snapshots and this feature?
Hi
I would suggest just tweak the config for snapshots retained, there is a grub snapper package, you could try removing that and rebuild grub?
In between posts, there was a grub update, and combined with what grub-customizer has done and the update. Grub-customizer stopped working and more-or-less broke the menu. I deleted grub-customizer and decided to customize the grub myself.
I’ve tweaked
/boot/grub2/grub.cfg
and ran
grub2-mkconfig
I guess tweaking grub menu is easier than I thought. Also a very weird observation:
If TW “Boot Loader” configures GRUB, the menu has the snapshot mode, while booted from TW, I cannot find any entry referring to snapshot in
/boot/grub2/grub.cfg
Now, alternatively if LEAP 15.1 "Boot Loader configures GRUB, the menu has no snapshot. Also the boot options for TW are broken. Upon inspection the TW boot options has some clutters of “/@/…/1/snapshot/…/” before /boot. I can edit the GRUB entry to boot from TW.
So to get the desired result, I currently do:
/boot/grub2/grub.cfg
grub2-mkconfig
Not touch Boot Loader from TW and possibly repeat this procedure at every release from TW.
Hi
There is a snapshot entry residing in /.snapshots did you remove grub2-snapper-plugin?
Edit /etc/default/grub and have: SUSE_BTRFS_SNAPSHOT_BOOTING=“false”. Then run: grub2-mkconfig -o /boot/grub2/grub.cfg
Remove and lock grub2-snapper-plugin package.
Whatever you changed in the first step will be overwritten next time grub.cfg is regenerated, meaning next time kernel or grub2 are updated. Actually either it was already overwritten by the second step or the second step was entirely useless.
You must reinstall grub2 after changing this variable otherwise generated grub.cfg will be incompatible with binaries.
The secondstep updates the grub loader with /boot/grub2/grub.cfg that I modified.
grub2-mkconfig -o /boot/grub2/grub.cfg
will generate a new config file but just running
grub2-mkconfig
updates the grubloader with the existing /boot/grub2/grug.cfg
I will set SUSE_BTRFS_SNAPSHOT_BOOTING=“false”
for /etc/default/grub
and I will also remove and lock grub2-snapper-plugin
To be exact, the prefix is
/@/.snapshots/1/snapshot
and it appears everytime LEAP15.1 Bootloader calls
grub2-mkconfig /boot/grub2/grub.cfg
even with the snapshot feature set to false on
/etc/default/grub
from LEAP15.1 and TW
Which will overwrite any modifications to grub.cfg you have done earlier.
but just running
grub2-mkconfig
updates the grubloader with the existing /boot/grub2/grug.cfg
I am not sure what you are talking about. This command does not update anything - this command just prints new content of grub.cfg to stdout. It does not affect content of /boot/grub2/grub.cfg in any way. Also I do not understand what you mean with “update bootloader”. grub2-mkconfig does not make any changes to bootloader and never did.
From my observation, if I don’t run grub2-mkconfig after making changes to /boot/grub2/grub.cfg, when I reboot, the changes I made to the /boot/grub2/grub.cfg do not happen. However it does if I do run grub2-mkconfig without the overwriting feature.
Just as a follow up. Doing as karlmistelberger suggested worked. Editing and setting
/etc/default/grub
SUSE_BTRFS_SNAPSHOT_BOOTING="false"
followed by
CODE]grub2-mkconfig -o /boot/grub2/grub.cfg
In addition, I was able to revert the mess that grub-customizer created since the update by going into
/etc/grub.d/
and removing everything ending with _proxy
apparently grub-customizer creates proxy boot information to delete/create/rearrange boot order and it takes one grub upgrade (which for TW is 1~2 times a week) to break grub-customizer.
Later I will look into what LEAP 15.1 does to TW boot information because it adds
/@/.snapshots/1/snapshot
in front of all TW boot options when LEAP 15.1 updates its boot loader/grub