I followed the documentation on the creation of the rescue disk and found
that rescue.img was not on disk 1 of the Red Hat Linux v 6.1 CD.
There has been a change in the way that rescue mode works. Rescue mode is now a
part of the distribution media, so to boot rescue mode, you just put in the
cdrom or boot disk and type "linux rescue" at the boot prompt. This will throw
you into the rescue mode and you will be able to proceed as normal.
NOTE: after booting (other than when booting directly from the cd) the installer
will proceed just as the install program did . . . that is, if you are booting
using the boot.img disk, then the installer will ask where the rescue image is,
on the cdrom or on the hard drive. Similarily, when booting from the
bootnet.img disk, you will need to provide the path to the source files so that
the rescue image file can be retrieved.
The documentation should be updated to instruct the user on rescue mode. It
should be made readily available if not directly distributed.
I have changed this bug to the install-guide from the installer so that the
documentation will get updated in the next release.
Actually, the documentation has been changed to reflect the missing rescue.img
The Installation Guide (p52 in the footnotes) has it correctly - or so I've been
told it was correct.
Using the CD-ROM to boot, type linux rescue at the boot: prompt.
Using the network boot disk, type linux rescue at the boot:
prompt. You will then be prompted to pull the rescue image from the
Using the boot disk included with the Red Hat Linux boxed set,
type linux rescue at the boot: prompt. You can then load the
rescue images from the CD-ROM or hard drive.
The Reference Guide had it incorrectly and that documentation has been
corrected. www.redhat.com/apps/support - you'll find a link for documentation
errata and the rescue disk info has been corrected there.
This is the direct link to the corrected documentation.
*** Bug 7496 has been marked as a duplicate of this bug. ***
*** Bug 7909 has been marked as a duplicate of this bug. ****** Bug 9130 has been marked as a duplicate of this bug. ***
*** Bug 7069 has been marked as a duplicate of this bug. ***