Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Let The Music Play: Join EFF Today

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents
Up to --> Solving Problems

· Solving Problems Yourself
· Preparing Yourself
· Checking the Sanity of Your System
· Problem Solving
· Crash Recovery
· Hardware Diagnostic Tools
· Netiquette

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Recommend Us
Surveys

Features
HOWTOs
News
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 198 guest(s) and 1 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  
Linux Tutorial - Solving Problems - Solving Problems Yourself - Crash Recovery
  Problem Solving ---- Hardware Diagnostic Tools  


Crash Recovery

If your system crashes, the most important thing is to prevent further damage. Hopefully, the messages that you see on your screen will give you some indication of what the problem is so that you can correct it. (For example, timeout errors on your hard disk might mean it's time to buy a new hard disk.)

Emergency Floppies

It may happen that the system crash you just experienced no longer allows you to boot your system. What then? The easiest solution (at least the easiest in terms of figuring out what to do) is reinstalling. If you have a recent backup and your tape drive is fairly fast, this is a valid alternative, provided there is no hardware problem causing the crash.

In an article I once wrote, I compared a system crash to an earthquake. The people who did well after the 1989 earthquake in Santa Cruz, Ca were those who were most prepared. The people who do well after a system crash are also those who are best prepared. As with an earthquake, the first few minutes after a system crash are crucial. The steps you take can make the difference between a quick, easy recovery and a forced re-install.

In previous sections, I talked about the different kinds of problems that can happen on your system, so there is no need to go over them again here. Instead, I will concentrate on the steps to take after you reboot your system and find that something is wrong. It's possible that when you reboot all is well and it will be another six months before that exact same set of circumstances occurs. On the other hand, your screen may be full of messages as it tries to bring itself up again.

Because of the urgent nature of system crashes and the potential loss of income, I decided that this was one troubleshooting topic through which I would hold your hand. There is a set of common problems that occur after a system crashes that need to be addressed. Although the cause of the crash can be a wide range of different events, the result of the crash is small by comparison. With this and the importance of getting your system running again in mind, I am going to forget what I said about giving you cookbook answers to specific questions for this one instance.

Lets first talk about those cases in which you can no longer boot at all. Think back to our discussion of starting and stopping the system and consider the steps the system goes through when it boot. I talked about them in detail before, so I will only review them here as necessary to describe the problems.

As I mentioned, when you turn on a computer, the first thing is the Power-On Self-Test, or POST. If something is amiss during the POST, you will usually hear a series of beeps. Hopefully, there will be some indication on your monitor of what the problem is. It can be anything from incorrect entries in your CMOS to bad RAM. If not, maybe the hardware documentation mentions something about what the beeps mean.

When finished with the POST, the computer executes code that looks for a device from which it can boot. On a Linux system, this boot device will more than likely be the hard disk. However, it could also be a floppy or even a CD-ROM. The built-in code finds the active partition on the hard disk and begins to execute the code at the beginning of the disk. What happens if the computer cannot find a drive from which to boot depends on your hardware. Often a message will indicate that there is no bootable floppy in drive A. It is also possible that the system will simply hang.

If your hard disk is installed and it should contain valid data, your master boot block is potentially corrupt. If you created the boot/root floppy set as I told you to do, you can use fdisk from it to recreate the partition table using the values from your notebook. Load the system from your boot/root floppy set and run fdisk.

This is done from the hard disk. With the floppy in the drive, you boot your system. When you get to the Boot: prompt, simply press Enter. After loading the kernel, it prompts you to insert the root file system floppy. Do that and press Enter. A short time later, you are brought to a # prompt from which you can begin to issue commands.

When you run fdisk, you will probably see an empty table. Because you made a copy of your partition table in your notebook as I told you to do, simply fill in the values exactly as they were before. Be sure that you make the partition active as it was previously. Otherwise, you won't be able to boot, or you could still boot but you will corrupt your file system. When you exit fdisk, it will write out a copy of the master boot block to the beginning of the disk. When you reboot, things will be back to normal.

(I've talked to at least one customer who literally laughed at me when I told him to do this. He insisted that it wouldn't work and that I didn't know what I was talking about. Fortunately for me, each time I suggested it, it did work. However, I have worked on many machines where it didn't work. With a success rate of more than 90 percent, it's obviously worth a try.)

Table - Files Used in Problem Solving

Command Description
/bin/pstatReports system information
/bin/whoLists who is on the system
/bin/whodoDetermines what process each user is running
/etc/badblockChecks for bad spots on your hard disk
/bin/rpmDisplays information about install packages (also used to install and remove software)
/etc/dfCalculates available disk space on all mounted file
/etc/fdisk Creates and administers disk partitions
/etc/fsck Checks and cleans file systems
/etc/fuser Indicates which users are using particular files and file systems
/etc/ifconfig Configures network interface parameters
/etc/ps Reports information on all processes
/usr/adm/hwconfig probe for hardware
/var/log/wtmpLogin records
/usr/bin/cpioCreates archives of files
/usr/bin/lastIndicates last logins of users and teletypes
/usr/bin/lpstatPrints information about status of print service
/usr/bin/netstatAdministers network interfaces
/usr/bin/sarReports on system activity
/usr/bin/tarCreates archives of files
/usr/bin/wReports who is on the system and what they are doing

 Previous Page
Problem Solving
  Back to Top
Table of Contents
Next Page 
Hardware Diagnostic Tools


MoreInfo

Test Your Knowledge

User Comments:


You can only add comments if you are logged in.

Copyright 2002-2009 by James Mohr. Licensed under modified GNU Free Documentation License (Portions of this material originally published by Prentice Hall, Pearson Education, Inc). See here for details. All rights reserved.
  




Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
You can get all the latest Site and Linux news by checking out our news page.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.40 Seconds