LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 09-09-2005, 08:53 AM   #1
Dankles
Member
 
Registered: May 2004
Location: /dev/null
Distribution: Slackware
Posts: 245

Rep: Reputation: 31
kernel panic - not syncing : VFS: unable to mount root FS on unknown-block


I'm geting this error message at startup:
"kernel panic - not syncing : VFS: unable to mount root FS on unknown-block"
I just upgraded from kernel 2.4 to 2.6, then this happend.
any suggestions?
 
Old 09-09-2005, 09:11 AM   #2
oxleyk
Member
 
Registered: Nov 2003
Distribution: Ubuntu
Posts: 309

Rep: Reputation: 30
Same thing happened to me when I didn't include reiser support in the kernel. You can either include the filesystem support in your kernel or create an initrd to load the module at startup.

Do a search on the error message to find other suggestions.

Kent
 
Old 09-09-2005, 09:11 AM   #3
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,373

Rep: Reputation: 164Reputation: 164
Check your config and make sure that you built-in the proper filesystem support. Do not compile this as a module.
 
Old 09-09-2005, 09:30 AM   #4
Dankles
Member
 
Registered: May 2004
Location: /dev/null
Distribution: Slackware
Posts: 245

Original Poster
Rep: Reputation: 31
I ran this command for FS support
mkinitrd -c -k 2.6.10 -m reiserfs

Heres my lilo entry
################
image = /boot/vmlinuz-generic-2.6.10
initrd = /boot/initrd.gz
root = /dev/hda3
label = Linux-2.6
read-only
 
Old 09-09-2005, 09:35 AM   #5
Dankles
Member
 
Registered: May 2004
Location: /dev/null
Distribution: Slackware
Posts: 245

Original Poster
Rep: Reputation: 31
I'm and idiot!! The problem was in lilo, i asumed that my loader was pointing to hda3; when in reality it was pointing to hda1
Thanks for your timely help!
 
Old 09-13-2005, 08:46 AM   #6
gbox
LQ Newbie
 
Registered: Sep 2005
Posts: 2

Rep: Reputation: 0
hi u wrote following:

I ran this command for FS support
mkinitrd -c -k 2.6.10 -m reiserfs

Heres my lilo entry
################
image = /boot/vmlinuz-generic-2.6.10
initrd = /boot/initrd.gz
root = /dev/hda3
label = Linux-2.6
read-only


Im expiring the same problem, but i dont know what to do. In my how to isnt a stage where i should assign the FS to the new kernel.

My question is : where to input this command and at which stage? It will be very helpful for me

10x
 
Old 09-13-2005, 08:53 AM   #7
Dankles
Member
 
Registered: May 2004
Location: /dev/null
Distribution: Slackware
Posts: 245

Original Poster
Rep: Reputation: 31
what does your lilo look like? This happened because I pointed my lilo to hda1 instead of hda3.
 
Old 09-13-2005, 09:33 AM   #8
gbox
LQ Newbie
 
Registered: Sep 2005
Posts: 2

Rep: Reputation: 0
hi

the problem is i didnt wrote any commant to point lilo for the new kernel. Here are all steps i have done to install the new kernel :

1. $ tar -zxf linux-2.6.11.4.tar.gz
2. $ cd linux-2.6.11.4
3. $ make xconfig
4. $ make
5. # cp .config /boot/config-2.6.11.4
# cp System.map /boot/System.map-2.6.11.4
# cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.11.4
# ln -sf config-2.6.11.4 /boot/config
# ln -sf System.map-2.6.11.4 /boot/System.map
# ln -sf vmlinuz-2.6.11.4 /boot/vmlinuz
6. # make modules_install
7. # /sbin/lilo

In my opinion there is no additional info on step 7, should be any, or not?

thats all i have done, and i didnt see anything about the FS. so what isnt present in my How to and what else should i do?

10x
 
Old 09-13-2005, 09:53 AM   #9
Dankles
Member
 
Registered: May 2004
Location: /dev/null
Distribution: Slackware
Posts: 245

Original Poster
Rep: Reputation: 31
Can you still get into you linux system?
you need to edit "/etc/lilo.conf"
add this:
--------------------------------

image = /boot/vmlinuz-2.6.11.4
root = /dev/hd*
label = **any thing**
read-only

---------------------------------

i think that will work, I'm not a linux expert though. If you cant get it to work this way, I suggest starting a new thread in the forms.
 
Old 10-19-2005, 05:24 AM   #10
cb951303
Member
 
Registered: Jan 2004
Distribution: Slackware 11 + Dropline Gnome 2.16
Posts: 194

Rep: Reputation: 30
I have the same problem(I upgraded to 2.6.13)
but I'm pretty sure that I included my ide and filesystem statically(not modules) (I already compiled my own kernel before), and I'm also sure that there is nothing wrong about my lilo.conf because "make install" does that automatically(I also checked my self)

