I have just performed a stage 1 install and found two related problems: 1. The /proc directory was not present at first boot, which prevented /proc from being mounted. It is there in the stage 1 tarball, so I have no idea where it went between untar and first boot. 2. More serious, the during bootup, this problem is not reported. Instead the computer simply hangs. In the /sbin/rc script is the line: try try mount -n -t proc none /proc If /proc does not exist, this line hangs, and does not output any error. Therefore it took me quite a while to realise what the problem was. This line should be fixed to output errors from the mount command. Reproducible: Always Steps to Reproduce:
Below is the code for try, which means you should (and I do here in testing) see an error message - any reason you would not see it ? -- try() { local errstr= local retval=0 # This works fine in test, but real life booting, fails for mounting /proc # if we only check $? for instance ... We thus need to [ -n "${errstr}" ] # as well. errstr="$((eval $*) 2>&1 >/dev/null)" retval=$? if [ "${retval}" -ne 0 ] || \ ([ "${*/mount/}" != "$*" -a -n "${errstr}" ]) then echo -e "${ENDCOL}${NORMAL}[${BAD} oops ${NORMAL}]" echo eerror "The \"${1}\" command failed with error:" echo echo "${errstr#*: }" echo eerror "Since this is a critical task, startup cannot continue." echo /sbin/sulogin ${CONSOLE} einfo "Unmounting filesystems" /bin/mount -a -o remount,ro & >/dev/null einfo "Rebooting" /sbin/reboot -f fi return ${retval} }
I can confirm that. It hangs with "mounting /proc" but no "Ok". I'm sure it is the "try try mount -n -t proc none /proc" line because I added a "echo debug" line directly after that into /sbin/rc. It did not show up without a /proc dir, but showed up after adding it by hand, resulting in successfull boot. Actually, this should be split into 2 bugs: 1) /proc gets lost somewhere in the install skripts. 2) we fail to detect the missing mount point on boot. I've not thought about the double "try", but it might eat the return code from the mount command. Bug 2) should be testable by "rmdir /mnt/gentoo/proc" from e.g. Knoppix and rebooting into Gentoo. There is justification to set an elevated priority for Bug 1).
*** Bug 36866 has been marked as a duplicate of this bug. ***
Problem also experienced with Gentoo-2004.0. See duplicate (http://bugs.gentoo.org/show_bug.cgi?id=36866)
I believe this was fixed in 2004.1 when I repaired the double-try stuff in /sbin/rc. Please reopen if the problem persists with current stages.
