[Bug 964553] New: Impossible to boot from read only snapshot
http://bugzilla.opensuse.org/show_bug.cgi?id=964553 Bug ID: 964553 Summary: Impossible to boot from read only snapshot Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: gtettamanzi@gmail.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 Build Identifier: Info: grub2 2.02~beta2-54.1; grub2-snapper-plugin 2.02~beta2-54.1; snapper 0.2.10-1.1 Description Whatever snapshot is chosen on the grub list, it does not boot; The sequence is: - turn on the rig - choose any of the listed snapshots - "Bootable snapshot #" <enter> - "If OK, run 'snapper rollback' and reboot." <enter> After this it loops on the last step - the only way to exit the loop is pressing Ctrl+Alt+Del. Reproducible: Always Steps to Reproduce: 1.Start the rig 2.on grub menu, choose "Start boot loader from a read-only snapshot" 3.Choose one in the listed snapshots, #X 4.press enter on "Bootable snapshot #X" 5.press enter on "If OK, run 'snapper rollback' and reboot." Actual Results: Looping on step 5 and no booting Expected Results: Booting from the chosen read only snapshot -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c2
--- Comment #2 from Gabriele Tettamanzi
(In reply to Gabriele Tettamanzi from comment #0)
Steps to Reproduce: 1.Start the rig 2.on grub menu, choose "Start boot loader from a read-only snapshot" 3.Choose one in the listed snapshots, #X 4.press enter on "Bootable snapshot #X"
You should not press enter on the title, you should select a boot entry. Most likely the second or third entry.
The first line is not a title: it's one in items of the list; however choosing an entry below the first does not change the result: it does not boot. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c3
Jiri Srain
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c4
Gabriele Tettamanzi
So, what happens after you type 'snapper rollback' and reboot? Is there any output of the snapper rollblack command? You wrote it loops, which sounds like it boots...
There's no error message, because it does nothing. If I edit the entry, this is what it is displayed: "If OK, run 'snapper rollback' and reboot." true; It loops showing this message as an entry. I attach grub.cfg -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c5
--- Comment #5 from Gabriele Tettamanzi
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c6
--- Comment #6 from Gabriele Tettamanzi
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
Arvin Schnell
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c7
Jiri Srain
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c8
Jiri Srain
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c9
--- Comment #9 from Axel Braun
Should this bug be caused by LVM?
Probably not, as I dont have LVM, but the same problem -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c10
Axel Braun
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c11
--- Comment #11 from Gabriele Tettamanzi
PS: I think the bug severity is 'major' as you only boot into a snapshot when you have a serious problem. And this feature - heavily advertised - is broken!
Agrred. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c12
--- Comment #12 from Gabriele Tettamanzi
(In reply to Axel Braun from comment #10)
PS: I think the bug severity is 'major' as you only boot into a snapshot when you have a serious problem. And this feature - heavily advertised - is broken!
Agrred.
Typo! Agreed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c16
Gabriele Tettamanzi
(In reply to Gabriele Tettamanzi from comment #2)
(In reply to Thorsten Kukuk from comment #1)
(In reply to Gabriele Tettamanzi from comment #0)
Steps to Reproduce: 1.Start the rig 2.on grub menu, choose "Start boot loader from a read-only snapshot" 3.Choose one in the listed snapshots, #X 4.press enter on "Bootable snapshot #X"
You should not press enter on the title, you should select a boot entry. Most likely the second or third entry.
The first line is not a title: it's one in items of the list; however choosing an entry below the first does not change the result: it does not boot.
Sorry but the first entry is used to display the snapshot number and not used for booting, because people may need to know what the snapshot this menu belongs to and currently no good means in boot menu for displaying that, so that we carry first menu entry title to display it until a good solution can be found.
The second or third are your snapshotted boot (menu)entry, what's the error message that it does not boot ?
I red again my post, I did not want to criticize in any way, I'm sorry if it sound rude - however I think that the first item could be more explicative, kind of "don't choose me, choose one in the list below" :-). I split my answer in two parts. First, as I wrote, there was no way to boot whichever entry I chose, and I got no error - just a black screen in case of second entry. Second, it looks like the last grub fixed the issue, I mean grub2 2.02~beta2-55.1. I'm going to fresh net install the system, in order to clean up messy things around. I'll be reporting back as soon as I've test booting from snapshot on the fresh installed system. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c18
--- Comment #18 from Gabriele Tettamanzi
(In reply to Gabriele Tettamanzi from comment #16)
(In reply to Michael Chang from comment #13)
(In reply to Gabriele Tettamanzi from comment #2)
(In reply to Thorsten Kukuk from comment #1)
(In reply to Gabriele Tettamanzi from comment #0)
Steps to Reproduce: 1.Start the rig 2.on grub menu, choose "Start boot loader from a read-only snapshot" 3.Choose one in the listed snapshots, #X 4.press enter on "Bootable snapshot #X"
You should not press enter on the title, you should select a boot entry. Most likely the second or third entry.
The first line is not a title: it's one in items of the list; however choosing an entry below the first does not change the result: it does not boot.
Sorry but the first entry is used to display the snapshot number and not used for booting, because people may need to know what the snapshot this menu belongs to and currently no good means in boot menu for displaying that, so that we carry first menu entry title to display it until a good solution can be found.
The second or third are your snapshotted boot (menu)entry, what's the error message that it does not boot ?
I red again my post, I did not want to criticize in any way, I'm sorry if it sound rude - however I think that the first item could be more explicative, kind of "don't choose me, choose one in the list below" :-).
I think we have to consider it, thanks.
You are not the first one reported that attempting to boot first entry is unbootable. I think we should try to improve it to be less confused. Besides it adds unwanted side effects in shifting the default entries in snapshotted grub.cfg if 'number' is used to index the entries. The proposed solution would be to use grub theme's label, but it lacks the ability to display text at run time so that requires patching grub2. And also it's not available in naked or text based menu without theme.
Another one would be to specifically handle first entry named the title 'bootable snapshot #..' to separate it from others, made it not counted as valid thus skipped and unselectable. but that's also ugly imho.
I split my answer in two parts.
First, as I wrote, there was no way to boot whichever entry I chose, and I got no error - just a black screen in case of second entry.
It could also be an issue from X, booting to text mode usually works for me.
Second, it looks like the last grub fixed the issue, I mean grub2 2.02~beta2-55.1.
I'm going to fresh net install the system, in order to clean up messy things around. I'll be reporting back as soon as I've test booting from snapshot on the fresh installed system.
Thanks and waiting for your result.
I tested it twice on my fresh install: it worked in both tests. In the second one, it hung on Plymouth splash screen, I switched to console mode (alt+tab) and I saw a message "waiting for starting job 1m35s", after 1m35s it booted. I guess it's something Plymouth related. Let me note that in addition of looking exactly like a menu entry, the line with "Bootable snapshot #X" has also the time count down and the automatic boot at the end. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c19
--- Comment #19 from Axel Braun
Please try this step instead:
1.Start the rig 2.on grub menu, choose "Start boot loader from a read-only snapshot" 3.Choose one in the listed snapshots, #X
After that you'll see sth like:
Bootable snapshot #10 openSUSE Tumbleweed Advanced options for openSUSE Tumbleweed
Select 'openSUSE Tumbleweed' or 'Advanced options for openSUSE Tumbleweed' if you want to boot an older kernel from that given snapshot#10.
As said, what I saw was: * Boot PC * "Start bootloader from a read-only snapshot" * Choose any of the listed snapshots * "Bootable snapshot #<num>" * "If OK, run 'snapper rollback' and reboot." * error: can't find command `true'. <newline> Press any key to continue... I suspect that , for whatever reason, no profile for snapper was created during installation. (When I went into snapper for the first time it told me that 'no profile exists. You need to create a profile... etc') After creation of a profile it showed the above options. Can we trace this somehow? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c20
--- Comment #20 from Michael Chang
(In reply to Michael Chang from comment #15)
I suspect that , for whatever reason, no profile for snapper was created during installation. (When I went into snapper for the first time it told me that 'no profile exists. You need to create a profile... etc') After creation of a profile it showed the above options. Can we trace this somehow?
Did your btrfs root partition more than 20 GB or such ? The btrfs snapshot requires enough size to be enabled by default for new installation. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c21
--- Comment #21 from Axel Braun
I suspect that , for whatever reason, no profile for snapper was created during installation. (When I went into snapper for the first time it told me that 'no profile exists. You need to create a profile... etc') After creation of a profile it showed the above options. Can we trace this somehow?
Did your btrfs root partition more than 20 GB or such ? The btrfs snapshot requires enough size to be enabled by default for new installation.
Yes, the root partition has some 45 GB -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=964553
http://bugzilla.opensuse.org/show_bug.cgi?id=964553#c22
Tristan Miller
participants (1)
-
bugzilla_noreply@novell.com