Академический Документы
Профессиональный Документы
Культура Документы
Overview
When a server fails to boot, a critical situation is at hand. The purpose of this document is to provide a quick reference guide to
narrow down the cause of a failed boot and get the server back up as quickly as possible. It is based on SUSE Linux
Enterprise Server 10 (SLES10).
Troubleshooting Procedure
1. The primary troubleshooting objective is to narrow down where in the boot process the failure occurred.
2. The boot process is summarized below. For more details, refer to the Troubleshooting Table below.
BIOS -> MBR/stage1 -> stage2 -> kernel/initrd -> init -> boot -> rc -> login
3. Look at the failed server's screen for the last on-screen landmark that matches the troubleshooting table's "On-Screen
Landmarks".
4. Once you determine how far in the boot process the failure occurred, look at the troubleshooting table's associated
files and troubleshooting/potential fixes.
5. The two most identifiable on-screen landmarks are:
1. The grub boot menu screen (Troubleshooting Table, Line 3)
2. Seeing the word "done" scrolling across the screen (Troubleshooting Table, Lines 8 and 11)
6. The purpose of boot installed system, run level 1 and chroot installed system is to get the server in an operational
maintenance state, so further problem resolution can be completed.
7. Boot Installed System (BIS) Procedure
1. If this procedure works, then the problem is most likely on lines 1-6 of the troubleshooting table.
2. Boot from CD1
3. Select "Installation"
4. Select your Language
5. Accept the License Agreement
6. Click "Other"
7. Select "Boot Installed System"
8. Click "OK"
8. Boot to Run Level 1
1. Run level 1 is very similar to chroot installed system (CIS), but the kernel does it for you. You also have
access to yast and the proc filesystem. So, run level 1 is preferred over CIS.
2. Append "init 1" to the boot options line of the default boot kernel (ie SUSE Linux Enterprise Server 10)
3. Type root's password
4. If you need network access, just use yast to configure it
yast lan > Next > Edit > Next > Next/Finish
9. chroot Installed System (CIS) Procedure
1. Used mostly in lines 7-14 of the troubleshooting table.
2. Boot from CD1
3. Select "Rescue System", Rescue login: root
4. Your first goal is to find and mount the root "/" partition, so we can see /etc/fstab
1. Run cat /proc/partitions to find the disk devices the OS sees
2. For each device, display the partition table
File system
ext2
linux-swap
Flags
boot, type=83
type=82
1/3
9/24/2014
3
5
6
7
535MB
535MB
1012MB
1596MB
2147MB
1012MB
1596MB
2147MB
1612MB
477MB
584MB
551MB
extended
logical
logical
logical
reiserfs
reiserfs
reiserfs
lba, type=0f
type=83
type=83
type=83
reiserfs
ext2
reiserfs
reiserfs
swap
proc
sysfs
debugfs
devpts
auto
acl,user_xattr
acl,user_xattr
acl,user_xattr
acl,user_xattr
defaults
defaults
noauto
noauto
mode=0620,gid=5
noauto,user,sync
1
1
1
1
0
0
0
0
0
0
1
2
2
2
0
0
0
0
0
0
chroot /mnt
1. If this command fails, then you need to confirm that /mnt/bin/bash and glibc on the installed system
are valid.
2. To return to the rescue system, type exit.
Troubleshooting Table
BIS = Boot Installed System Procedure
CIS = chroot Installed System Procedure
Boot Process
Associated File(s)
On-Screen Landmarks
Troubleshooting/Potential Fixes
BIOS
N/A
BIOS Messages
MBR
/boot/grub/stage1
GRUB
loading stage2...
BIS
grub-install /dev/<disk> or lilo -v
GRUB
/boot/grub/stage2
/boot/grub/menu.lst
BIS
grub-install /dev/<disk> or lilo -v
Check /boot/grub/menu.lst
kernel
/boot/vmlinuz
BIS
Reinstall kernel rpm
initrd
/boot/initrd
/etc/sysconfig/kernel
RAMDISK: <relevant
message>
BIS
mkdir -p /tmp/ramdisk; cd /tmp/ramdisk;
zcat /boot/initrd | cpio-ivd
mkinitrd
lilo -v
ramdisk:init
/init in /boot/initrd
/etc/sysconfig/kernel
Starting udevd
Creating devices
Loading <module_name>
BIS
mkinitrd creates the ramdisk:init file.
https://www.novell.com/coolsolutions/feature/19263.html
2/3
9/24/2014
sbin:init
sbin:init:boot
/sbin/init
/etc/inittab
/bin/bash
/etc/init.d/boot
/etc/init.d/boot.d/*
sbin:init:boot
/etc/init.d/boot.local
10 sbin:init
/etc/inittab
11 sbin:init:rc
/bin/bash
/etc/init.d/rc
/etc/init.d/rc?.d/*
12 sbin:init
/etc/inittab
N/A
13 sbin:init:mingetty
/etc/issue
/sbin/mingetty
14 sbin:init:X
If you don't know what to do next, and BIS or CIS work, you can always run
https://www.novell.com/coolsolutions/feature/19263.html
3/3