|
Bugzilla – Full Text Bug Listing |
| Summary: | grub 2 don't display snapshot entry | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Marc collin <marc.collin> |
| Component: | Bootloader | Assignee: | Josef Reidinger <jreidinger> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | jreidinger, marc.collin, mchang |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
grub.cfg
grub-snapshot.cfg |
||
|
Description
Marc collin
2018-02-17 02:41:26 UTC
Hi Marc, This is fixed. See also bsc#1079780. Thanks for reporting. *** This bug has been marked as a duplicate of bug 1079780 *** took today update with kernel 4.15.4-1... same issue... will be available soon? get update and problem still there Hi Marc,
Let's check first what is your in package changelog ?
> rpm -q --changelog grub2-snapper-plugin
Thanks.
content passte to https://pastebin.com/TS5Zi3Yj last entry is feb 13 * Tue Feb 13 2018 mchang@suse.com - Fix incorrect check preventing the script from running (bsc#1078481) * 80_suse_btrfs_snapshot Yes, you're running the latest build. Would you please also attach the related grub configuration file ? /boot/grub2/grub.cfg /.snapshots/grub-snapshot.cfg Thanks. Created attachment 761900 [details]
grub.cfg
Created attachment 761903 [details]
grub-snapshot.cfg
i provided you file asked Your grub.cfg suggests that /boot is a separate partition which does not meet the requirement of snapshot booting. The /boot and / has to be the same btrfs partition and (default) subvolume managed by snapper. will need to do a full reinstall? is it possible with tumbleweed installer to have lvm encrypted partition with snapshot? seem like yast always propose a separate partition for boot when we use encryption (In reply to Marc collin from comment #12) > will need to do a full reinstall? I think so. Although it is possible to tweak manually to make it work, there's no warranty then. (In reply to Marc collin from comment #13) > is it possible with tumbleweed installer to have > lvm encrypted partition with snapshot? > seem like yast always propose a separate partition for boot when we use > encryption Maybe Josef could help in explaining the behavior ? I could not foresee problem of doing it but could be my lack of understanding to the scenario. (In reply to Michael Chang from comment #15) > (In reply to Marc collin from comment #13) > > is it possible with tumbleweed installer to have > > lvm encrypted partition with snapshot? > > seem like yast always propose a separate partition for boot when we use > > encryption > > Maybe Josef could help in explaining the behavior ? I could not foresee > problem of doing it but could be my lack of understanding to the scenario. Installer propose separated /boot when MBR gap on disk is not big enough to hold grub2, so we propose separate /boot to be able to boot. To verify it I will need y2logs where it should be written. Hi Josef, Here I reassign to you, as it seems to be specific configuration/setup to be clarified. Thanks. Marc - I will need logs from installation to see that it is really caused by missing MBR gap seem my problem was because my boot partition was on different partition then my root... (In reply to Marc collin from comment #19) > seem my problem was because my boot partition was on different partition > then my root... yes, that is true. Only think we can do here is to check why /boot partition is created, which I can read from logs. The most probable variant is that disk does not have big enough space in MBR gap. i think we can close it |