[mdlug] Kernel upgrade problems

May, Mat MCMay at RGIS.com
Tue Dec 18 14:00:58 EST 2007 

Ok, now this is totally driving me crazy, and I am sure that it is going
to be something really simple that I have overlooked once I pull my
forehead off the wall.  
 
I tried the entry that you listed below, and the system panicked again.
After some quick digging and few pushes of the power button I have the
following information:
 
The / partition is /dev/sda3
The /boot partition is /dev/sda1
Both the vmlinuz-2.4.21-53.ELsmp and initrd-2.4.21-53.ELsmp.img files
reside in the "/boot" directory (sorry if I am explaining things
everyone already knows)
Using e2label I have verified the following:  "/dev/sda1" is "/boot" and
"/dev/sda3" is "/"
Here are the results from various grub.conf configurations:
 
Boot using:       title Red Hat Enterprise Linux AS (2.4.21-53.ELsmp)
                        root (hd0,0)
                        kernel /vmlinuz-2.4.21-53.ELsmp ro
root=/dev/sda3
                        initrd /initrd-2.4.21-53.ELsmp.img
Result:                 
            Creating block devices
            Kmod: failed to exec /sbin/modprobe -s -k block-major8,
errno = 2
            VFS: Cannot open root device "sda3" or 08:03
            Please append a correct "root=" boot option
            Kernel panic: VFS: Unable to mount root fs on 08:03
 
Boot using:       title Red Hat Enterprise Linux AS (2.4.21-53.ELsmp)
                        root (hd0,0)
                        kernel /vmlinuz-2.4.21-53.ELsmp ro
root=LABEL=/boot
                        initrd /initrd-2.4.21-53.ELsmp.img
Results:          
            Creating block devices
            VFS: Cannot open root devices "LABEL=/boot" or 00:00
            Please append a correct "root=" boot option
            Kernel panic: VFS: Unable to mount root fs on 00:00
 
Boot using:       title Red Hat Enterprise Linux AS (2.4.21-53.ELsmp)
                        root (hd0,0)
                        kernel /vmlinuz-2.4.21-53.ELsmp ro
root=/dev/sda1
                        initrd /initrd-2.4.21-53.ELsmp.img  
Result:
Creating block device
Kmod: failed to exec /sbin/modprobe -s -k block-major-8, errno = 2
VFS: Cannot open root device "sda1" or 08:00
Please append a correct "root=" boot option
Kerner panic: VFS: Unable to mount root fs on 08:01
 
Boot using:       title Red Hat Enterprise Linux AS (2.4.21-53.ELsmp)
                        root (hd0,0)
                        kernel /vmlinuz-2.4.21-53.ELsmp ro root=LABEL=/
                        initrd /initrd-2.4.21-53.ELsmp.img
Result:     
Creating block devices
            VFS: Cannot open root device "LABEL=/" or 00:00
            Please append a correct "root=" boot option
            Kernel panic: VFS: Unable to mount root fs on 00:00
 
 
 
In a world without walls and fences, why do we need Windows and Gates?
 
Mathew May
 
RGIS LLC
 
Inventory System Support
 
mcmay at rgis.com
 
(248)608-8244
 
 
 
-----Original Message-----
From: mdlug-bounces at mdlug.org [mailto:mdlug-bounces at mdlug.org] On Behalf
Of Wojtak, Greg
Sent: Tuesday, December 18, 2007 8:10 AM
To: MDLUG's Main discussion list
Subject: Re: [mdlug] Kernel upgrade problems
 
Unless you have another /boot partition, the root(hd0,0) should stay the
same.  This is the grub root, not the system root (/).  Try this entry:
 
title Red Hat Enterprise Linux AS (2.4.21-53.ELsmp)
        root (hd0,0)
        kernel /vmlinuz-2.4.21-53.ELsmp ro root=/dev/sda3
        initrd /initrd-2.4.21-53.ELsmp.img
 
 
Note the changes to the "root" line and the "kernel" line.
 
Greg
 
 
On 12/17/07 4:05 PM, "May, Mat" <MCMay at RGIS.com> wrote:
 
