[SLE] Classic "VFS unable to mount root fs" Problem
Hi, I get the classic "VFS unable to mount root fs..." message on boot after I modified my /etc/sysconfig/kernel file. I added in cdrom and ide-cd after reiserfs. I think the error is because I didn't run lilo after I ran mk_initrd. How can I fix this or how can I boot an old kernel (if there is one)? I'm running 8.1. Thanks. Also, does anyone know a server with 8.2 (not live-eval). ===== This has been a test of the emergency broadcasting channel, if this was an actual emergency, you would be dead. __________________________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo http://search.yahoo.com
once upon a short time ago, before initrd, it was very simple to compile new kernels..having been in the solaris world by day, i am quite behind on linux kernel compiling, is there any FAQ on compiling kernels for SuSE? I mean step-by-step Thanks, Rob On Tue, 2003-04-15 at 10:34, VB wrote:
Hi,
I get the classic "VFS unable to mount root fs..." message on boot after I modified my /etc/sysconfig/kernel file. I added in cdrom and ide-cd after reiserfs. I think the error is because I didn't run lilo after I ran mk_initrd.
How can I fix this or how can I boot an old kernel (if there is one)? I'm running 8.1. Thanks.
Also, does anyone know a server with 8.2 (not live-eval).
===== This has been a test of the emergency broadcasting channel, if this was an actual emergency, you would be dead.
__________________________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo http://search.yahoo.com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
* Robert Joost (rjoost@yahoo.com) [030415 10:35]:
is there any FAQ on compiling kernels for SuSE?
There's nothing special about SuSE kernels.
I mean step-by-step
cd /usr/src/linux make cloneconfig make menuconfig make dep bzImage modules modules_install cp arch/i386/boot/bzImage /boot/vmlinuz cp System.map /boot/ vi /etc/sysconfig/kernel # in case you need to add an additional module to INITRD_MODULES mk_initrd lilo # if you aren't using grub init 6 If you are rbuilding the kernel you might as well build your scsi controller and reiserfs into the kernel, then you don't need initrd. -- -ckm
I just have to add the mk_initrd step... thanks On Tue, 2003-04-15 at 11:27, Christopher Mahmood wrote:
* Robert Joost (rjoost@yahoo.com) [030415 10:35]:
is there any FAQ on compiling kernels for SuSE?
There's nothing special about SuSE kernels.
I mean step-by-step
cd /usr/src/linux make cloneconfig make menuconfig make dep bzImage modules modules_install cp arch/i386/boot/bzImage /boot/vmlinuz cp System.map /boot/ vi /etc/sysconfig/kernel # in case you need to add an additional module to INITRD_MODULES mk_initrd lilo # if you aren't using grub init 6
If you are rbuilding the kernel you might as well build your scsi controller and reiserfs into the kernel, then you don't need initrd.
--
-ckm
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
make dep bzImage modules modules_install
How about a mv step to keep the old kernel/modules around? My *old* instructions follow: make menuconfig make dep make bzImage make modules mv /lib/modules/current /lib/modules/old make modules_install vi /etc/lilo.conf mv /boot/bzImage /boot/bzOld cp /usr/src/linux/arch/i386/boot/bzImage /boot/bzImage /sbin/lilo cp /usr/src/linux/System.map /boot/System.map-x.x.x I guess somwhat of a lot has changed. This instructions are so old the pencil markings are starting to fade. They've been pasted to my monitor for at least 5 years now. -- John LeMay KC2KTH Senior Enterprise Consultant NJMC | http://www.njmc.com | Phone 732-557-4848 Specializing in Microsoft and Unix based solutions
* John LeMay (jlemay@njmc.com) [030415 11:56]:
I guess somwhat of a lot has changed. This instructions are so old the pencil markings are starting to fade. They've been pasted to my monitor for at least 5 years now.
No, your receipt is good because because you keep the old kernel around. -- -ckm
On Tue, 2003-04-15 at 20:58, John LeMay wrote:
make dep bzImage modules modules_install
How about a mv step to keep the old kernel/modules around? My *old* instructions follow:
make menuconfig make dep make bzImage make modules mv /lib/modules/current /lib/modules/old
It's better to set EXTRAVERSION in the top level makefile. Then you won't have to boot from a rescue CD and move the modules directory back if something goes wrong, you'll be able to boot straight into the old kernel. If you're compiling 2.4.20 and set EXTRAVERSION to -foo, the newly created modules directory will be called 2.4.20-foo and can coexist with the old modules dir.
make modules_install vi /etc/lilo.conf mv /boot/bzImage /boot/bzOld
Same comment. I always keep the old kernel/modules around and give the new a different name until I'm sure everything works.
Thanks! On Tue, 2003-04-15 at 11:58, John LeMay wrote:
make dep bzImage modules modules_install
How about a mv step to keep the old kernel/modules around? My *old* instructions follow:
make menuconfig make dep make bzImage make modules mv /lib/modules/current /lib/modules/old make modules_install vi /etc/lilo.conf mv /boot/bzImage /boot/bzOld cp /usr/src/linux/arch/i386/boot/bzImage /boot/bzImage /sbin/lilo cp /usr/src/linux/System.map /boot/System.map-x.x.x
I guess somwhat of a lot has changed. This instructions are so old the pencil markings are starting to fade. They've been pasted to my monitor for at least 5 years now.
-- John LeMay KC2KTH Senior Enterprise Consultant NJMC | http://www.njmc.com | Phone 732-557-4848 Specializing in Microsoft and Unix based solutions
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Wow you guys sure went off on a tangent...I'm going to
have to refresh my original question:
Hi,
I get the classic "VFS unable to mount root fs..."
message on boot after I modified my
/etc/sysconfig/kernel file. I added in
'INITRD_MODULES=cdrom' and
'INITRD_MODULES=ide-cd' after
'INITRD_MODULES=reiserfs'. I think the error is
because I
didn't run lilo after I ran mk_initrd.
How can I fix this or how can I boot an old kernel (if
there is one)? I'm running 8.1. Thanks.
Also, does anyone know a server with 8.2 (not
live-eval).
--- Robert Joost
Thanks!
make dep bzImage modules modules_install
How about a mv step to keep the old kernel/modules around? My *old* instructions follow:
make menuconfig make dep make bzImage make modules mv /lib/modules/current /lib/modules/old make modules_install vi /etc/lilo.conf mv /boot/bzImage /boot/bzOld cp /usr/src/linux/arch/i386/boot/bzImage /boot/bzImage /sbin/lilo cp /usr/src/linux/System.map /boot/System.map-x.x.x
I guess somwhat of a lot has changed. This instructions are so old the pencil markings are starting to fade. They've been
On Tue, 2003-04-15 at 11:58, John LeMay wrote: pasted to my monitor
for at least 5 years now.
-- John LeMay KC2KTH Senior Enterprise Consultant NJMC | http://www.njmc.com | Phone 732-557-4848 Specializing in Microsoft and Unix based solutions
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
===== This has been a test of the emergency broadcasting channel, if this was an actual emergency, you would be dead. __________________________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo http://search.yahoo.com
On Tue, Apr 15, 2003 at 01:19:45PM -0700, VB wrote:
Wow you guys sure went off on a tangent...I'm going to have to refresh my original question:
Hi,
I get the classic "VFS unable to mount root fs..." message on boot after I modified my /etc/sysconfig/kernel file. I added in 'INITRD_MODULES=cdrom' and 'INITRD_MODULES=ide-cd' after 'INITRD_MODULES=reiserfs'. I think the error is because I didn't run lilo after I ran mk_initrd.
How can I fix this or how can I boot an old kernel (if there is one)? I'm running 8.1. Thanks.
Boot to the CD/DVD. Boot installed system. run mk_initrd run lilo reboot without the CD. -- Brad Shelton On Line Exchange http://ole.net Phone: 313-526-1111 Fax: 313-526-3333
On Tue, 2003-04-15 at 22:19, VB wrote:
Wow you guys sure went off on a tangent...I'm going to have to refresh my original question:
Hi,
I get the classic "VFS unable to mount root fs..." message on boot after I modified my /etc/sysconfig/kernel file. I added in 'INITRD_MODULES=cdrom' and 'INITRD_MODULES=ide-cd' after 'INITRD_MODULES=reiserfs'.
Are you saying you have this on three different lines in that file? That won't work. Try INITRD_MODULES="cdrom ide-cd reiserfs"
I think the error is because I didn't run lilo after I ran mk_initrd.
Are you using lilo? 8.1 by default uses grub, and with grub you don't have to run anything. Just make sure your files are referenced by /boot/grub/menu.lst
How can I fix this or how can I boot an old kernel (if there is one)? I'm running 8.1. Thanks.
Boot from the first CD or DVD. Select installation. When YaST starts up, you get a new choice. From that menu select "boot installed system". method #2: boot from the first CD or DVD and select Rescue system.
Thanks Anders!! Worked like a charm.
--- Anders Johansson
On Tue, 2003-04-15 at 22:19, VB wrote:
Wow you guys sure went off on a tangent...I'm going to have to refresh my original question:
Hi,
I get the classic "VFS unable to mount root fs..." message on boot after I modified my /etc/sysconfig/kernel file. I added in 'INITRD_MODULES=cdrom' and 'INITRD_MODULES=ide-cd' after 'INITRD_MODULES=reiserfs'.
Are you saying you have this on three different lines in that file? That won't work. Try
INITRD_MODULES="cdrom ide-cd reiserfs"
I think the error is because I didn't run lilo after I ran mk_initrd.
Are you using lilo? 8.1 by default uses grub, and with grub you don't have to run anything. Just make sure your files are referenced by /boot/grub/menu.lst
How can I fix this or how can I boot an old kernel
(if
there is one)? I'm running 8.1. Thanks.
Boot from the first CD or DVD. Select installation. When YaST starts up, you get a new choice. From that menu select "boot installed system".
method #2: boot from the first CD or DVD and select Rescue system.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
===== This has been a test of the emergency broadcasting channel, if this was an actual emergency, you would be dead. __________________________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo http://search.yahoo.com
Thank you very much. Such step by step instructions are a great help. I assume that if we have grub, then we do not need to reconfigure its since it isn't listed? Is that correct? -Trey
I mean step-by-step
cd /usr/src/linux make cloneconfig make menuconfig make dep bzImage modules modules_install cp arch/i386/boot/bzImage /boot/vmlinuz cp System.map /boot/ vi /etc/sysconfig/kernel # in case you need to add an additional module to INITRD_MODULES mk_initrd lilo # if you aren't using grub init 6
If you are rbuilding the kernel you might as well build your scsi controller and reiserfs into the kernel, then you don't need initrd.
participants (7)
-
Anders Johansson -
Brad Shelton -
Christopher Mahmood -
John LeMay -
Robert Joost -
Trey -
VB