Boot problems are situations when your system does not boot properly (that is, does not boot to the expected runlevel and login screen).
If the hardware is functioning properly, it is possible that the boot loader has become corrupted and Linux cannot start on the machine. In this case, it is necessary to reinstall the boot loader.
To reinstall the boot loader, proceed as follows:
Insert the installation media into the drive.
Reboot the machine.
Selectfrom the boot menu.
Select a language.
Accept the license agreement.
In thescreen, select and set the installation mode to .
Once in the YaST System Repair module, selectthen select .
Restore the original settings and reinstall the boot loader.
Leave YaST System Repair and reboot the system.
Other reasons for the machine not booting may be BIOS-related:
Check your BIOS for references to your hard drive. GRUB might simply not be started if the hard drive itself cannot be found with the current BIOS settings.
Check whether your system's boot order includes the hard disk. If the hard disk option was not enabled, your system might install properly, but fail to boot when access to the hard disk is required.
If the machine comes up, but does not boot into the graphical login
manager, anticipate problems either with the choice of the default
runlevel or the configuration of the X Window System.
To check the runlevel configuration, log in as the
root user and check
whether the machine is configured to boot into runlevel 5 (graphical
desktop). A quick way to check this is to examine the contents of
/etc/inittab, as follows:
nld-machine:~ # grep "id:" /etc/inittab id:5:initdefault: nld-machine:~ #
The returned line indicates that the machine's default runlevel
initdefault) is set to
that it should boot to the graphical desktop. If the
runlevel is set to any other number, use the YaST Runlevel Editor
module to set it to
Do not edit the runlevel configuration manually. Otherwise SuSEconfig (run
by YaST) will overwrite these changes on its next run. If you need
to make manual changes here, disable future SuSEconfig changes
If the runlevel is set to
5, you might have
corruption problems with your desktop or X Windows software. Examine
the log files at
detailed messages from the X server as it attempted to start. If the
desktop fails during start, it might log error messages to
/var/log/messages. If these error messages hint at
a configuration problem in the X server, try to fix these issues. If
the graphical system still does not come up,
consider reinstalling the graphical desktop. For more information about X
configuration, refer to Chapter 14, The X Window System (↑Reference).
One quick test: the startx command should force the X Window System to start with the configured defaults if the user is currently logged in on the console. If that does not work, it should log errors to the console. For more information about the X Window system configuration, refer to Chapter 14, The X Window System (↑Reference).