LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
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 08-18-2004, 11:36 PM   #1
abs
Member
 
Registered: Oct 2003
Posts: 203

Rep: Reputation: 30
kernel upgrade fails, VFS error (me too, have read other posts)


hi
getting the kernel panic vfs error:
Code:
Cannot open root device '1645' or unknown block (22,69)
specify boot..etc. with the 'root=' boot option.
using ext3 for all my parititions. decided to compile in ext2, 3, jbd and reiserfs anyway (i remember the old kernels need ext2 for ext3 but i think that's changed for 2.6.x).

tried initrd, doesn't work. a question about that. if initrd is compiled into the kernel, does it have to be used? tried with and without initrd compiled, doesn't work. i don't even see any ramdisk related messages.

i've installed mod-utils (mod-init-tools) pre-5.

the default slack 10 kernel 2.4.26 loads normally. using that *right now*.
got the same lines for the 2.6.x slack as the default. gave the old image the non-link names. works fine.

ty
abs

Last edited by abs; 08-18-2004 at 11:43 PM.
 
Old 08-19-2004, 02:49 AM   #2
nukkel
Member
 
Registered: Mar 2003
Location: Belgium
Distribution: Hardened gentoo
Posts: 323

Rep: Reputation: 30
Hi,

Are you sure it's trying the right device as root device? (22,69) should correspond to /dev/hdd5 is that your / partition?

If not, you may need to add root=/dev/<correct root device> to the boot command line; or alternatively use the rdev command to "bake" it into the kernel image.

Good luck
nukkel
 
Old 08-20-2004, 09:36 AM   #3
abs
Member
 
Registered: Oct 2003
Posts: 203

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by nukkel
Are you sure it's trying the right device as root device? (22,69) should correspond to /dev/hdd5 is that your / partition?
yes that's the correct one. (image is in /boot)

Quote:
Originally posted by nukkel
If not, you may need to add root=/dev/<correct root device> to the boot command line; or alternatively use the rdev command to "bake" it into the kernel image.
i'll try that. how come it's needed even though i've given that in lilo. will try that. will check rdev too. assuming i've compiled it right, can u think of any other reason it won't work?

also: http://www.linuxquestions.org/questi...hreadid=220150
 
Old 08-21-2004, 04:36 AM   #4
nukkel
Member
 
Registered: Mar 2003
Location: Belgium
Distribution: Hardened gentoo
Posts: 323

Rep: Reputation: 30
Quote:
Originally posted by abs
assuming i've compiled it right, can u think of any other reason it won't work?
Strange, the only thing I can think of is you forgot to compile in the driver for the IDE controller, or IDE disk support... Maybe double-check that, or check the output of the boot process to see if it detected the IDE controllers or the hard drive? There ought to be sth like "hda: xxxxxxx/yyyyyyy sectors; partitions: hda1 hda4 <hda5 hda6 hda7>"

BTW, when compiling your own kernel, there's no need to use initrd, it's just helpful to make very generic kernels. When building your own, you can make it very specific to your computer, eliminating the need for an initrd (I put sth in the other thread too about that)

Quote:
how come it's needed even though i've given that in lilo.
You need only do one of both; either put it in /etc/lilo.conf, either on the boot prompt. I just wasn't sure you had it in /etc/lilo.conf.
With rdev you can change the "default" behaviour, i.e. when neither of those two is set.
 
Old 08-21-2004, 06:07 PM   #5
abs
Member
 
Registered: Oct 2003
Posts: 203

Original Poster
Rep: Reputation: 30
ok
i installed the 2.6.7 kernel given in slack10. it has ext2 inbuilt. ext3 (and jbd) are modules. now, when i tried to boot that kernel, it worked fine. (even though my root file system is ext3). i didn't set up initrd for that kernel but it still worked. (1st case)

2. in dmesg, ext2 was being used to access the root filesystem, and then ext3-fs starts and handles it. cool eh? the initrd in this case has the same syntax as given in the README.initrd (except the kernel version).

EDIT: this output is from when the initrd.gz IS used. so i'm not sure what order it happens in. i figure it's loading the ext3 module from initrd after detecting the journal (since initally, ext2 is used from the kernel).
Code:
VFS: Mounted root (ext2 filesystem).
kjournald starting Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
so it works with and without initrd, though in the 2nd case, the ext3 'module' was loaded and used for the root filesystem, as is the exact purpose of initrd.

@nukkel: i might have missed the ide controller, seems like the only possibilty.

abs

other threads about all this:
http://www.linuxquestions.org/questi...hreadid=220150
http://www.linuxquestions.org/questi...hreadid=220154

Last edited by abs; 08-21-2004 at 11:21 PM.
 
Old 08-22-2004, 11:35 PM   #6
abs
Member
 
Registered: Oct 2003
Posts: 203

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by abs
@nukkel: i might have missed the ide controller, seems like the only possibilty.
yeah, that's what i didn't do fully. didn't enable all the things. not that i'm sure about what is and is not necessary.

got 2.6.8.1 running. to check out my continuing problems: http://www.linuxquestions.org/questi...92#post1126592 :P

Last edited by abs; 08-22-2004 at 11:38 PM.
 
Old 08-23-2004, 04:16 AM   #7
nukkel
Member
 
Registered: Mar 2003
Location: Belgium
Distribution: Hardened gentoo
Posts: 323

Rep: Reputation: 30
Yep, the nice thing about ext3 is that it can be mounted as ext2, without journalling. I didn't know however that when the ext3 module loads later on, it remounts it as full ext3. That's pretty cool
 
Old 08-23-2004, 01:20 PM   #8
abs
Member
 
Registered: Oct 2003
Posts: 203

Original Poster
Rep: Reputation: 30
yes, very!
 
  


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 upgrade fails, VFS error cragwolf Slackware 6 08-19-2004 01:17 AM
2.6.* kernel not booting slack VFS: and INIT: fails mus335 Slackware 9 04-22-2004 01:52 PM
kernel panic unable to mount root (yes ive read/read other posts) dmx9595 Linux - General 4 01-17-2004 05:07 AM
outgoing kernel: VFS: Error -5 HELP! What is this phurstname Linux - General 1 10-15-2003 07:36 PM
Kernel Panic (and yes, I have read the simmilar posts) BrokenUnity Linux - Newbie 6 09-14-2003 08:09 AM


All times are GMT -5. The time now is 10:24 AM.

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