From Fedora Project Wiki
(add the 'associated criterion' block) |
Chrismurphy (talk | contribs) (fix rescue mode install guide URL) |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template:Associated_release_criterion| | {{Template:Associated_release_criterion|Alpha|rescue-mode}} | ||
{{Template:Associated_release_criterion| | {{Template:Associated_release_criterion|Beta|rescue-mode}} | ||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=This test boots any available installation method (CDROM, DVD, or network) and requests a '''rescue''' | |description=This test boots any available installation method (CDROM, DVD, or network) and requests a '''rescue''' mode. For details on booting into rescue mode please refer to the [https://docs.fedoraproject.org/en-US/fedora/f{{FedoraVersion}}/install-guide/advanced/Boot_Options/#sect-boot-options-rescue Install Guide] . | ||
|actions= | |actions= | ||
# Boot the installer using any available non-Live means (anything except {{filename|Live.iso}}) | # Boot the installer using any available non-Live means (anything except {{filename|Live.iso}}) | ||
Latest revision as of 19:57, 3 September 2020
Associated release criterion
This test case is associated with the Basic_Release_Criteria#rescue-mode release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
This test case is associated with the Basic_Release_Criteria#rescue-mode release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
Associated release criterion
This test case is associated with the Fedora_42_Beta_Release_Criteria#rescue-mode release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
This test case is associated with the Fedora_42_Beta_Release_Criteria#rescue-mode release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion. If so, please file a bug and nominate it as blocking the appropriate milestone, using the blocker bug nomination page.
Description
This test boots any available installation method (CDROM, DVD, or network) and requests a rescue mode. For details on booting into rescue mode please refer to the Install Guide .
How to test
- Boot the installer using any available non-Live means (anything except
Live.iso) - At the initial screen, select the Troubleshooting menu and then the option labelled Rescue a Fedora system
- When prompted, direct anaconda to scan your disks for existing installations
- Select OK to chroot into
/mnt/sysimagefor your existing installation - Accept the default shell menu entry to get an interactive shell
Expected Results
- Anaconda should start and proceed to disk scan prompt
- Scanning your disk for existing installations should not result in a failure
- Selecting OK will present you with a shell where you are able to see the previous installation mounted under
/mnt/sysimage - Anaconda should be able to mount (read-write and read-only) LVM, encrypted, and RAID (BIOS, hardware, and software) installations
- Additionally, you may be able to execute
chroot /mnt/sysimage /bin/bashwithout error