Bug 1374064

Summary: Booting Your Computer in Rescue Mode
Product: [Retired] Fedora Documentation Reporter: Chris Murphy <bugzilla>
Component: install-guideAssignee: Jaromir Hradilek <jhradile>
Status: CLOSED EOL QA Contact: Fedora Docs QA <docs-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: develCC: pbokoc, zach
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-21 09:21:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description Chris Murphy 2016-09-07 20:39:16 UTC 
Created attachment 1198832 [details]
screenshot

Description of problem:

This section doesn't apply to live media, as it's a graphical boot and the Anaconda rescue mode is text based so it won't work in graphical boot. Therefore inst.rescue doesn't apply, and also there is no "Rescue a Fedora System" option on lives.

What they can do is include a boot parameter:
init=/bin/bash

The problem with using rescue.target or emergency.target is Fedora lives don't set a root user password, and systemd requires a root password to use those targets.


https://docs.fedoraproject.org/en-US/Fedora/23/html/Installation_Guide/sect-boot-options-rescue.html
https://docs.fedoraproject.org/en-US/Fedora/24/html/Installation_Guide/sect-boot-options-rescue.html
Comment 2 Petr Bokoc 2024-05-21 09:21:52 UTC 
The install guide has been retired, therefore I'm closing this bug. 

If you would like to report Fedora docs bugs in the future, please use the "bug" icon on the top right of the affected page, it will take you directly to the appropriate issue tracker.