RE: kernel wont boot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Title: RE: kernel wont boot

Roger,

Are you using grub or lilo?  Not that it matters but the config is a little different.  Make sure you have the new kernel in the config file.  Make sure you have the initrd to match your version of the kernel.  If not use mkinitrd to create the initrd.  Read the manpage for the syntax, it's pretty simple.  I've never had this happen to me using up2date but that doesn't mean it can't.  I don't use labels for my partitions, I typically just boot the root device so if you are using labels it may be a function of loading the modules using the ramdisk(initrd).

Drew

-----Original Message-----
From: Roger Beever [mailto:roger2@xxxxxxxxxxxx]
Sent: Tuesday, February 03, 2004 1:19 PM
To: redhat list
Subject: RE: kernel wont boot


On Tue, 2004-02-03 at 15:31, Hamilton Andrew wrote:
> This means that in your /boot/grub/grub.conf file you have a line that
> looks like this:
>
> kernel /vmlinuz-2.4.20 ro root=<some device>,  or something similar
>
> The "root=" part of it needs to be a valid root partition or a label
> that points to a valid root partition.
>
> One thing that might be happening if you are using modules for you
> disk controllers, you may need to make a ramdisk, "initrd" file.  I
> would recommend that you do this if you have any modules that are
> needed to load hardware drivers.  To do this use mkinitrd.  To figure
> out how to use mkinitrd just read the man page.  It's pretty simple.
>
> Regards,
>
> Drew
>
> -----Original Message-----
> From: Ashish Samant [mailto:als1140@xxxxxxxxxx]
> Sent: Tuesday, February 03, 2004 9:36 AM
> To: redhat-list@xxxxxxxxxx
> Subject: kernel wont boot
>
>
>
>
> Hi...
>
> I was trying to compile and install a new kernel, from a clean kernel
> source (2.4.20). But looks like I messed up some step and now I cant
> boot
> with the new kernel. I can however get back to my old one.I am going
> to
> try redoing the whole thing, but not quite sure, what should I do
> differently.
>
> Could anybody tell me what could have gone wrong with my last attempt
> ? I
> got the following error when I tried to boot the new kernel :
>
> .............
> VFS : cannot open root device "Label=/1" OR 00:00
> Please append a correct "root=" boot option
> Kernel panic :VFS Unable to mount fs on 00:00
> .......
>
> What does that above statement mean ?
> If it would help, here is my lilo.conf

Sorry to partly hijack the post.
But I get the same thing when trying to run the current RH9 Kernel
All I did was get the new kernel as part of an up2date.
Why does it complain when the previous version was happy.

Please rename the thread if you feel the to are not related.
Regards Roger



--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list


[Index of Archives]     [CentOS]     [Kernel Development]     [PAM]     [Fedora Users]     [Red Hat Development]     [Big List of Linux Books]     [Linux Admin]     [Gimp]     [Asterisk PBX]     [Yosemite News]     [Red Hat Crash Utility]


  Powered by Linux