Bug 157036 – sys-kernel/gentoo-sources-2.6.19-r1 unable to mount root fs on boot

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Matthew Schultz 2006-12-03 17:48:01 UTC]

I'm getting this error message when attempting to boot of this kernel.  I used the same config options from the previous kernel so they should work.  My root file system is reiserfs. 

VFS: Cannot open root device "sda5" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

grub:

title  Gentoo 2.6.19-r1
root (hd0,0)
kernel /boot/kernel-2.6.19-gentoo-r1 root=/dev/sda5 vga=0x318 video=vesafb:mtrr:3,ywrap

fstab: 

# /etc/fstab: static file system information.
#
# 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.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# 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/sda1               /boot           ext3            noauto,noatime  1 2
/dev/sda5               /               reiserfs        notail,noatime  0 1
/dev/sda3               /var            reiserfs        notail,noatime  0 1
/dev/sda6               /home           xfs             noatime         0 1
/dev/sda2               none            swap            sw              0 0
/dev/cdroms/cdrom0      /mnt/cdrom      iso9660         noauto,ro       0 0
#/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


emerge --info:

Portage 2.1.1-r2 (default-linux/amd64/2006.1, gcc-4.1.1, glibc-2.4-r4, 2.6.18-gentoo-r3 x86_64)
=================================================================
System uname: 2.6.18-gentoo-r3 x86_64 Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz
Gentoo Base System version 1.12.6
Last Sync: Mon, 04 Dec 2006 00:00:02 +0000
app-admin/eselect-compiler: [Not Present]
dev-java/java-config: 1.3.7, 2.0.30
dev-lang/python:     2.4.3-r4
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     [Not Present]
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.60
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.16.1-r3
sys-devel/gcc-config: 1.3.13-r4
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=nocona -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo"
CXXFLAGS="-march=nocona -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks metadata-transfer parallel-fetch sandbox sfperms strict"
GENTOO_MIRRORS="http://gentoo.cites.uiuc.edu/pub/gentoo/ http://gentoo.mirrors.easynews.com/linux/gentoo/ http://mirror.phy.olemiss.edu/mirror/gentoo"
LINGUAS="en ru"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X a52 aac alsa apache2 audiofile avi bcmath bdf berkdb bitmap-fonts bzip2 calendar cdr cjk clamav cli cracklib crypt ctype cups curl curlwrappers dbus dio directfb dlloader dri dts dvb dvd dvdread elibc_glibc emu-linux-x86 encode exif fbcon ffmpeg flac fortran ftp gd gdbm gif gmp gpm gtk gtk2 hal hardenedphp hash iconv ieee1394 imagemagick imap imlib innodb input_devices_keyboard input_devices_mouse ipv6 isdnlog ithreads java javascript jpeg jpeg2k kde kernel_linux lcms ldap libg++ linguas_en linguas_ru lzo mad matroska mcal mhash mime mjpeg mng mp3 mp4 mpeg msession msn mysql mysqli ncurses network nls nptl nptlonly nsplugin nvidia ogg openal opengl osc oss pam pcntl pcre pdf pdo pear perl php png posix postgres ppds pppd python qt qt3 qt4 quicktime readline reflection samba sasl sdl seamonkey session simplexml snmp soap sockets spl sqlite ssl subversion svg tcpd theora threads tidy tiff tokenizer transcode truetype truetype-fonts type1-fonts udev unicode usb userland_GNU v4l v4l2 vcd video_cards_fbdev video_cards_nv video_cards_nvidia video_cards_v4l video_cards_vesa vorbis wddx wifi wxwindows x264 xine xml xorg xpm xv xvid zlib"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS

[Comment 1 Matthew Schultz 2006-12-03 17:49:19 UTC]

Created attachment 103296 [details]
Kernel 2.6.19-r1 config

[Comment 2 Jakub Moc (RETIRED) 2006-12-03 17:53:13 UTC]

> I used the same config options from the previous kernel so they should work.

NO! It really shouldn't. All the drivers options changed, never recycle .configs between different kernel versions.

[Comment 3 Matthew Schultz 2006-12-04 08:08:57 UTC]

Looks like you're right. I went through the long process of ticking everything from scratch without recycling the .config and it worked.  I guess I just got used to recycling old configs because I figured make menuconfig was smart and wouldn't write things that don't exist or aren't supported anymore. It's also easier to not have to retick everything everytime I upgrade the kernel and since it worked in the past, I never thought about it.