Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Mercy Corps

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents
Up to --> Installing and Upgrading

· Getting Your Own Copy
· Preparing for the Installation
· Installation Checklist
· Hardware Requirements
· Partitioning
· Swap Space
· Installation Problems
· Preparing for the Worst

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, 244 guest(s) and 1 member(s) that are online.

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

  
Linux Tutorial - Installing and Upgrading - Preparing for the Installation - Installation Problems
  Swap Space ---- Preparing for the Worst  


Installation Problems

Some possible problems could occur during the installation, one of which is that you have no free space. Many Linux distributions will allow you to install it on an existing DOS partition, so you need to be careful with this one. Fortunately, the system will tell what kind of file system it is.

If you are having trouble booting from floppies, there are a few reasons for this. The first, which I saw quite often while I was in tech support, happens on new machines when the CMOS setting for the floppy does not match what really is in the drive. Even today, CMOS are delivered in which the default A: floppy is 5.25" and 360K. If you have a 3.5" 1.44MB, it won't work right. The kernel might load, because it is just reading one sector after the other. However, the first time you have to seek to a particular sector, you're hosed.

Another common problem is simply that it is defective media. If you can install directly from the CD-ROM, this problem is unlikely to happen. If your CD-ROM drive needs a caddy, I have seen sticky slots that don't open all the way. It might also be that the CD-ROM is just dirty. Wipe it off with a clean dry, non-static cloth. If you have to create a boot floppy set, it's best to have new floppies. The cost of a new box is worth the piece of mind.

If the system hangs during boot process, pay close attention to any messages that come up, particularly the last few. These messages might indicate what the problems are. Although it didn't cause a hang, I had an Ethernet card and multi-port board that were both software configurable. Both configured to IRQ 10. Because the multi-port board was initialized first, my Ethernet card was inaccessible. Also check the Hardware HOWTO to make sure that your hardware is supported.

I have heard of out-of-memory errors. I have never experienced them myself because I have always installed my system with 32MB. The reason for this error is that you have very little RAM and a RAM disk is created during the install for the root file system. If the amount of RAM you have minus the ramdisk doesn't leave enough for Linux, you're in trouble. If you don't have enough RAM, get more. RAM is not prohibitively expensive, and you cant run a productive system without it anyway.

If you run into hardware problems, strip the system to just the devices you need for the install. Remove the parallel/serial ports, sound cards, network cards, mouse cards, and anything else you don't need for the installation. If the problem still continues, maybe one of the other cards is loose (like the SCSI host adapter). Remove and reseat all the cards. Check for conflicts of base address, IRQ, DMA, and, obviously, check that your hardware is supported.

SCSI devices are good things to have, but they can also be a major headache. I must admit that at times I almost have a too-relaxed attitude when installing. (Hey, I know what I am doing, right?) I often take for granted that the hardware is configured in a particular way, especially when other hardware of the same type is configured that way. This leads to problems!

I have seen systems in which a SCSI device is detected at all IDs, though no devices are there and no manufacturers ID is recognized. This happens when there is a device and HA at the same SCSI ID. The host adapter must be at ID 7. Every other device must be at a different, unique ID.

Maybe Linux detects errors on the disk, but the disk is known to be error free, which is often caused by either bad cables or incorrect termination. If your SCSI devices report timeouts, there may be a conflict with base address, DMA, or IRQ of the host adapter. I have also experienced timeouts when more than two devices on the bus are terminated. Remember that only the two devices at the physical end of the SCSI bus should be (must be) terminated. the SCSI devices report timeouts, this may also be due to bad connections or termination problems. However, it might also be due to conflicts with the I/O address or IRQ or DMA channels.

If you have obtained a version from the Internet, you can get read errors or "file not found" messages. I specifically mentioned the Internet because I have never seen it with commercial versions. This might be an indication of bad media (so instead, use new floppies) or that something went wrong with the transfer.

If you used ftp to copy the files from DOS/Windows machine, the transfer mode is normally ASCII by default. These files must be transferred in binary mode or they could result in messages like "tar: read error" or "gzip: not in gzip format."

After installing, you may have some problems booting. You may see something like "non-system disk in drive," "disk not bootable," "NO OS," etc., probably because your master boot block is corrupt. This can occur when installing onto machines with multiple operating systems. Some OSs have to be installed on the active partition. I have experienced this once, when I installed a second OS on a system only to find that the second simply overwrote the first.

The fdisk program on all PC-based OSs can read the partition table. It may not see what kind of partition it is, but it will see that something is there. On the other hand, the Linux fdisk can read the partition table and recognize what kind of partitions they are.

Another cause of this kind of message is that LILO might not have been installed correctly. Therefore, you should boot from the boot/root floppy that you made for the installation. Once you get to the boot:, you can specify the root file system to be on the hard disk. Once there, check the /etc/lilo.conf file and install it again.

One of my favorite problems I saw both with Linux and other UNIX dialects. When you boot, another OS starts instead of Linux, or Linux is installed first and after installing the other OS, Linux is no longer accessible. In the first case, LILO may not have been installed. If it was installed, maybe it was not installed in the master boot record; but Linux is not active, so the other OS boots. Maybe you simply configured LILO so that OS will boot by default. Ctrl+Shift+Tab and often just Tab gives you the LILO menu. (See man-page for more details.)

Depending on the distribution, you may be able to choose what type of file system on which you want to install. If you will remember from the section on file systems, Linux supports several different types of file systems, most of which you can install on.

If you are fortunate to have a system that understands the RedHat Package Manager Format (rpm), adding additional software is fairly easy. See the rpm man-page for more details.

 Previous Page
Swap Space
  Back to Top
Table of Contents
Next Page 
Preparing for the Worst


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.
  
Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.


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 choose larger fonts by selecting a different themes.


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.13 Seconds