Bug 1404240 - Upgrade from fedora 24 to 25 - failed to start switch root, /sysroot is not on os tree, os-release file is missing.
Summary: Upgrade from fedora 24 to 25 - failed to start switch root, /sysroot is not...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 24
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-13 13:04 UTC by jdw
Modified: 2016-12-19 12:31 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-19 12:31:19 UTC
Type: Bug


Attachments (Terms of Use)

Description jdw 2016-12-13 13:04:25 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 jdw 2016-12-13 13:15:55 UTC
Used dnf to upgrade from fedora 24 to fedora 25. Upgrade seemed to work but I cannot get to a login screen. I got into grub2 and in looking at the log file I see an error message stating: "failed to start switch root, /sysroot is not on os tree, os-release file is missing". I do not know what the file is and looked on google and fedora forums for possible answers but could find nothing.  As of right now I am booting from my Workstation Live iso since my rescue disk does not seem to work either, so I am having a lot of trouble getting more information or even trying to fix anything.

Comment 2 Igor Gnatenko 2016-12-19 12:31:19 UTC
Unfortunately, bugzilla is not the place where people get help to fix broken system. Probably something went wrong during upgrade.

I would recommend to write to https://ask.fedoraproject.org or to users mailing list with logs from dnf and system-upgrade (in journald).


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