Chapter 5 Flashcards
What graphical application can be used to configure Red Hat Enterprise Linux services?
system-config-services
What key sequence can be used to scroll through the history of a virtual console?
SHIFT+PAGEUP
Upon booting, very shortly after selecting the appropriate stanza from the GRUB menu, your system displays the following message.
Booting ‘Red Hat Enterprise Linux (2.6.28-8.el5)’
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz-2.6.28-8.el5 ro root=LABEL=/
Error 15: File not found
Press any key to continue…
-
Which of the following is the most likely cause of the problem?
The bootloader has been configured with an incorrect root partition or path to the kernel.
Which of the following files will most likely have to be edited to solve the problem?
/boot/grub/grub.conf
Upon booting, you select an entry from from the GRUB menu, and see a series of kernel messages. The boot sequence ends abruptly at the following point, however.
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 146k freed
VFS: Mounted root (ext2 filesystem).
Journalled Block Device driver loaded
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
Freeing unused kernel memory: 132k freed
init-2.05b#
You are left at an interactive shell.
-
Which of the following best explains the problem?
For some reason, the kernel could not find or execute its normal first process.
Which file should be examined and or modified?
/sbin/init
Upon booting, you select an entry from from the GRUB menu, and see a series of kernel and init script messages. The boot sequence ends abruptly at the following point, however.
kjournald starting. Commit interval 5 seconds
Freeing unused kernel memory: 132k freed
INIT: version 2.84 booting
Setting default font (latarcyrheb-sun16): [ OK ]
Welcome to Red Hat Enterprise Linux Press 'I' to enter interactive startup. Mounting proc filesystem: [ OK ] Unmounting initrd: [ OK ] Configuring kernel parameters: [ OK ] Setting clock (localtime): Fri Nov 14 14:32:45 EST 2003 [ OK ] Loading default keymap (us): [ OK ] Setting hostname dhcp63-237.rdu.redhat.com: [ OK ] Initializing USB controller (usb-uhci): [ OK ] Mounting USB filesystem: [ OK ] Initializing USB HID interface: [ OK ] Initializing USB keyboard: [ OK ] Initializing USB mouse: [ OK ] Checking root filesystem e2fsck 1.32 (09-Nov-2002) Couldn't find ext2 superblock, trying backup blocks...
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
e2fsck: Bad magic number in super-block while trying to open /dev/hda7
- ** An error occurred during the file system check.
- ** Dropping you to a shell; the system will reboot
- ** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):
-
What is the most likely problem?
The /etc/fstab file has an incorrect entry referencing the root partition.
Which file would you most likely have to edit to solve this problem?
/etc/fstab
Upon booting, you select an entry from from the GRUB menu, and see a series of kernel and init script messages. The boot sequence is littered with messages such as the following interspersed with failed service script starts, and eventually the system hangs.
Unable to remove file /var/lib/rpm/__db.001: Read-only Filesystem
Unable to remove file /var/lib/rpm/__db.002: Read-only Filesystem
Unable to remove file /var/lib/rpm/__db.003: Read-only Filesystem
-
What is the most likely cause of the problem?
The /var partition was mounted read-only.
Which of the following files would most likely need to be edited to fix the problem?
/etc/fstab
