LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 10-28-2005, 10:53 PM   #1
hitman_et
Member
 
Registered: Oct 2004
Location: Queensland, Australia
Distribution: Fedora Core 4
Posts: 67

Rep: Reputation: 15
Kernal Panic: VFS: Unable to mount root fs on 00:00


Whenever i try and boot i get these errors
Code:
 RAMDISK: Compressed image found at block 0
invalid compressed format (err=2)<6>Freeing initrd memory: 143k freed
VFS: Cannot open root device "LABEL=/" or 00:00
Please append a correct "root=" boot option
Kernal Panic: VFS: Unable to mount root fs on 00:00
Kernal Ver.=2.4.20-31.9
Kernal boot options(i think??, the options listed when i click 'e')
Code:
root (hd0,1)
kernel /boot/vmlinux-2.4.20-31.9 ro root=LABEL=/ hdc=ide-scsi
initrd /boot/initrd-2.4.20-31.9.img
i tried using the original kernel version that came with redhat 9 but it gave same errors.

I havent updated or changed the kernel for 6 months. and i dont think i changed anything the last time i used the computer.
I suspect it might have soemthing to do with the harddrive.

I tried a knoppix cd but it gave me much the same errors, the kernel panic and invalid compressed format. I also got an error about SMP

Thanks in Advance
 
Old 10-29-2005, 12:43 AM   #2
DaneM
Member
 
Registered: Oct 2003
Location: Chico, CA, USA
Distribution: Linux Mint
Posts: 881

Rep: Reputation: 130Reputation: 130
I'm not very familiar with RedHat, but I think that bit about "root=LABEL=/" is bad. Try replacing it with something like:

root=/dev/hda2

or

root=(hd0,1)

I hope that helps.

--Dane
 
Old 10-29-2005, 01:24 AM   #3
hitman_et
Member
 
Registered: Oct 2004
Location: Queensland, Australia
Distribution: Fedora Core 4
Posts: 67

Original Poster
Rep: Reputation: 15
root=/dev/hda2 didn't work so i tried /dev/hda1. It gets a line further and says "Warning: unable to open an initial console
Kernel panic: No init found.Try passing init= option to kernel"

i tried init=/sbin/init, but that gave same error.
 
Old 10-29-2005, 02:22 AM   #4
DaneM
Member
 
Registered: Oct 2003
Location: Chico, CA, USA
Distribution: Linux Mint
Posts: 881

Rep: Reputation: 130Reputation: 130
Try putting in the value for the runlevel you want to start at (3, 4, 5, etc.). In mine (on Gentoo) it says init=linuxrc. Dunno what that means; it might just be a gentoo thing. Also try putting in init=/bin/sh. That was recommended on a website I saw. (http://www.linuxforums.org/forum/topic-19763.html)

I'm kind-of shooting in the dark here, so if anybody else has an idea, please post!

--Dane

Last edited by DaneM; 10-29-2005 at 02:25 AM.
 
Old 10-29-2005, 06:56 PM   #5
hitman_et
Member
 
Registered: Oct 2004
Location: Queensland, Australia
Distribution: Fedora Core 4
Posts: 67

Original Poster
Rep: Reputation: 15
No luck
 
Old 10-29-2005, 07:47 PM   #6
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 113Reputation: 113
I believe your root partition should be /dev/hda2 as Grub counts from 0.

Therefore root=/dev/hda2 should be OK. What you need to do also is to amend the LABEL in the /etc/fstab file first statement so that /dev/hda2 corresponds to /.

Red Hat series distros do have this mismatched from time to time.
 
Old 10-29-2005, 09:00 PM   #7
hitman_et
Member
 
Registered: Oct 2004
Location: Queensland, Australia
Distribution: Fedora Core 4
Posts: 67

Original Poster
Rep: Reputation: 15
Quote:
What you need to do also is to amend the LABEL in the /etc/fstab file first statement so that /dev/hda2 corresponds to /.
So what do i have to change/add to fstab. This is what it is currently. (trimmed)
Code:
LABEL=/                  /             ext3   defaults              1 1
proc ....

/dev/hda3               swap      swap defaults               00

/dev/sda1...
/dev/scd0...

Last edited by hitman_et; 10-29-2005 at 09:03 PM.
 
Old 10-30-2005, 03:32 AM   #8
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 113Reputation: 113
since your call your root consistently as /dev/hda2. In the first line in fstab just substitute

LABEL=/ with /dev/hda2 so that RH knows it corresponds to the / directory, in a similar manner as the later statement which raw device corresponds to swap

Last edited by saikee; 10-30-2005 at 03:34 AM.
 
Old 10-30-2005, 06:54 PM   #9
hitman_et
Member
 
Registered: Oct 2004
Location: Queensland, Australia
Distribution: Fedora Core 4
Posts: 67

Original Poster
Rep: Reputation: 15
Could this actually be a problem with my ram as i tried to boot with different ram and it booted fine, but when i plugged the network cable in the computer froze and wont boot again. In fact when i switched the old ram to different slots the computer would either freeze at "Checking nvram" or the screen would not turn on. With the new ram in, the monitor will not turn on.

Could there be a problem with my ram slots? Is there anyway to tell?

Thanks
 
Old 10-30-2005, 07:05 PM   #10
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 113Reputation: 113
You have to isolate one problem from another. Mixing the hardware fault with the software problem can be a major headache.

You should go back to the original ram arrangement (& network arrangement) and start from there. Get the system working first then try out the ram and network.

You should be aware of each Mobo can work with only a certain brands of rams (approved by the Mobo vendor). Also a Mobo manufacturer frequently dictates the arrangement of how to fill up the slots.
 
Old 10-30-2005, 07:09 PM   #11
hitman_et
Member
 
Registered: Oct 2004
Location: Queensland, Australia
Distribution: Fedora Core 4
Posts: 67

Original Poster
Rep: Reputation: 15
Yeah that is a bit of a problem, i cannot get the original ram to work again, i have tried putting it back in the orginal slots, but no luck. I even tried removing the network card and sound card.

I have cheapo ram so it doesnt really matter which slots they are in and I have also tried using only one stick at a time.

Thanks
 
Old 10-30-2005, 07:11 PM   #12
saikee
Senior Member
 
Registered: Sep 2005
Location: Newcastle upon Tyne UK
Distribution: Any free distro.
Posts: 3,398
Blog Entries: 1

Rep: Reputation: 113Reputation: 113
The hardware can be tested by a Live CD from another LInux
 
  


Reply



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 On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernal panic: VFS: Unable to mount root fs nodnarb Linux - Newbie 1 12-25-2004 10:04 PM
Kernal Panic: VFS: unable to mount root fs on hdb1 icebreaker Slackware 3 05-21-2004 10:25 PM
Kermel panic: VFS: Unable to mount root fs on 00:00 teclipse Linux - General 1 10-04-2003 11:56 AM
Kernel panic: VFS: Unable to mount root fs on 08:01 welsh2000836 Debian 3 08-31-2003 02:34 PM
kernel panic:vfs:unable to mount root fs on 03:06 brianlan Linux - Software 4 06-28-2002 10:16 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 01:38 PM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration