LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora - Installation (http://www.linuxquestions.org/questions/fedora-installation-39/)
-   -   Upgrade kernel (FC5) loses root partition (http://www.linuxquestions.org/questions/fedora-installation-39/upgrade-kernel-fc5-loses-root-partition-487833/)

flobadob 09-28-2006 08:43 PM

Upgrade kernel (FC5) loses root partition
 
Hello, I did a fresh install of FC5. Everything works fine with kernel.x86_64 .2.6.15-1.2054_FC5 when I yum update to kernel.x86_64.2.6.17-1.2187_FC5 I cannot boot the new kernel. I get an error along the lines of 'mount: can't find root'. I have tried the solution where I gunzip /boot/initrd-2.6.17-1.2187_FC5.img and edit init to be...
#mount /sysroot
mount -o defaults --ro -t ext3 /dev/sdb3 /sysroot
...but then I just get a similar message where it can't find /dev/sdb3. I have tried /dev/hdf3 and /dev/hde3 also.

here is my fstab...
Code:

LABEL=/                /                      ext3    defaults        1 1
LABEL=/boot            /boot                  ext3    defaults        1 2
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
tmpfs                  /dev/shm                tmpfs  defaults        0 0
proc                    /proc                  proc    defaults        0 0
sysfs                  /sys                    sysfs  defaults        0 0
LABEL=SWAP-sdb4        swap                    swap    defaults        0 0

here is grub.conf...
Code:

#boot=/dev/sdb
default=2
timeout=20
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.17-1.2187_FC5)
        root (hd0,0)
        kernel /vmlinuz-2.6.17-1.2187_FC5 ro root=LABEL=/ rhgb quiet
        initrd /initrd-2.6.17-1.2187_FC5.img
title Fedora Core (2.6.15-1.2054_FC5)
        root (hd0,0)
        kernel /vmlinuz-2.6.15-1.2054_FC5 ro root=LABEL=/ rhgb quiet
        initrd /initrd-2.6.15-1.2054_FC5.img
title Windows XP
        map (hd0) (hd1)
        map (hd1) (hd0)
        rootnoverify (hd1,0)
        chainloader +1

here is grubs device.map...
Code:

(hd1)    /dev/sda
(hd0)    /dev/sdb

here is fdisk -l...
Code:

Disk /dev/sda: 320.0 GB, 320071851520 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start        End      Blocks  Id  System
/dev/sda4  *          1      38912  312560608+  7  HPFS/NTFS

Disk /dev/sdb: 160.0 GB, 160040803840 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start        End      Blocks  Id  System
/dev/sdb1  *          1          13      104391  83  Linux
/dev/sdb2          16908      19457    20482875    f  W95 Ext'd (LBA)
/dev/sdb3              14      16524  132624607+  83  Linux
/dev/sdb4          16525      16906    3068415  82  Linux swap / Solaris
/dev/sdb5          16908      19457    20482843+  b  W95 FAT32

Partition table entries are not in disk order

Any ideas please? Doing my head in.

Leisy 09-29-2006 09:19 PM

I would try mount -o defaults --ro -t ext3 /dev/sda3 /sysroot

and I would also try to check disk/partition numbers in grub.conf when you get error 'mount: can't find root'

flobadob 09-30-2006 05:29 PM

Quote:

Originally Posted by Leisy
I would try mount -o defaults --ro -t ext3 /dev/sda3 /sysroot

and I would also try to check disk/partition numbers in grub.conf when you get error 'mount: can't find root'

Didn't work. grub.conf looks fine. Remember that everything worked ok on fc5 kernel 2.6.15 and the grub.conf is similar for the new kernel. My / partition is definately /dev/sdb3 I have tried /dev/hde also since I think this is equivolent?

jcliburn 10-01-2006 12:31 PM

A few things to try...

1. Install the current FC5 testing kernel. It's based on kernel version 2.6.18 and may have a bugfix that helps you.

2. Add the following to your kernel command line: vga=791
This will result in more lines per screen displayed during boot. Check to see if libata.ko and scsi_mod.ko are listed in the boot messages. If they're not, you may have to make a new initrd. It's easy, but not necessary until we know for sure that's the problem.

3. In a working kernel, run "/sbin/lspci -v" and paste the results here.

flobadob 10-01-2006 05:06 PM

Quote:

Originally Posted by jcliburn
A few things to try...

1. Install the current FC5 testing kernel. It's based on kernel version 2.6.18 and may have a bugfix that helps you.

The update to the development 2.6.18 kernel is working. Thanks. Now all I need to do is find a kmod-nvidia for this kernel :)


All times are GMT -5. The time now is 11:05 PM.