[Bug 1045713] New: Upgrading legacy mode system with EFI mode stick breaks the system
http://bugzilla.suse.com/show_bug.cgi?id=1045713 Bug ID: 1045713 Summary: Upgrading legacy mode system with EFI mode stick breaks the system Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: adrien.plazas@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- I had a Leap 42.2 install that I wanted to upgrade to Tumbleweed; to do so I loaded a recent TW on a USB stick, booted from it in EFI mode, and from the stick's menu I selected the Upgrade (or Update, I don't remember the phrasing) option. The upgrade went fine until the very end when I was presented an error message, IIRC it stated that the EFI partition couldn't be found. When booting the system, grub tells me that linuxefi can't be found and hence the system doesn't start. It looks like I upgraded a system installed in legacy mode with a stick in EFI mode, and that the upgrade was performed as if the installed system was in EFI mode; now my install is in a weird in-between state. I would expect the upgrade to be made from the installed mode to the same one, despite the mode the upgrade is performed in, or in the worst case I would expect to be asked to perform the upgrade in the adequate mode. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1045713
http://bugzilla.suse.com/show_bug.cgi?id=1045713#c1
--- Comment #1 from Adrien Plazas
http://bugzilla.suse.com/show_bug.cgi?id=1045713
http://bugzilla.suse.com/show_bug.cgi?id=1045713#c2
--- Comment #2 from Steffen Winterfeldt
http://bugzilla.suse.com/show_bug.cgi?id=1045713
http://bugzilla.suse.com/show_bug.cgi?id=1045713#c3
Steffen Winterfeldt
http://bugzilla.suse.com/show_bug.cgi?id=1045713
http://bugzilla.suse.com/show_bug.cgi?id=1045713#c4
--- Comment #4 from Adrien Plazas
In any case, if you have them, please attach yast logs:
Unfortunately I don't have them anymore, sorry. :/ -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com