"Kernel Panic : VFS : Unable to mount root fs on 03:07"
Hi, SuSErs I have downloaded RPM for the latest SuSE Default Kernel. After executing mk_initrd, I have edited /etc/lilo.conf to load the new VMLINUZ , and, run LILO Any ideas , please, how to solve this problem on trying to boot the new default kernel :- "Kernel Panic : VFS : Unable to mount root fs on 03:07" thanks best wishes ____________ sent on Linux ____________
On Saturday 03 August 2002 20:11, tabanna wrote:
Hi, SuSErs
I have downloaded RPM for the latest SuSE Default Kernel.
After executing mk_initrd, I have edited /etc/lilo.conf to load the new VMLINUZ , and, run LILO
Any ideas , please, how to solve this problem on trying to boot the new default kernel :-
"Kernel Panic : VFS : Unable to mount root fs on 03:07"
When you say you edited lilo.conf it makes me a little curious, since normally you don't have to do that when you use suse's rpms. Could you post your lilo.conf, and also indicate how you created your initial ramdisk (ie. what parameters you used with mk_initrd)? //Anders
On Sunday 04 August 2002 06:24 am, Anders Johansson wrote:
"Kernel Panic : VFS : Unable to mount root fs on 03:07"
When you say you edited lilo.conf it makes me a little curious, since normally you don't have to do that when you use suse's rpms. Could you post your lilo.conf, and also indicate how you created your initial ramdisk (ie. what parameters you used with mk_initrd)?
Thank you, Anders, kindly :) I ran MK_INITRD without parameters [ presumably default was used ] My current kernel was compiled by me, from source. The RPM kernel that I am trying to install is called VMLINUZ the kernel rpm is called :- k%5fdeflt_2.4.18-231_i386.rpm { I suspect, that, /etc/sysconfig/kernel which contains, only : INITRD_MODULES = "reiserfs" maybe also needs module "ide-scsi" } This is my /etc/lilo.conf :- ......................................... # Modified by YaST2. Last modification on Fri Aug 2 18:36:13 2002 # LILO configuration file # Start LILO global Section # If you want to prevent console users to boot with init=/bin/bash, # restrict usage of boot params by setting a passwd and using the option # restricted. #password=bootpwd #restricted append = enableapic boot = /dev/hda # disk = /dev/scd0 #compact # faster, but won't work on all systems. lba32 vga = normal message = /boot/message menu-scheme = Wg:kw:Wg:Wg read-only prompt timeout = 100 image = /boot/sus8_080202 # image = /boot/vmlinuz label = sus80 optional root = /dev/hda7 image = /boot/memtest.bin label = memtest86 optional image = /boot/sus8_062502 label = sus8_rsv root = /dev/hda6 other = /dev/hda2 label = win2k table = /dev/hda ..................................... Thanks a ton :) { btw, this morning I saw a couple of List e-mails suggesting that, maybe, Mr. Hubert Mantel's recent default kernels may have overlooked something? } best wishes ____________ sent on SuSE 8 Linux ____________
On Sunday 04 August 2002 10:01, tabanna wrote:
This is my /etc/lilo.conf :- ......................................... # Modified by YaST2. Last modification on Fri Aug 2 18:36:13 2002 # LILO configuration file # Start LILO global Section # If you want to prevent console users to boot with init=/bin/bash, # restrict usage of boot params by setting a passwd and using the option # restricted. #password=bootpwd #restricted append = enableapic boot = /dev/hda # disk = /dev/scd0 #compact # faster, but won't work on all systems. lba32 vga = normal message = /boot/message menu-scheme = Wg:kw:Wg:Wg read-only prompt timeout = 100
image = /boot/sus8_080202 # image = /boot/vmlinuz label = sus80 optional root = /dev/hda7
OK, could you provide a little running commentary here please, because I'm confused. What is it that you've called sus8_080202? Is this the vmlinuz from the rpm? I don't see an entry for vmlinuz here, so I can't say were to edit, but the entry for the kernel in the rpm needs initrd=/boot/initrd or whatever you called the initrd you created. Also note that if you renamed the kernel before you ran mk_initrd it won't have created an initrd for it. In that case you need to explicitely give the name of the kernel with mk_initrd -k "kernelname" -i "initrdname" for a kernel named /boot/kernelname and an initrd to be created called /boot/initrdname //Anders
On Sunday 04 August 2002 08:18 am, Anders Johansson wrote: image = /boot/sus8_080202 # image = /boot/vmlinuz label = sus80 optional root = /dev/hda7 ________________ The Name I gave to "bzImage" compiled from kernel Source is : image = /boot/sus8_080202 Just below that, is, Hashed-Out, "image=/boot/vmlinuz" { Hashed-Out by me, after it failed to load.
edit, but the entry for the kernel in the rpm needs
initrd=/boot/initrd
THIS looks like "My_Problem" ! .....................
Also note that if you renamed the kernel before you ran mk_initrd it won't have created an initrd for it. In that case you need to explicitely give the name of the kernel with
mk_initrd -k "kernelname" -i "initrdname"
for a kernel named /boot/kernelname and an initrd to be created called /boot/initrdname
Gee, thanks . . . this, for me, is IMPortant lesson :o) Thanks a Ton, Anders. best wishes ____________ sent on Linux ____________
On Sunday 04 August 2002 08:18 am, Anders Johansson wrote: the entry for the kernel in the rpm needs initrd=/boot/initrd or whatever you called the initrd you created. ____________________________________ That was it ! . . . Thank you so much, Anders . . . works a Charm . . . Boots just Fine :) ______________ My CPU is an AMD K/6 : I imagine that running a standard default Kernel, which is NOT Optimised for AMD K/6 will result in some small sacrifice of efficiency, but, not significant for a non_power user like me :o) ? -- best wishes, rh ____________ sent on Linux ____________
** Reply to message from tabanna
** Reply to message from tabanna
participants (3)
-
Anders Johansson
-
Ed Harrison
-
tabanna