LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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
 
LinkBack Search this Thread
Old 05-04-2006, 08:05 PM   #1
push
Member
 
Registered: Sep 2004
Location: Cincinnati
Distribution: Slackware 10.2
Posts: 32

Rep: Reputation: 15
Kernel Panic - Not Syncing VFS: unable to mount root file system


Alright I already know the problem is most likely when I made changes to the lilo.conf and wrote it to the MBR I didn't specify to use the reiser fs, but now I can't boot up Slackware. I have an auditor cd and put that in and tried to make the changes and then run lilo, but of course it runs the auditor lilo, so I tried running /mnt/hda2/sbin/lilo and it complains that the kernel differs or something. So the question now is how do I write the new lilo.conf to the MBR. This all started when I made changes to initrd.gz and lilo.conf to enable bootsplash. Any ideas? I have restored my backups of initrd.gz and lilo.conf. I am running the 2.6.15.3 linux kernel.
 
Old 05-04-2006, 08:39 PM   #2
ataraxia
Member
 
Registered: Apr 2006
Location: Pittsburgh
Distribution: Debian Sid AMD64
Posts: 296

Rep: Reputation: 30
Code:
chroot /mnt/hda2 /sbin/lilo
 
Old 05-05-2006, 12:51 AM   #3
Acron_0248
Member
 
Registered: Feb 2006
Location: Venezuela
Distribution: Gentoo
Posts: 449

Rep: Reputation: 33
Correct me if I'm wrong, but the Kernel Panic VFS message occurs when you have a kernel that has the filesystem support for the HD that has linux installed, compiled as a module when it should be compiled "into" the kernel, not as a module....



Regards
 
Old 05-05-2006, 07:36 AM   #4
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 10,888
Blog Entries: 1

Rep: Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307Reputation: 1307
Quote:
Originally Posted by Acron_0248
Correct me if I'm wrong, but the Kernel Panic VFS message occurs when you have a kernel that has the filesystem support for the HD that has linux installed, compiled as a module when it should be compiled "into" the kernel, not as a module....



Regards
Hi,

Yes! If you want to use a module for your FS then you must create a initrd. Then add the initrd to the stanza of the lilo.conf. And run lilo to update the lilo on the mbr.
 
Old 05-05-2006, 06:49 PM   #5
push
Member
 
Registered: Sep 2004
Location: Cincinnati
Distribution: Slackware 10.2
Posts: 32

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by ataraxia
Code:
chroot /mnt/hda2 /sbin/lilo
Thank you that worked
 
Old 05-05-2006, 06:51 PM   #6
push
Member
 
Registered: Sep 2004
Location: Cincinnati
Distribution: Slackware 10.2
Posts: 32

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by gwsandvik
Hi,

Yes! If you want to use a module for your FS then you must create a initrd. Then add the initrd to the stanza of the lilo.conf. And run lilo to update the lilo on the mbr.
Yeah that's what I have done, I chose a bad initrd and it caused the panic. Fixed the problem and ran lilo and it's working again
 
Old 08-28-2006, 06:07 AM   #7
gau_veldt
LQ Newbie
 
Registered: Aug 2006
Location: Prince George, BC, Canada
Distribution: Debian (Sarge+Linex)
Posts: 6

Rep: Reputation: 0
does udev need initrd?

Quote:
Originally Posted by push
Yeah that's what I have done, I chose a bad initrd and it caused the panic. Fixed the problem and ran lilo and it's working again
running 2.6.12 using udev and the FS for reiser2 (the type on /dev/hda2 which happens to be the drive on my root= parameter)

I get the same error VFS: Unable to...on unknown block(0,0)
under these circumstances

I think udev is the name to my pain and I have a hunch a /dev node needs to exist in an initrd for udev to work (to make hda2 visible) so the kernel can mount it

Or is there something I'm overlooking?
 
Old 08-28-2006, 07:06 AM   #8
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 1,748

Rep: Reputation: 159Reputation: 159
Quote:
Originally Posted by gau_veldt
running 2.6.12 using udev
Which version of udev? The latest versions of udev require a 2.6.15 kernel as a minimum.
 
Old 08-28-2006, 07:17 AM   #9
gau_veldt
LQ Newbie
 
Registered: Aug 2006
Location: Prince George, BC, Canada
Distribution: Debian (Sarge+Linex)
Posts: 6

Rep: Reputation: 0
Thumbs down

Quote:
Originally Posted by rkelsen
Which version of udev? The latest versions of udev require a 2.6.15 kernel as a minimum.
I had this kernel running (on a previous build) until I lost the initrd support in a new kernel rebuild. I have a udev that wanted 2.6.10+ won't know its version until this kernel I'm trying to get to work will go and I'm not using a LFS rescue disk to mount my system to fix whatever was wrong.

To make the long sad story short dpkg did what the dox said it shouldn't: namely deleting the currently active kernel. I'm surprised I didn't get a panic on the spot when dpkg pulled that stunt.

so I have no system (aside from an LFS rescue disk) until this rebuild of the kernel decides to get past the VFS problem (again I think disabling initrd support via menuconfig had something to do with it--I took it out becuase on *that* build I had panic issues stemming from an initrd enabled kernel not finding an initrd file, oh and the symlink I had to add to the initrd becuase make-kpkg seemed to have compiled the kernel to use one version name and set the module directory in the initrd otherwise).

The joys of surrogately mounting the filesystems and using
Code:
chroot /mountedroot/ bash
so I can recompile the kernel until it decides to work

UPDATE: I've got the kernel rebuilt and working again so that means the initrd support is required for udev (and it's 076 btw).

Last edited by gau_veldt; 08-28-2006 at 07:42 AM.
 
  


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
kernel panic - not syncing : VFS: unable to mount root FS on unknown-block Dankles Slackware 23 01-28-2011 03:01 AM
kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(3,2) o2bfishn Slackware 5 04-28-2006 03:51 PM
Kernel Panic!!! -Not Syncing VFS:Unable to mount root FS on unknown - block (0,0) scarabs Linux - Software 4 04-16-2006 04:16 PM
Kernel panic - not syncing: VFS: Unable to mount root fs on unkown-block(3,2) Rhatlinux Linux - General 12 02-14-2006 11:04 AM
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,2) Volgin Linux - Software 1 12-11-2005 07:46 PM


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