View previous topic :: View next topic |
Author |
Message |
azlan Guru
Joined: 11 Nov 2002 Posts: 381 Location: Seattle WA USA
|
Posted: Sun Mar 02, 2003 11:21 pm Post subject: kernel panic |
|
|
I have posted this before but with no adiquite response.
after install I built my kernel, then I configured /proc....grub....
same as ever....
kernel ........
kmod: failed to exec /sbin/modprobe -s -k nls_iso8859-1, errno = 2
kernel panic: VFS: Unable to mount root fs on 03:03
I re-emerge'd system and tried building the kernel again.
I am using ReiserFS and have the reiserfs-progs installed.
what is my problem????
(besides the ones you can't see from there) _________________ there is no crazy, only violet and non violet.. |
|
Back to top |
|
|
neilhwatson l33t
Joined: 06 Feb 2003 Posts: 719 Location: Canada
|
Posted: Sun Mar 02, 2003 11:37 pm Post subject: |
|
|
Your kernel does have the file system support loaded to read /. Make sure you've compiled it in the kernel. You can do it as a module but that is harder and involved making a initial ram disk (mkinitrd). _________________ The true guru is a teacher.
Neil Watson |
|
Back to top |
|
|
azlan Guru
Joined: 11 Nov 2002 Posts: 381 Location: Seattle WA USA
|
Posted: Sun Mar 02, 2003 11:45 pm Post subject: of course |
|
|
Of course I have kernel compiled with rieserfs + internal checking built in. (I have always been afraid of making as a module in case something goes wrong during boot).
................well anyhoo _________________ there is no crazy, only violet and non violet.. |
|
Back to top |
|
|
Twist Guru
Joined: 03 Jan 2003 Posts: 414 Location: San Diego
|
Posted: Mon Mar 03, 2003 1:34 am Post subject: |
|
|
Code: | kmod: failed to exec /sbin/modprobe -s -k nls_iso8859-1, errno = 2 |
Looks like it's telling you what the problem is. Try checking on by default (not as a module) NLS ISO8859-1 in File Systems/Native Language Support of your kernel, then rebuild and reboot.
Of course, that's supposed to be the default, so it should work anyway, but it's worth a try. Unless you reset the default to something else (top of that same menu).
There are only a few basic reasons a kernel panics on mounting a filesystem: doesn't have support built in for the type, doesn't recognize the partition structure, finds an invalid file system (ie a trashed identifier block). Anything other than these and it should at least provide interesting error messages.
-Twist |
|
Back to top |
|
|
|