> I am running RHEL AS 3 Update 9 on Dell PowerEdge 2850s and I have
just
> updated the kernel from 2.4.21-27.0.4.ELsmp to 2.4.21-53.ELsmp and
when
> I reboot the server to use the new kernel I get the following error:
>  
>             VFS: Cannot open root device "LABEL=/" or 00:00
>             Please append a correct "root=" boot option
>             Kernel panic: VFS: Unable to mount root fs on 00:00
>  
> I then went into the grub.conf and changed the entry replacing the
> "LABEL=" with "/dev/sda3" which is my / partition and also changed the
> "root=" from 0:0 to 0:2.  After reboot I received the following error:
>  
>             Kmod: failed to exec /sbin/modprobe -s -k block-major-8,
> errno = 2
>             VFS: Cannot open root device "sda3" or 08:03
>             Please append a corrent "root=" boot option
>             Kernel panic: VFS: Unable to mount root fs on 08:30
>  
> Here are my grub.conf and device.map files.
>  
> Grub.conf
>  
> [root at dc1-21 grub]# more grub.conf
> # grub.conf generated by anaconda
> #
> # Note that you do not have to rerun grub after making changes to this
> file
> # NOTICE:  You have a /boot partition.  This means that
> #          all kernel and initrd paths are relative to /boot/, eg.
> #          root (hd0,0)
> #          kernel /vmlinuz-version ro root=/dev/sda3
> #          initrd /initrd-version.img
> #boot=/dev/sda
> default=1
> timeout=10
> splashimage=(hd0,0)/grub/splash.xpm.gz
> title Red Hat Enterprise Linux AS (2.4.21-53.EL)
>         root (hd0,0)
>         kernel /vmlinuz-2.4.21-53.EL ro root=LABEL=/
>         initrd /initrd-2.4.21-53.EL.img
> title Red Hat Enterprise Linux AS (2.4.21-53.ELsmp)
>         root (hd0,2)
>         kernel /vmlinuz-2.4.21-53.ELsmp ro root=LABEL=/
>         initrd /initrd-2.4.21-53.ELsmp.img
> title Red Hat Enterprise Linux AS (2.4.21-27.0.4.EL)
>         root (hd0,0)
>         kernel /vmlinuz-2.4.21-27.0.4.EL ro root=LABEL=/
>         initrd /initrd-2.4.21-27.0.4.EL.img
> title Red Hat Enterprise Linux AS (2.4.21-27.0.4.ELsmp)
>         root (hd0,0)
>         kernel /vmlinuz-2.4.21-27.0.4.ELsmp ro root=LABEL=/
>         initrd /initrd-2.4.21-27.0.4.ELsmp.img
>  
> device.map
>  
> [root at dc1-21 grub]# more device.map
> # this device map was generated by anaconda
> (fd0)     /dev/fd0
> (hd0)     /dev/sda
>  
> I can boot into the older kernel version no problem, but I cannot
figure
> out what to change to allow me to boot into the newer version.  Any
help
> would be greatly appreciated.
>  
>  
> In a world without walls and fences, why do we need Windows and Gates?
> Mathew May
> RGIS LLC
> Inventory System Support
> mcmay at rgis.com
> (248)608-8244
>  
>  
> 
> 
> NOTE: The information in this email may be confidential and legally
> privileged. If you are not the intended recipi-ent, you must not read,
use or
> disseminate the information; please advise the sender immediately by
reply
> email and delete this message and any attachments without retaining a
copy.
> Although this email and any attachments are believed to be free of any
virus
> or other defect that may affect any computer system into which it is
received
> and opened, it is the responsibility of the recipient to ensure that
it is
> virus free and no responsibility is accepted by RGIS, LLC for any loss
or
> damage arising in any way from its use.
> _______________________________________________
> mdlug mailing list
> mdlug at mdlug.org
> http://mdlug.org/mailman/listinfo/mdlug
 
_______________________________________________
mdlug mailing list
mdlug at mdlug.org
http://mdlug.org/mailman/listinfo/mdlug


NOTE: The information in this email may be confidential and legally privileged. If you are not the intended recipi­ent, you must not read, use or disseminate the information; please advise the sender immediately by reply email and delete this message and any attachments without retaining a copy. Although this email and any attachments are believed to be free of any virus or other defect that may affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by RGIS, LLC for any loss or damage arising in any way from its use.

More information about the mdlug mailing list