so what could be another reasons for that error?
 
Old 10-19-2005, 08:09 AM   #11
carboncopy
Senior Member
 
Registered: Jan 2003
Location: Malaysia
Distribution: Fedora Core, Slackware, Mac OS X, Debian, OpenSUSE
Posts: 1,210
Blog Entries: 4

Rep: Reputation: 45
Hi guys,
I went through the same problem when I upgraded kernel from 2.4 to 2.6 on Dell Inspiron 6000 laptop. It is documented here. And specifically, the fix post

What IDE controller do you have? Or specifically what is the chipset?

There is a likely hood that on 2.6 kernel, your IDE harddisk is recognise as /dev/sd**, just as it happens to mine.

The solution is to change the lilo.conf entry for your new kernel image root = /dev/sd**

Remember to change your /etc/fstab entries as well. If you do not change that, you will be able to boot but the kernel will complain it can't mount the root partition later.

Last edited by carboncopy; 10-19-2005 at 08:11 AM.
 
Old 10-19-2005, 08:32 AM   #12
gbonvehi
Senior Member
 
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145

Rep: Reputation: 51
Quote:
Originally posted by gbox
hi

the problem is i didnt wrote any commant to point lilo for the new kernel. Here are all steps i have done to install the new kernel :

1. $ tar -zxf linux-2.6.11.4.tar.gz
2. $ cd linux-2.6.11.4
3. $ make xconfig
4. $ make
5. # cp .config /boot/config-2.6.11.4
# cp System.map /boot/System.map-2.6.11.4
# cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.11.4
# ln -sf config-2.6.11.4 /boot/config
# ln -sf System.map-2.6.11.4 /boot/System.map
# ln -sf vmlinuz-2.6.11.4 /boot/vmlinuz
6. # make modules_install
7. # /sbin/lilo

In my opinion there is no additional info on step 7, should be any, or not?

thats all i have done, and i didnt see anything about the FS. so what isnt present in my How to and what else should i do?

10x
You forgot make modules, also check that you've support for your harddisk type and filesystem in your kernel, you should be fine with those.
 
Old 11-24-2005, 09:34 PM   #13
simber
LQ Newbie
 
Registered: Nov 2005
Location: Ankara
Distribution: SuSE 9.2
Posts: 24

Rep: Reputation: 15
Hi everyone,

I got the same problem here, my SuSE 9.2 can't boot. I understand that I must reach config file but I can not even reach my HD with external tools, such as this famous Ultimate Boot CD which includes a live Linux too. The hda1 (swap) and hda2 (reiserfs) are seen in the table of Qtparted (a GUI tool for handling partitions) but hell, no way to change anyting on them, formatting doesn't work either. The booting stops with the error message: hda: read-initr: uncorrectable error: LBA 2020108 This sector is in the hda2 partition that includes SuSE 9.2. Any workaround for that?

Last edited by simber; 11-24-2005 at 09:38 PM.
 
Old 01-04-2011, 08:36 AM   #14
starz
LQ Newbie
 
Registered: Jan 2011
Posts: 4

Rep: Reputation: 0
Kernel Panic- not syncing

Hello Experts,
I am having same problem after I upgraded my Ubuntu.
Ubuntu is installed as application on my XP.
Normal Ubuntu gives me error "[ 0.785649] kernel panic - not syncing : VFS: unable to mount root FS on unknown-block(8,2)"
Safe/Recovering boot option gives me details traceback..
Pid :1 comm: swapper not tainted 2.6.32-27-generic#
call Trace:
[<c058b313>]?printK+0x1d/0x22
....
Please need a help..
 
Old 01-04-2011, 10:01 AM   #15
Dankles
Member
 
Registered: May 2004
Location: /dev/null
Distribution: Slackware
Posts: 245

Original Poster
Rep: Reputation: 31
Wow... this is a blast from the past!

The error is usually indicative of miss configured grub or something like that. What do you mean that ubuntu is installed as an application?
 
  


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
kernel panic: VFS unable to mount root fs on unknown-block(3,1) koolgentoo Linux From Scratch 5 08-15-2008 07:06 AM
Kernel Panic: VFS: Unable to mount root fs on unknown-block Igor007 Programming 3 08-14-2005 07:54 PM
Kernel Panic: VFS: Unable to mount root fs on unknown-block(3,65) kpaske Linux - Newbie 1 08-07-2004 12:03 AM
Kernel Panic:VFS:Unable to mount root fs on Unknown block dinesha Linux - Software 2 02-27-2004 12:37 PM
kernel panic VFS: unable to mount root fs on unknown-block (0,0) demmylls Linux - General 2 02-08-2004 10:18 AM


All times are GMT -5. The time now is 01:55 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