Hide Forgot
Description of problem: after initiating the DNF process to upgrade and invoking the DNF reboot command, the system fails to boot for the upgrade with "starting Switch root" hang. Version-Release number of selected component (if applicable): How reproducible: system unable to be logged into after the failure Steps to Reproduce: 1. 2. 3. Actual results: Expected results: upgrade should proceed without error. Additional info: unable to chroot into the root system and rescue fails with the same error.
> rescue fails with the same error. Can you describe what you tried to boot in rescue mode and what the error looked like?
Sure, rescue via the grub menu. after removing rhgb and quiet from the kernel parameters, I get; systemd [1] failed to execute /sbin/init, giving up: Input/output error
This looks like filesystem corruption. A missing library generates a different error (error while loading shared libraries: ...: cannot open shared object file: No such file or directory), as does a truncated executable (segmentation fault). You should check your root filesystem. http://k.japko.eu/fedora-fsck-root.html has some nice instructions.
I had checked the filesystem with Gparted from Puppy Linux and it showed no problems. Let me look at a few more things per your link and respond. The filesystem was fine before the upgrade, but I wonder if there is a grub issue and I will look at that as well. Let me know if I should continue this inquiry or if this is more appropriate for the forums (if this does not look like a problem that is appropriate for this forum).
A file system check checks file system metadata. It does not check if there are bad sectors, etc. It would be probably best to start a rescue system (e.g. the one you used for fsck), and try to execute /sbin/init from there. If there's an fs error, it'll tell you.
I have unable to resolve this issue and all rescue system attempts have failed to get into the root filesystem. Looks like I will need to start from scratch and reinstall Fedora from scratch. This is an ssd disk that I have been using for about I year and I need a working system. Thanks for your help.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.