| View previous topic :: View next topic |
| Author |
Message |
Aquiles
Apprentice
Joined: 23 Feb 2007
Posts: 230
Location: Somewhere, surrounded by my circumstances.
|
 Posted: Sat Sep 06, 2008 12:00 pm Post subject: [SOLVED] Problems upgrading Kernel |
 |
|
Hello there,
I'm willing to upgrade my fully working 2.6.23-r8 to a new 2.6.25-r7. I'm a genkernel user, so my idea is to build a basic kernel that allows me to start up the system and then fine tune it as I go. To achieve that I did a "genkernel all" but the thing is that, during startup, it complains about my root partition not being a valid block device. Here's the thing:
My /etc/fstab looks like this (only relevant entries shown):
| Code: |
/dev/sda6 / ext3 noatime 0 1
/dev/sda5 /usr ext3 noatime 0 1
/dev/sda3 none swap sw 0 0
/dev/sda4 /home/joan/data ext3 auto,rw 0 0
/dev/hdb1 /home/joan/downloads ext3 auto,rw 0 0
|
As you see, the root filesystem is /dev/sda6 and /usr is in a different partition.
Now, my /boot/grub/grub.conf looks like this:
| Code: |
default 0
timeout 10
#splashimage=(hd0,5)/boot/grub/splash.xpm.gz
title=Gentoo Linux 2.6.23-r8
root (hd0,5)
kernel /boot/kernel-genkernel-x86-2.6.23-gentoo-r8 root=/dev/ram0 quiet init=/linuxrc ramdisk=8192 real_root=/dev/sda6 vga=0x31b
initrd /boot/initramfs-genkernel-x86-2.6.23-gentoo-r8
title=Gentoo Linux 2.6.25-r7
root (hd0,5)
kernel /boot/kernel-genkernel-x86-2.6.25-gentoo-r7 root=/dev/ram0 quiet init=/linuxrc ramdisk=8192 real_root=/dev/sda6 vga=0x31b
initrd /boot/initramfs-genkernel-x86-2.6.25-gentoo-r7
|
Now, the thing is, as I said, that the new 2.6.25-r7 version is complaining about /dev/sda6 not being a valid block device or something like this. But the old 2.6.23-r8 version starts fine like it always did.
Any hint about where the problem lies?
EDIT: I'm gonna be a bit more precise. Grub is installed in /dev/sda6 (I've got another boot manager in the MBR). In the grub menu I choose the new kernel and it starts loading modules or doing stuff, I don't know. Then it says the following:
| Code: |
>> Activating mdev
mdev://sys/class/scsi_host/host0/device: No such file or directory
mdev://sys/class/scsi_host/host1/device: No such file or directory
>> Determining root device
!! Block device /dev/sda6 is not a valid root device
|
The thing is immediately after that it prompts for a valid root device. It turns out that if I try /dev/sdc6 (that is C instead of A) it actually continues the startup but after a few lines there is an error related to ext3 saying that /dev/sda6: no such file or directory (note the A in /dev/sda6)
Now, is it possible that this new kernel is labelling my drives differently, so that according to the old kernel my root partition is /dev/sda6 but according to the new one it is /dev/sdc6???
What I understand until I run some more tests is that the kernel looks for /dev/sda6, but it doesn't exist. Then I manually tell him to continue with /dev/sdc6, but immediately after it tries to mount /dev/sda6 according to /etc/fstab, so it fails again. This makes sense?
I'll try to change /dev/sda6 to /dev/sdc6 in real_root in grub.conf and also in /etc/fstab to see if it starts up. But if this is the case, then I'm gonna be f*ck*d up because each time I want to start the old kernel I'll have to change it back.
_________________
Aquiles
Last edited by Aquiles on Sun Sep 07, 2008 8:40 am; edited 1 time in total |
|
| Back to top |
|
 |
Aquiles
Apprentice
Joined: 23 Feb 2007
Posts: 230
Location: Somewhere, surrounded by my circumstances.
|
| Posted: Sat Sep 06, 2008 5:50 pm Post subject: |
|
|
Well, I'm going to reply my own post: it turns out the things went as I suspected. I have three hard disks, two ATA and one SATA. In the previous kernel version the two ATA drives were hda and hdb, and the SATA drive was sda. Now the new kernel puts the ATA drives in sda and sdb, so the actual SATA drive falls to sdc. I don't know what option of the kernel configuration makes this change to take place...
Fortunately, I've managed to get everything working again pretty fast, so now I can definitely remove the old kernel and settle everything.
Anyway, I still get the following message during startup:
| Code: |
>> Activating mdev
mdev://sys/class/scsi_host/host0/device: no such file or directory
mdev://sys/class/scsi_host/host1/device: no such file or directory
|
How can I get rid of it?
_________________
Aquiles |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
