Description of problem: I had some issue with btrfs, so I wanted to run btrfsck on it. As btrfsck does not work on mounted filesystem, I've tried to reboot into rescue initrd in emergency mode. Unfortunately, this did not work for me - I have the root partition encrypted, and the startup insisted on entering the password to unlock the partition, there was no (obivous) way to skip this step. And after entering the password, it just got remounted as real root instead of the rescue initrd one, effectively hiding the initrd contents and disalowing me to umount it manually as it got into use. Version-Release number of selected component (if applicable): (don't know, the system is dead now ... fully updated Fedora 20, as of May 2nd) How reproducible: always Steps to Reproduce: 1. reboot 2. in grub, choose the rescue option, append "emergency" 3. try to get into the initrd shell without mounting the real root Actual results: impossible Expected results: you get an option to skip unlocking encrypted partitions, and if running from the rescue initrd, the root stays on the ramdisk and is not remounted to the real root Additional info: note that this may be actually two problems in one, also something in the way the rescue option is composed ... please feel free to split and create a new blocking/dependent bug for other components ... I just don't know what is involved in the proces, I just file for systemd because I believe it is its job to mount the fs
> 3. try to get into the initrd shell without mounting the real root - add "rd.break rd.shell" to the kernel command line - you will be dropped to the dracut shell - /sysroot contains the root filesystem
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.
(In reply to Harald Hoyer from comment #1) > > 3. try to get into the initrd shell without mounting the real root > > - add "rd.break rd.shell" to the kernel command line > - you will be dropped to the dracut shell > - /sysroot contains the root filesystem I fail to find this trick in documentation for Fedora 22 => reopening (at least improve the docs, please) in the past, there used to be a chapter on system recovery, see e.g. https://docs.fedoraproject.org/en-US/Fedora/14/html/Installation_Guide/ap-rescuemode.html - which doesn't mention that either, but at least explains some bits about 'rescue' and 'emergency' but F14 is dark past now, and if btrfs (unlike older filesystems) needs NOT to be mounted at all, simply having it ro isn't sufficient, then new recovery workflow has to be invented in this case, it'd be much more user friendly (RFE!) if there would be a question like "Do you want to mount root filesystem and be switched to it?" when answering "No" would drop the user to the emergency initrd containing recovery tools, instead of having to pass some un- (poorly) documented options to the kernel commandline ... see also https://bugs.freedesktop.org/show_bug.cgi?id=85200
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.