I emerged baselayout-1.11.3 (as part of emerge -uD world) and then did an etc-update. When I rebooted, I got : *Checking root Filesystem... [ok] Failed to open the device '/dev/hda5': No such file or directory *Filesystem couldn't be fixed :( [!!] Give root password for maintanence (or type Control-D for normal startup): I booted into FC2, chrooted to roll back to baselayout-1.10.4 and things were fine. Once back into Gentoo, I tried updating to 1.11.3 (thinking I messed up somewhere) but ended up with the same above mentioned error(s). # emerge info Portage 2.0.51-r2 (default-x86-2004.2, gcc-3.4.2, glibc-2.3.4.20041006-r0, 2.6.9-gentooy i686) ================================================================= System uname: 2.6.9-gentooy i686 Intel(R) Pentium(R) 4 CPU 2.60GHz Gentoo Base System version 1.5.3 ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.92.0.2-r1 Headers: sys-kernel/linux-headers-2.4.22 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium4 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache digest distlocks sandbox" GENTOO_MIRRORS="http://gentoo.mirrors.pair.com http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib acpi aim alsa apache2 apm arts audiofile avi berkdb bitmap-fonts bonobo bzlib cdr crypt cscope ctype cups curl directfb divx4linux docdvd encode esd ethereal evo exif f77 fbcon flac flash foomaticdb ftp gb gd gdbm ggi gif gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml icq imagemagick imap imlib innodb jabber java jpeg kde libg++ libwww mad man mbox memlimit mikmod mmap mmx motif mozilla mpeg mysql ncurses network nls odbc offensive oggvorbis opengl oscar oss pam pcre pdflib perl php png posix python qt quicktime readline recode samba sdl slang snmp sockets spell sse ssl svg svga sysvipc tcltk tcpd tetex tiff truetype unicode usb vhosts videos wmf x86 xinerama xml xml2 xmms xosd xprint xsl xv xvid yahoo zlib" Any other piece of info that maybe useful?
Same here. Had to rollback to 1.10.4.
Same problem here. For some reason, the fsck calls in /etc/init.d/checkroot and /etc/init.d/checkfsnow now fail. After entering sulogin, I found no hda entries in /dev, maybe that is the problem? emerge info: Portage 2.0.51-r2 (default-x86-2004.0, gcc-3.4.2, glibc-2.3.4.20041006-r0, 2.6.9-gentoo-r1 i686) ================================================================= System uname: 2.6.9-gentoo-r1 i686 Intel(R) Pentium(R) M processor 1500MHz Gentoo Base System version 1.5.3 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.92.0.2-r1 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-fforce-addr -march=pentium-m -mno-sse2 -Os -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-fforce-addr -march=pentium-m -mno-sse2 -Os -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks sandbox" GENTOO_MIRRORS="ftp://ftp.gentoo.skynet.be/pub/gentoo ftp://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://mirrors.sec.informatik.tu-darmstadt.de/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.be.gentoo.org/gentoo-portage" USE="X acpi alsa arts avi berkdb bindist bitmap-fonts cdr crypt cups dga dio directfb divx4linux dvd encode f77 fbcon foomaticdb gdbm gif gpm i8x0 imlib java jpeg junit kde libg++ libwww mad mikmod mmx motif mpeg msn ncurses nls oggvorbis opengl pam pcmcia pdflib perl png pnp ppdspython qt quicktime readline real samba sdl slang spell sse ssl svga tcltk tcpd theora tiff truetype unicode usb x86 xml2 xmms xprint xv xvid zlib video_cards_i830"
Yeah. /dev had no entries for hdx. I guess that's the only reason the fsck fails? Coz there is nothing to check as far as it can see...
do you guys all use udev ? what do you have RC_DEVICES set to in /etc/conf.d/rc ? if so, do you use the RC_DEVICE_TARBALL feature ?
I don't use udev. I don't seem to have RC_DEVICES in /etc/conf.d/rc but I do have RC_DEVICE_TARBALL set to yes.
umm, if you're using 1.11.x and you dont have RC_DEVICES in /etc/conf.d/rc, it sounds like you either didnt run `etc-update` or portage didnt merge all the config files correctly if `etc-update` doesnt show anything to update, try `emerge baselayout --noconfmem`
I'm using 1.10.4 now. You want me to retry with 1.11.3? PS : etc-update showed 26 files to update (after merging 1.11.3) & I'm pretty sure /etc/conf.d/rc wasn't one of them...maybe its not updating /etc/conf.d/rc as it should?
Created attachment 42557 [details] /etc/conf.d/rc /etc/conf.d/rc was actually updated while doing rc-update to this ...
Possible then that auto isn't doing its job? I have devfsd...
People using udev (/me use udev) say the solution is set RC_DEVICES="udev" instead of "auto"... Or maybe just a Device Tarball = yes ?
I have set RC_DEVICES to "devfsd" (i use dev fs) with no luck at all - system won't boot...
Same problem here. Happens with RC_DEVICES set to "auto", "devfs" and "udev". However if I replace /dev/hdaX in /etc/fstab with /dev/discs/disc0/partX, then everything is fine again. After the successful boot I again have /dev/hda*.
You need to edit /etc/fstab to use /dev/ide/host0/bus0/target0/lun0/partX instead of hdaX
By that you are just working around the problem of not created /dev nodes.
*** Bug 68826 has been marked as a duplicate of this bug. ***
sounds like the auto setup is selecting devfs instead of udev like it should when the system is booting, what do the init scripts say for setting up /dev ?
solution: /sbin/devfsd /dev in start section of etc/init.d/checkroot
/sbin/rc already runs devfsd: ebegin "Starting devfsd" /sbin/devfsd /dev > /dev/null eend $? "Could not start /sbin/devfsd" right after it mounts devfs on /dev: ebegin "Mounting devfs at /dev" try mount -n -t devfs none /dev eend $? so forcing it to run in checkroot may be one hack of a workaround but it isnt a solution
same here chrooted and falling back...
I use devfs and had this problem on reboot. I found that /sbin/rc checks if /dev/.devfsd exists to determine whether devfsd is already running but on my system it seems to be there before devfsd is started. I don't know where it is coming from though. devfs is compiled into the kernel (2.4.26).
ok, as Cubittus points out, the problem seems to be with people who use devfsd and have it compiled into their kernel to automount at boottime i'll test out that configuration and work with agriffis to release either a 1.11.3-r1 or 1.11.4
It's not just devsd users. I use udev here and had to drop back to 1.10.
everyone please post this info then: what do you normally use (udev/devfs) ? what do you have RC_DEVICES and RC_DEVICE_TARBALL set to ? during bootup, what do you see after 'Mounting proc at /proc' and before 'Activating (possible) swap' ? when you sulogin, what does /proc/mounts show ? there's probably multiple issues here, but the devfs one is due to /sbin/devfsd not being started when devfs is auto-mounted at boot
a quick look at /sbin/rc left me with the impression devfsd is only started when devfs isn't already mounted... can this be true? devfsd should also be started, when devfs is already mounted (imho)
As in this thread, I replaced /sbin/rc with an older version and everything seems to work. http://forums.gentoo.org/viewtopic.php?t=242001&postdays=0&postorder=asc&highlight=ext2&start=25 You might whan to fire diff; seems many changes regarding udev and fsdev have been made to /sbin/rc in this memorable update... ;-)
Really memorable update ;) Had me thinking that my hard disk was kaput as well lol
1.11.4 is in cvs with the auto-mounting devfsd fixes there's also a few other fixes, so if udev users still cant boot, open a new bug ... this one is for devfsd users
so get to it ...
dumb question, but if I can't boot, how can I get it?
Try chrooting from another Distro (like Knoppix) and roll back to 1.10.4...then get in & update.
Looks ok to me now. The only strange thing (but perhaps it's just a glitch in my configuration) is that when init writes out "Activating (possibly) more swap", it tries to mount my standard swap partition once more and logicaly outputs error "Device busy".
I get the same as well. Everything else is ok.
ive seen the swap warning on one of my boxes but none of the others ... oddly, it shouldnt happen, as `swapon -a` should fail silently as for booting, if you append 'devfs=nomount' at boot time, you should be able to boot fine with 1.11.3
But that would mean we would have to use udev - I am using devfs. ;)
umm, no ... devfs=nomount means dont automount devfs at boot time gentoo=nodevfs means dont use devfs, use udev instead
hmm - I see
*** Bug 69086 has been marked as a duplicate of this bug. ***
