A friend of mine is attempting to use Dialog installer to networklessly install Gentoo -- we have previously created partitions, and selected them for use in the Dialog installer, and the rest of the installation goes smoothly until the progressbar hits 100%, sometimes higher (she's seen 115%), and then crashes with: No such file or directory: '/tmp/spawn_exitcode' Reproducible: Always Steps to Reproduce: 1. Start installing gentoo with Dialog installer. 2. (not sure if it makes a difference) select pre-configured partitions for install. filesystems may already be made on them. 3. continue install normally. Actual Results: The progress bar reaches 100%, sometimes higher. Crashes with error "No such file or directory: '/tmp/spawn_exitcode'". doesn't install the bootloader. Expected Results: Install correctly. I do not have direct access to this machine, only by communication with its owner. We are willing to perform any further diagnostics needed to resolve this. This is, by definition, a blocker -- we cannot continue past this point.
Here are two pictures of this and another error she has received while installing: First attempt: http://turbogfx.homelinux.org/imgfiles/9-15-07_065.jpg This happened after a second attempt yesterday: http://turbogfx.homelinux.org/imgfiles/9-15-07_067.jpg (ignore the white horizontal line.. bad pixels) This second error leads me to believe that it ran out of RAM for tmpfs or something similar. None of the partitions we are installing to were even close to filled (confirmed with parted magic livecd)
The 2nd screenshot shows the error pretty clearly: "No space left on device". This isn't our problem.
Please read my note along with the images... None of the partitions we are installing to were even close to filled (confirmed with parted magic livecd)
reopening (hit wrong radio button from last comment)
The most likely explanation for this is that she never *mounted* the partitions after creating them. This is a separate step now as opposed to previous versions of the installer. If it doesn't mount / correctly, then the tarball will extract into the tmpfs and fill up all the space and you will crash with the error shown. Please check that the partitions are mounted. If you can look at /var/log/installer.log you may find an error message related to mounting the partition. If so, please post it.
This may indeed be what happened -- In my own tests with a testing box, if no partitions other than swap (which is already defined by default) are given a mountpoint, then eventually this error will come up as you described (df shows tmpfs 100% used and no /mnt/gentoo[/*] mounted). Should there not be a method in place to prevent the installer from continuing if no partition is defined as the root mountpoint? While I now know how this bug is occuring and how to fix it, I think it would be advantageous to leave this bug open until a mechanism that prevents continuing without a root mountpoint is in place. Unless there is already a bug open for that... A quick search did not reveal one.
This is definitely not a blocker.
This has been fixed in SVN.
