LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This 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.

Notices

Reply
 
Search this Thread
Old 04-09-2003, 01:40 PM   #1
Kajtek
LQ Newbie
 
Registered: Apr 2003
Posts: 6

Rep: Reputation: 0
Kernel panic after Redhat 8.0 upgrade


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):

....
Mounting /proc filesystem
Creating block devices
Creating root device
Creating root filesystem
Mount: error 6 mounting ext2
pivotroot: pivot_root (/sysroot, /sysroot/initrd) failed: 2
Freeing unused kernel memory: 212k freed
Kernel panic: No init found. Try passing init= option to kernel.


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.

Thank you,
Martin
 
Old 04-09-2003, 02:21 PM   #2
david_ross
Moderator
 
Registered: Mar 2003
Location: Scotland
Distribution: Slackware, RedHat, Debian
Posts: 12,047

Rep: Reputation: 64
By default redhat 8 uses ext3 not ext2? Did you specifically use ext2 during the install?
 
Old 04-09-2003, 03:12 PM   #3
Kajtek
LQ Newbie
 
Registered: Apr 2003
Posts: 6

Original Poster
Rep: Reputation: 0
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?
Martin
 
Old 04-09-2003, 03:18 PM   #4
david_ross
Moderator
 
Registered: Mar 2003
Location: Scotland
Distribution: Slackware, RedHat, Debian
Posts: 12,047

Rep: Reputation: 64
I think it is trying to mount ext2. What does your /etc/inittab file say?
 
Old 04-09-2003, 05:00 PM   #5
jailbait
Guru
 
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Debian Wheezy, Debian Jessie
Posts: 7,509

Rep: Reputation: 176Reputation: 176
maybe lilo.conf

You may need a parameter in your lilo.conf similar to:
initrd = /boot/vmlinuz
 
Old 04-09-2003, 05:29 PM   #6
Kajtek
LQ Newbie
 
Registered: Apr 2003
Posts: 6

Original Poster
Rep: Reputation: 0
/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?
Martin
 
Old 04-11-2003, 10:49 AM   #7
Kajtek
LQ Newbie
 
Registered: Apr 2003
Posts: 6

Original Poster
Rep: Reputation: 0
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:
root=/dev/hda1
to the Linux kernel parameters.
Then, I tried to start Linux from the hard disk by entering
linux root=/dev/hda1
at the Linux boot prompt and it worked.
Then, I looked at lilo.conf and noticed that it contained:
root="LABEL=/"
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.
Martin
 
Old 04-11-2003, 02:40 PM   #8
david_ross
Moderator
 
Registered: Mar 2003
Location: Scotland
Distribution: Slackware, RedHat, Debian
Posts: 12,047

Rep: Reputation: 64
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.
 
Old 04-11-2003, 05:10 PM   #9
Kajtek
LQ Newbie
 
Registered: Apr 2003
Posts: 6

Original Poster
Rep: Reputation: 0
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.
Martin
 
Old 04-11-2003, 05:18 PM   #10
david_ross
Moderator
 
Registered: Mar 2003
Location: Scotland
Distribution: Slackware, RedHat, Debian
Posts: 12,047

Rep: Reputation: 64
All's well that ends well

Trust me - LABEL values cause me nothing but trouble.
 
Old 04-11-2003, 05:21 PM   #11
Kajtek
LQ Newbie
 
Registered: Apr 2003
Posts: 6

Original Poster
Rep: Reputation: 0
Now I know.
This is the first time I have ever seen them used and I agree with you.
Martin
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Upgrade FC3 to 2.6.14 results in kernel panic mrs kensington Fedora 2 11-14-2005 01:18 PM
Kernel panic after motherboard upgrade TarouSatomi Linux - Hardware 1 11-13-2005 03:24 PM
Kernel Panic after upgrade from RHES3 to RHES4 dawuad Linux - Enterprise 1 11-11-2005 04:19 AM
Kernel Panic 2.6.7, 4TH Release via apt-get upgrade Outabux Debian 1 08-12-2004 12:05 AM
framebuffer causes kernel panic after RAM upgrade lezek Linux - Hardware 9 04-14-2003 04:23 PM


All times are GMT -5. The time now is 05:36 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration