Subtitles of the Movie

Sometimes even the GRUB boot loader doesn't work. It might not even appear when you boot your system, but there's no need to panic. Red Hat Enterprise Linux provides a rescue environment. It's available from the first installation CD. All you have to do when you see the boot prompt is you don't have to reinstall Linux, just type in Linux rescue and you're taken to a rescue boat. Let's see how that works. I have put in my first installation CD. I'm booting from the CD and I see the first installation screen. I press F5 for a little bit more information and, voila, I see a rescue mode. Let's see how that works. Linux rescue and it looks like it's starting the installation process. I don't want to do that, but in a moment we'll see everything's okay. The first steps associated with rescue mode are the same as the installation process. I get to select a language and a keyboard, but in a moment we'll see that it's actually a rescue mode. It loads necessary drivers and now I can select a language and look at that top line. It says welcome to Red Hat Enterprise Linux client rescue mode. I select a keyboard, select okay. I can set up networking if I want to and that can be useful if you have installation files on a remote computer, but for the [00:02:15 ] purpose of this video, let's skip that step. And there are three options here in the rescue screen. If I select continue it looks for my Red Hat Enterprise Linux files and mounts them in read write mode, assuming they're read write in the applicable etc slash fstab configuration file. If I select read only, it mounts those file systems in read only mode but sometimes the problem is that Linux has problems mounting file systems, so you can skip the mount process. If you select skip, Linux rescue mode doesn't mount anything. You can then find your file systems, run commands like fsck on them, and more. We'll select continue and it'll attempt to mount the file systems from my Red Hat Enterprise Linux 5 installation in the mount slash sysimage directory. It takes a moment to search my hard drive and success, it says my system has been mounted under the mount slash sysimage directory. Pay attention to that command. I can make my system the root environment by running that command. I get a shell prompt and look what's mounted. The dev slash volgroup00 slash logvol00 is the logical volume for my top level root file system. It's mounted on the mount slash sysimage directory. Other partitions, including dev slash sda1, are mounted on mount slash sysimage slash boot. That looks promising. Now let's try that troot command. Troot mount slash sysimage. Now what's mounted? A ha! The logical volume is mounted on my top level root directory, the partition is mounted on my boot directory, and now I'm all set up to fix whatever's wrong with my system. Thank you and on to the next video.