Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I had the Redhat 8.0 running on my system to begin with.
Then, I upgraded my system to a new mother board, new video card, etc. but I wanted to keep some of my hard disks.
I have one hard disk dedicated to Linux and another to Windows.
Unknowingly, I had the LILO on the Windows disk so I reinstalled it on my Linux disk so I could upgrade Windows also.
I did it by installing Redhat 8.0 on top of my Linux disk (already Redhat 8.0) but without reformatting and reparitioning it so I could preserve the existing files.
Now, I can start Linux but I get an error when kernel initializes.
I will only show last few lines of the screen (everything above it looked OK):
After that, the system is stopped (keyboard LEDs blink).
My guess is that for some reason the mount did not work and everything else is a result of this.
I do not understand what is the problem and I would appreciate any help.
I can run the Linux Rescue option and I can access the hard disk and the /sbin/init exists where it suppose to.
I believe that the only time the installer gave me a choice of ext3 vs. ext2 was during reparitioning option, but because I did not want to reparition, I selected no partitioning and no formatting and continued the installation. I know that my system is ext2.
I had Redhat 7.1 before, then 8.0 which worked before the hardware upgrade and all I am trying to do is to make it work in the new hardware environment without any file loss.
Is it possible that the kernel assumes ext3 even though it is ext2?
/etc/inittab looks OK to me, very similar to one in my linux book.
I can check the lilo.conf but I believe it is correct because the kernel initializes correctly and checks hardware and tries to start init. Also, it was generated by Redhat installer.
But I have some more information:
When I use the boot disk created by the Redhat installer, the kernel starts up from the floppy and then it jumps to the init on the hard disk and continues correctly and I am able to log in.
Looks like the problem occurs when kernel tries to give up control to init and in case of hard disk boot, it does not work and I do not know why.
All of the kernel messages look about the same between floppy and hard disk boot until it tries to mount devices and start init.
There must be some kind of setting somewhere that is not correct. Any ideas?
I found the problem but I still do not understand why it happened.
I looked at the floppy configuration file and noticed that it appended:
to the Linux kernel parameters.
Then, I tried to start Linux from the hard disk by entering
at the Linux boot prompt and it worked.
Then, I looked at lilo.conf and noticed that it contained:
which did not make sense to me.
I also found "LABEL=/" in my fstab file where I would expect "/dev/hda1" to be.
I replaced the references to "LABEL=/" with "/dev/hda1" in lilo.conf and fstab and now it works correctly.
I believe that something during Redhat installation caused this to happen because I did not do it myself.
Possible installation script bug or oversight?
If anybody knows the reason for this, speak up, otherwise I will not bother with this anymore.
The LABEL values are the names of the partitions (specified when you create the partition). Since I dual boot my linux boxes with multiple linux distros I tend not to use them since almost all will want to access a partition with lables of "/" and "/var". Perhaps when you reinstalled, the partition names were deleted or something.
When I upgraded my hardware, I moved my hard disks around and my Linux drive which was hdc1 became hda1. I also added a lot of new hardware and that is why I decided to resinstall Redhat 8 onto the disk.
When I ran the install program, I did not go through paritioning and formatting but I reinstalled LILO to fix the hard disk locations.
The install program asked me about the root location and I specified /dev/hda1. The parition names (whatever this means) I did not see nor changed.
Somehow the install program got really confused by all of this.