Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1829172 - Can't boot after upgrade from Fedora 31 to Fedora 32
Summary: Can't boot after upgrade from Fedora 31 to Fedora 32
Keywords:
Status: CLOSED DUPLICATE of bug 1765297
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 32
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-29 06:03 UTC by Le Anh Tuan
Modified: 2020-05-08 12:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-04 10:28:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Le Anh Tuan 2020-04-29 06:03:10 UTC
Description of problem:
Failed to switch root: Specified switch root path '/sysroot' does not seem to be an OS tree. os-release file is missing.

Version-Release number of selected component (if applicable):


How reproducible:
Upgrade from Fedora 31 to Fedora 31. Reboot to install

Steps to Reproduce:
1. Using GNOME Store to download upgrade
2. Reboot to install
3. Failed to switch root

Actual results:
Failed to switch root, can't boot up.

Expected results:
Normal boot, continue upgrade.

Additional info:
I'm using Lenovo X1 Carbon C6 & having Windows on the same SSD.

Comment 1 Javier Martinez Canillas 2020-05-04 10:28:09 UTC
This appears to be a duplicate of bug #1779611. Could you please test the update fixing that bug?

*** This bug has been marked as a duplicate of bug 1779611 ***

Comment 2 Javier Martinez Canillas 2020-05-08 12:09:27 UTC
Sorry, I meant a duplicate of bug #1765297

*** This bug has been marked as a duplicate of bug 1765297 ***


Note You need to log in before you can comment on or make changes to this bug.