Cant find boot device after kernel update

Message

zpon · Post by **zpon** » Fri Aug 18, 2006 6:43 pm

I'm not sure this is the right place on this forum, but here we go, any way.

After updating my kernel (following the guide "Gentoo Linux Kernel Upgrade Guide"), I suddenly get problems when booting up the new kernel:

Code: Select all

* Block device /dev/hda3 is not a valid root device
* The root device is unspecified or not detected

But if I changes GRUB to boot the old kernel it works fine. I've done this several times, but never met this problem before.

My /boot/grub/grub.conf

Code: Select all

default 0
timeout 15
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
splash=silent

title=Gentoo Linux
root (hd0,0)
kernel /boot/kernel-genkernel-x86-2.6.17-gentoo-r4 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda3 udev
initrd /boot/initramfs-genkernel-x86-2.6.17-gentoo-r4
vga=791

And my /etc/fstab

Code: Select all

# This file is edited by fstab-sync - see 'man fstab-sync' for details
# /etc/fstab: static file system information.
# $Header: /var/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.18.4.1 2005/01/31 23:05:14 vapier Exp $
#
# noatime turns off atimes for increased performance (atimes normally aren't 
# needed; notail increases performance of ReiserFS (at the expense of storage 
# efficiency).  It's safe to drop the noatime options if you want and to 
# switch between notail / tail freely.
#
# See the manpage fstab(5) for more information.

# <fs>			<mountpoint>	<type>		<opts>		<dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda1		/boot		ext2		noauto,noatime		1 2
/dev/hda3		/		ext3		noatime			0 1
/dev/hda2		none		swap		sw			0 0
/dev/hdb1		/mnt/160	vfat		noatime,users		0 1
/dev/cdroms/cdrom0	/mnt/dvd	iso9660		noauto,ro		0 0
/dev/cdroms/cdrom1	/mnt/cdrom	iso9660		noauto,ro		0 0
/dev/sda1		/mnt/usb	vfat		noatime,users		0 1
/dev/fd0		/mnt/floppy	auto		noauto			0 0

# NOTE: The next line is critical for boot!
proc			/proc		proc		defaults	0 0

# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for 
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
#  use almost no memory if not populated with files)
shm			/dev/shm	tmpfs		nodev,nosuid,noexec	0 0
/dev/hdd                /media/cdrecorder       auto    user,exec,noauto,managed 0 0
/dev/hdc                /media/cdrecorder1      auto    user,exec,noauto,managed 0 0

Can anybody help?

morodoch · Post by **morodoch** » Fri Aug 18, 2006 7:17 pm

Is it possible that your new kernel is missing a driver it needs to access the device (ata controller, ...)?

Try diffing the .config files for your old & new kernel and look through any changes. (This may be a big job if the two kernels are far apart in version numbers).

zpon · Post by **zpon** » Fri Aug 18, 2006 7:37 pm

They were both maid with genkernel
My old kernel was kernel-genkernel-x86-2.6.16-gentoo-r7 and my new kernel-genkernel-x86-2.6.17-gentoo-r4

morodoch · Post by **morodoch** » Fri Aug 18, 2006 7:40 pm

You should still have a .config for both source trees, and could try diffing them.

I sometimes use something like this to make sure my config is more-or-less the same:

Code: Select all

cd /usr/src/linux.new.version
make clean; make mrproper
cp /usr/src/linux.old.version/.config .
make oldconfig
genkernel --kerneldir=`pwd` --oldconfig [other options]

I'm sure this is a hack, but it seems to work.

zpon · Post by **zpon** » Fri Aug 18, 2006 7:52 pm

Okay, should pwd be substituted with something?

morodoch · Post by **morodoch** » Fri Aug 18, 2006 7:57 pm

If you've done the first bit about cd'ing into your new kernel directory, it should be fine.

zpon · Post by **zpon** » Fri Aug 18, 2006 8:01 pm

Okay, I'll give it a try, it usually takes some time to compile the new kernel, but I will be back with the result when done

zpon · Post by **zpon** » Fri Aug 18, 2006 8:31 pm

That didn't seem to work

Code: Select all

* ERROR: Failed to compile the "modules" target...

* -- Grepping log... --

  SCSI media changer support (CHR_DEV_SCH) [M/n/y/?] m
  *
  * Some SCSI devices (e.g. CD jukebox) support multiple LUNs
  *
  Probe all LUNs on each SCSI device (SCSI_MULTI_LUN) [N/y/?] n
  Verbose SCSI error reporting (kernel size +=12K) (SCSI_CONSTANTS) [N/y/?] n
--
    Verbose debugging output (INFINIBAND_MTHCA_DEBUG) [N/y/?] n
IP-over-InfiniBand (INFINIBAND_IPOIB) [M/n/?] m
  IP-over-InfiniBand debugging (INFINIBAND_IPOIB_DEBUG) [N/y/?] n
InfiniBand SCSI RDMA Protocol (INFINIBAND_SRP) [N/m/?] n
*
* EDAC - error detection and reporting (RAS) (EXPERIMENTAL)
*
EDAC core system error reporting (EXPERIMENTAL) (EDAC) [N/m/y/?] n
--
  CC      net/core/link_watch.o
  CC      drivers/scsi/sr_ioctl.o
  CC      net/core/filter.o
  CC      drivers/scsi/sr_vendor.o
  CC      drivers/scsi/advansys.o
drivers/scsi/advansys.c:795:2: advarsel: #warning this driver is still not properly converted to the DMA API
--
  CC [M]  drivers/net/lne390.o
  CC [M]  drivers/net/ne3210.o
  CC [M]  drivers/net/b44.o
  CC [M]  drivers/net/forcedeth.o
drivers/net/forcedeth.c: I funktionen 'nv_init_tx':
drivers/net/forcedeth.c:1141: internal compiler error: Lagersegmentfejl
--
make[1]: *** [drivers/net] Fejl 2
make: *** [drivers] Fejl 2
* Gentoo Linux Genkernel; Version 3.4.0
* Running with options: --kerneldir=/usr/src/linux-2.6.17-gentoo-r4 --oldconfig --bootloader=grub all

* ERROR: Failed to compile the "modules" target...

* -- End log... --

* Please consult /var/log/genkernel.log for more information and any
* errors that were reported above.

* Report any genkernel bugs to bugs.gentoo.org and
* assign your bug to genkernel@gentoo.org. Please include
* as much information as you can in your bug report; attaching
* /var/log/genkernel.log so that your issue can be dealt with effectively.
*
* Please do *not* report compilation failures as genkernel bugs!
*

morodoch · Post by **morodoch** » Fri Aug 18, 2006 9:49 pm

Hmm:

drivers/net/forcedeth.c internal compiler error: Lagersegmentfejl

This looks like a compiler bug?

Do you use the forcedeth driver? If not, try disabling it (try make menuconfig, then the genkernel again with the --oldconfig). If so, I guess you could try emerging a different version of gcc, then re-compiling from clean.

OTOH it's possibly a hardware fault (cpu/memory/swap). Does this seem likely? Do you overclock?

zpon · Post by **zpon** » Fri Aug 18, 2006 10:15 pm

I wasn't that patience when i used "make oldconfig", so i just typed yes to them all, maybe that could have caused the problem?
No i have never overclocked this computer.
right now i am giving "genkernel --bootloader=grub all" a try again.

morodoch · Post by **morodoch** » Fri Aug 18, 2006 10:37 pm

I'm pretty sure that you shouldn't be able to generate an "internal compiler error" no matter what you're trying to compile, it's a problem with the compiler.

Although having done a quick google for this I can't find a definitive statement. Anyone else know?