Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Img files generated, but no iso

    Development
    2
    10
    3.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • E
      emery
      last edited by

      Hi folks,
      I tried a stock build on a FreeBSD 8.3 VM following the instructions more than a few times now. However, I haven't been able to generate ISO files, only 'img.gz' files are produced (which is fine). Then, I tried booting from these IMG file that I flashed onto a USB stick using 'gzip/dd combo', and that didn't work either (no /boot/loader or /boot/kernel/kernel). The build log contains some errors such as:

      
cp: /usr/local/pfsense-clone/lib/libthr.so.3: No such file or directory
cp: /usr/local/pfsense-clone/lib/libc.so.7: No such file or directory
cp: /usr/local/pfsense-clone/usr/lib/libwrap.so.6: No such file or directory
cp: /usr/local/pfsense-clone/usr/lib/libpam.so.5: No such file or directory
cp: /usr/local/pfsense-clone/lib/libcrypt.so.5: No such file or directory
cp: /usr/local/pfsense-clone/lib/libutil.so.8: No such file or directory

      that I can't quite explain. The files are there. Then, there are 'filesystem full' messages that are indicated to be normal:

      
mount of /usr/local/pfsense-clone/usr
Done!
>>> Using TAR to clone...
>>> Deleting files listed in /usr/home/pfsense/tools/builder_scripts/conf/rmlist/remove.list.iso.8
>>> Filling the uncompressed fs with zeros to compress better
>>> Don't worry if you see a 'filesystem full' message here
umount: unmount of /usr/local/pfsense-clone/usr failed: Device busy
*** Error code 1

      When everything is said and done, the process ends normally:

      
Stop in /usr/home/pfsense/freesbie2.
>>> Finalizing iso...
>>> Creating memstick...
>>> Creating serial memstick...
>>> /tmp/pfSense/ now contains:
total 146440
drwxr-xr-x   2 root  wheel   512B Aug 21 14:16 .
drwxrwxrwt  19 root  wheel   4.5k Aug 21 14:15 ..
-rw-r--r--   1 root  wheel    71M Aug 21 14:16 pfSense-memstick-2.1-DEVELOPMENT-amd64-20130821-1354.img.gz
-rw-r--r--   1 root  wheel    71M Aug 21 14:16 pfSense-memstick-serial-2.1-DEVELOPMENT-amd64-20130821-1354.img.gz
>>> Operation ./build_iso.sh has ended at Wed Aug 21 14:16:52 EDT 2013

      Clearly, I am not getting it. I've attached the build log, and at this point I am looking for any ideas.

      Thanks a lot.
      build_log.txt

      1 Reply Last reply Reply Quote 0
      • Z
        zenny
        last edited by

        Did you notice  from line 168 till 724 in your build.log that the required binaries are missing?

        I suggest you to run ./build_pfPorts.sh before running ./build_iso.sh. This may create iso image if your pfsense-build.conf is correctly configured.

        1 Reply Last reply Reply Quote 0
        • E
          emery
          last edited by

          Thanks for the reply. Yes, I saw that those shared libraries were reported missing by the script, but they were all under corresponding directories (/usr/local/pfsense-clone/lib & /usr/local/pfsense-clone/usr/lib) when I built. Instead of './menu.sh', I also tried './build_pfPorts.sh' followed by './build_iso.sh' with the same result. I haven't modified the 'pfsense-build.conf' file (attached). I wish I could just mkisofs from the build directories, but I haven't been able to run the script 'launch.sh' for iso properly under freesbie directory…

          pfsense-build.conf.txt

          1 Reply Last reply Reply Quote 0
          • Z
            zenny
            last edited by

            In your pfsense-build.conf, can you make changes like as follows and check again:

            export BASE_DIR=/home/pfsense
            export BUILDER_TOOLS=/home/pfsense/tools
            export BUILDER_SCRIPTS=/home/pfsense/tools/builder_scripts

            from line 12 and 13 and rebuild? Just a wild guess.

            1 Reply Last reply Reply Quote 0
            • Z
              zenny
              last edited by

              I confirm that the iso is not built with the same configuaration which was working earlier. I got the following, but no iso (though I do not need an iso):

              Compressing /usr/local/pfsense-clone/uzip/usr.ufs… 71.1097% saved
              Finalizing iso...
              Creating memstick...
              Creating serial memstick...
              /tmp/pfSense/ now contains:
              total 185316
              drwxr-xr-x  2 root  wheel  512B Aug 22 21:02 .
              drwxrwxrwt  11 root  wheel  1.0k Aug 22 21:01 ..
              -rw-r--r--  1 root  wheel    90M Aug 22 21:02 pfSense-memstick-2.1-RC0-amd64-20130822-1924.img.gz
              -rw-r--r--  1 root  wheel    90M Aug 22 21:02 pfSense-memstick-serial-2.1-RC0-amd64-20130822-1924.img.gz
              Operation ./build_iso.sh has ended at Thu Aug 22 21:02:35 CEST 2013

              1 Reply Last reply Reply Quote 0
              • E
                emery
                last edited by

                I actually tried again on a fresh BSD VM this afternoon with the same result. I'll try your  suggestions about the config file. If you think this is a pfsense-build.conf issue, would you be able to post a version of your file that generates an ISO? Normally, I wouldn't mind if the iso file is generated or not, as long as I was able to boot from those generated img.gz files. But my trouble is when I try booting with one of those images flashed on a USB drive, I get "No /boot/loader" and "No /boot/kernel/kernel" messages. Just curious if you tried booting from your img.gz files and whether it succeeds…

                Thanks again.

                1 Reply Last reply Reply Quote 0
                • E
                  emery
                  last edited by

                  Apologies, no need to post your config file, I just saw a version of the pfsens-build.conf file in your other thread http://forum.pfsense.org/index.php/topic,61074.0.html. Will try again…

                  1 Reply Last reply Reply Quote 0
                  • Z
                    zenny
                    last edited by

                    @emery:

                    Apologies, no need to post your config file, I just saw a version of the pfsens-build.conf file in your other thread http://forum.pfsense.org/index.php/topic,61074.0.html. Will try again…

                    None of my isos are bootable and ends with kernel panic, because I tried to add some kernel options like vimage, epair, if_bridge and without sctp. They do seem inherently unsupported in pfSense 2.1, so Jim stated in one of the thread that they might have been left by developers as they could not make it go with those kernel options (http://forum.pfsense.org/index.php/topic,61074.msg355329.html#msg355329).

                    I have been struggling still to run haproxy in jail with it's own virtual ethernet. ;-)

                    1 Reply Last reply Reply Quote 0
                    • E
                      emery
                      last edited by

                      Sorry, I can't be of much use with either kernel panic or haproxy :( However, I have resolved my issue with no ISO files. It turned out that the GNOME desktop (in particular gvfsd-trash applet) was the culprit. The MD device that gets created during FS cloning couldn't be unmounted because of gvfsd-trash. And that broke the subsequent 'freesbie_make iso' command in the script. When I stopped GDM, and repeated the process at console, the LiveCD ISO , which I was able to boot from, was generated. Yay!

                      1 Reply Last reply Reply Quote 0
                      • Z
                        zenny
                        last edited by

                        Since I do not use any display managers like gdm/kdm/xdm etc., that is not in my case. I directly boot into xserver using startx command. No display managers are active. I use i3 as desktop environment (i3-wm.org) with free OSes, fyi.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post