From Fedora Project Wiki

(update instructions slightly)
(update instructions slightly again)
Line 7: Line 7:
 
# When prompted, direct anaconda to scan your disks for existing installations
 
# When prompted, direct anaconda to scan your disks for existing installations
 
# Select ''OK'' to chroot into {{filename|/mnt/sysimage}} for your existing installation
 
# Select ''OK'' to chroot into {{filename|/mnt/sysimage}} for your existing installation
 +
# Accept the default ''shell'' menu entry to get an interactive shell
 
|results=
 
|results=
# Anaconda should prompt for language, keymap, and installation media (e.g. nfs, http, ftp, local cdrom, hard drive)
 
 
# Anaconda should start and proceed to disk scan prompt
 
# Anaconda should start and proceed to disk scan prompt
 
# Scanning your disk for existing installations should not result in a failure
 
# Scanning your disk for existing installations should not result in a failure

Revision as of 18:09, 4 April 2012

Description

This test boots any available installation method (CDROM, DVD, or network) and requests a rescue install. For details on booting into rescue mode please refer to the Install Guide .


How to test

  1. Boot the installer using any available means (CDROM, DVD, http, ftp, or nfs)
  2. At the initial screen, select the Troubleshooting menu and then the option labelled Rescue a Fedora system
  3. When prompted, direct anaconda to scan your disks for existing installations
  4. Select OK to chroot into /mnt/sysimage for your existing installation
  5. Accept the default shell menu entry to get an interactive shell

Expected Results

  1. Anaconda should start and proceed to disk scan prompt
  2. Scanning your disk for existing installations should not result in a failure
  3. Selecting OK will present you with a shell where you are able to see the previous installation mounted under /mnt/sysimage
  4. Anaconda should be able to mount (read-write and read-only) LVM, encrypted, and RAID (BIOS, hardware, and software) installations
  5. Additionally, you may be able to execute chroot /mnt/sysimage /bin/bash without error