Bug 1708845 - Failure to reboot following Fedora 30 upgrade - fail to switch root error
Summary: Failure to reboot following Fedora 30 upgrade - fail to switch root error
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 30
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: dracut-maint-list
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-11 04:43 UTC by Andrew Lucas
Modified: 2020-05-26 15:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 15:45:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1492208 0 unspecified CLOSED Failed to switch root: Specified switch root path /sysroot does not seem to be an OS tree. os-release file is missing 2023-09-07 19:02:22 UTC

Description Andrew Lucas 2019-05-11 04:43:20 UTC
Description of problem:
This bug is identical to that reported in Bug 1492208 against Red Hat Enterprise Linux 7. It occurred after a dnf upgrade from Fedora 29 to Fedora 30

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


How reproducible:
The reproducibility was described in Bug 1492208 - it involves the removal of the os-release file from /usr/lib, which is symlinked to /etc/


Steps to Reproduce:
Described in Bug 1492208

Additional info:
The result after upgrading from Fedora 29 to Fedora 30 was a boot that failed with the Failed to switch root: Specified switch root path /sysroot does not seem to be an OS tree. os-release file is missing.

I had to reboot of live distro (Clonezilla)
Activate the LVM and mount the root volume
Copy a copy of os-release from another working fedora 30 installation into mounted root's volume /usr/lib
I had problems generating a valid symlink so copied the os-release file to the mounted root's volume /etc/ directory
Successfully rebooted the installation.

Comment 1 James Tanis 2019-06-19 01:32:28 UTC
I was able to fix this without having to reboot with alive distro or go through the hassle of mounting an LVM (whose multiple steps I never remember). It's in comment in https://bugzilla.redhat.com/show_bug.cgi?id=1705651.

Comment 2 Ben Cotton 2020-04-30 21:46:37 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2020-05-26 15:45:45 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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