Storix Software SBAdmin Linux System Recovery Guide - Manual (Page 73)

An arrow (
==> ) will appear next to the device modules that are currently loaded on the system. If you highlight
and select a line for a module that is not currently loaded, a message will appear indicating that the module is
being loaded. If the module is loaded successfully and new devices (or adapters) are detected, a message will
appear showing you the names of the configured devices. If no new devices are detected, the module will be
unloaded automatically and a message to that affect will appear on the screen.
If you highlight a line containing an arrow and press enter, you will be informed that the module is currently
loaded and asked if you want to unload the module. Note that unloading a module may cause devices currently
configured to become unavailable (i.e. disk or tape drives), and some modules may not be unloaded if they are
currently in use (i.e. network adapters for active networks).
When you have finished your selections, press ESC or F3 to return to the System Recovery Utilities menu .
Start a Maintenance Shell
Select this option to start a maintenance shell where you may perform various operations for performing system
maintenance or recovery such as mounting and repairing disk filesystems, or reconfiguring the disk boot loader.
When entering the shell, no disk filesystems will be loaded, and only the command set available on the boot
media for system recovery are available. The user will need to perform the manual tasks needed to mount the
root (/) or other filesystems if access to the data stored on the disks is desired. The commands and options for
doing this vary much too widely to be discussed here, as some filesystems reside in LVM, others are made from
RAID devices, etc.
When you have finished the system maintenance tasks, you may reboot the system from the command line, or,
if you wish to return to the system installation process, you may type “exit” at the prompt to return to the menus.
Note: There is no job control in the maintenance shell. Therefore using CRTL-C to end a process will not work.
This is important to note if you are attempting to use the “ping” command to diagnose network issues. Any
command you run should exit by itself. For example, if you are using the “ping” command, add an argument to
limit the number of tries (normally the –c flag) so that the command will exit on its own.
Storix System Backup Administrator 73 Version 8.2 Linux System Recovery Guide