Bug 1607503 - Rescue mode is not provided on system with BIOS firmware.
Summary: Rescue mode is not provided on system with BIOS firmware.
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 30
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-23 15:36 UTC by ricky.tigg
Modified: 2020-05-26 15:29 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-05-26 15:29:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Fedora_installation_media_boot_linux_rescue (230.00 KB, application/x-tar)
2018-07-29 19:37 UTC, ricky.tigg
no flags Details

Description ricky.tigg 2018-07-23 15:36:16 UTC
Description of problem: Rescue mode is not provided on system with BIOS firmware.

Version-Release number of component: used install media is Fedora-Workstation-Live-x86_64-28-1.1.iso from official source.

How reproducible: Currently two documentations with a common subject as Fedora Installation Guide are made available for users regarding that distribution. 

- documentation-1:  https://docs-old.fedoraproject.org/en-US/Fedora/26/html/Installation_Guide/sect-boot-options-rescue.html, chapter 8.5.3

Follow suggested method 'choose Rescue a Fedora system from the Troubleshooting submenu in the boot menu'.

- documentation-2:  https://docs.fedoraproject.org/f28/install-guide/advanced/Boot_Options.html#sect-boot-options-available

Actual results: documentation-1 – on booted system, non-presence of announced entry 'Rescue a Fedora system'.
documentation-2 –  Not related to subject Rescue a Fedora system.

Expected results: System to be bootable in rescue mode using the Anaconda software on system with BIOS firmware.

Additional info: Scenario :The logical volume hosting root has to be shrink and subsequently unmounted. Tested on system with BIOS firmware.

Comment 1 ricky.tigg 2018-07-29 19:37:37 UTC
Created attachment 1471374 [details]
Fedora_installation_media_boot_linux_rescue

At last the installation boot prompt was accessible as intended which involved Esc key and I was in situation to type 'linux rescue'. Nevertheless entering rescue mode fails, producing  errors messages, that could not be copied/pasted by essence of text-based console: both pieces are part of a same output.

Comment 2 Ben Cotton 2019-05-02 21:14:37 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 2019-05-28 21:59:21 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.

Comment 4 Ben Cotton 2020-04-30 21:54:15 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 5 Ben Cotton 2020-05-26 15:29:30 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.