TUT 129 Troubleshooting SLES 10
- Oops
- Types of Issues
- System doesnt install
- Installation Workflow
- Syslinux or pxeboot loads the installation kernel initrd and starts the kernel
- The kernel mounts the initrd and starts linuxrc as the init process
- linuxrc sets up devices required to load the root system and loads it to a RAM disk
- The root system contains YaST, which will request additional information, prepare disk volumes and install packages
- linuxrc starts YaST and detaches the initrd with chroot_pivot
- After installation of the packages YasT starts the installed system with or without a reboot
- On the first start of the installed system yast gets called again and finishes lloading the system
- Installation Doesn’t work
- Check DVD, drive, or BIOS settings
- Bootload comes up, but cannont load kernel or initrd
- Check installation media
- Kernel starts bu hangs at splash screen
- Press F2 and check messages
- Still hangs at splass screen
- Reboot, start with textmode and safe mode options and check messages where it gets stuck
- linuxrcstarts, but hangs
- try safe mode boot options
- linuxrc starts, but falls back to manual setup
- Normal for mainframe. Go through manual setup
- Cannot find installation system. Check installation source.
- YaST2 starts, but eventuall crashes and falls back to linuxrc
- check if disks have correct partition label
- check if filesystems have been created
- Check if enough RAM
- Check installation source
- YaST2 still crashes
- Check /var/log/YaST2/y2log
- There is a shell on text console 2
- On zSeries there is an sshd process running to login via network during installation
- After Installation
- runlevel says unknown runlevel
- vnc/ssh/remote X11 installation
- YaST2 hasn’t run after installation
- vnc installation: start vncviewer
- X11 installation: start remote X11 server
- After Boot
- Kernel Boot Messages
- Linux kernel prints alot of status messages during startup
- While the amount might be confusing at firste, they are a valuable resource
- Some messages smell like error messges, but are in fact just harmless status notices or warnings
- the kernel sometimes finds flaws of the hardware design or BIOS and complains about them
- Kernel messages are logged by the klogd daemon, which feeds them to syslogd
- Previous kernel messages can be red with dmesg, whidch reads the /proc/kmsg ring buffer
- Boot Paramaters if the kernel starts but eventually locks up
- Failsave kernel paramaters
- ide=nodma – use PIO modes for ide disks – slow
- edd=off BIOS extended disk driver services off
- apm=off don’t use APM
- acpi=off dont use ACPI
- noapic use XT interrupt controller
- nosmp turn off smp support
- maxcups=0 max cpu usage is really 1
- Beware of the difference between ACPI and APIC
- ACPI is Advanced Configuration and Power Interface (provided by the bios)
- APIc is the Advanced Programmable Interrupt Controller, a part of the mainboard’s chipset
- To add to the confusion, the ACPI table contains the APIC configuration data
- ACPI=off turns off ACPI support
- system does install but doesn’t come up
- System locks up after a while
- System actually locks up or crashes
- Apps do not start
- Apps crash
- Expected better performance
- Everything works fine, but what does this message mean?
Ended up leaving the session due to irrelevant content to me… also very difficult to understand speaker.
powered by performancing firefox
Technorati Tags: SLES, Troubleshooting, YaST, YaST2