Navigation

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

    Cannot update 2.3.2_1 i386 on 4GB nanoBSD

    Installation and Upgrades
    2
    2
    254
    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.
    • A
      archenroot last edited by

      Hi guys,

      I am trying to update:
      Current Base System 2.3.2_1
      Latest Base System 2.3.4_1

      Via web I get to point:

      [51/114] Fetching openvpn-client-export-2.4.4.txz: .......... done
      [52/114] Fetching nginx-1.12.1,2.txz: .......... done
      [53/114] Fetching dnsmasq-2.78,1.txz: .......... done
      [54/114] Fetching curl-7.54.1.txz: .......... done
      [55/114] Fetching clamav-0.99.2_3.txz: .......... done
      [56/114] Fetching c-icap-modules-0.4.5.txz: .......... done
      [57/114] Fetching bind-tools-9.11.1P1.txz: .......... done
      [58/114] Fetching openvpn23-2.3.17.txz: .......... done
      [59/114] Fetching libidn2-2.0.4.txz: .......... done
      [60/114] Fetching libunistring-0.9.7.txz: .......... done
      Checking integrity...
      
      

      Via command line I get something more:

      [38/114] Fetching php-suhosin-0.9.38_3.txz: ....... done
      [39/114] Fetching pfSense-rc-2.3.4_1.txz: . done
      [40/114] Fetching pfSense-pkg-squid-0.4.42.txz: ........ done
      [41/114] Fetching pfSense-pkg-openvpn-client-export-1.4.14.txz: ... done
      [42/114] Fetching pfSense-kernel-pfSense_wrap-2.3.4_1.txz: .......... done
      [43/114] Fetching pfSense-default-config-serial-2.3.4_1.txz: . done
      [44/114] Fetching pfSense-base-nanobsd-2.3.4_1.txz: .......... done
      [45/114] Fetching pfSense-Status_Monitoring-1.6.3.txz: ... done
      [46/114] Fetching pfSense-2.3.4_1.txz: . done
      [47/114] Fetching pecl-zmq-1.1.3_2.txz: ... done
      [48/114] Fetching pecl-ssh2-0.13.txz: ... done
      [49/114] Fetching pecl-rrd-1.1.3_4.txz: .. done
      [50/114] Fetching pecl-radius-1.4.0.b1.txz: ... done
      [51/114] Fetching openvpn-client-export-2.4.4.txz: .......... done
      [52/114] Fetching nginx-1.12.1,2.txz: .......... done
      [53/114] Fetching dnsmasq-2.78,1.txz: .......... done
      [54/114] Fetching curl-7.54.1.txz: .......... done
      [55/114] Fetching clamav-0.99.2_3.txz: .......... done
      [56/114] Fetching c-icap-modules-0.4.5.txz: .......... done
      [57/114] Fetching bind-tools-9.11.1P1.txz: .......... done
      [58/114] Fetching openvpn23-2.3.17.txz: .......... done
      [59/114] Fetching libidn2-2.0.4.txz: .......... done
      [60/114] Fetching libunistring-0.9.7.txz: .......... done
      Checking integrity...Child process pid=62714 terminated abnormally: Killed
      >>> Locking package pfSense-kernel-pfSense_wrap... 
      Locking pfSense-kernel-pfSense_wrap-2.3.2_1
      

      In the log file I found:

      # cat * |grep 62714
      Jan 21 14:32:44 blackhole kernel: pid 62714 (pkg-static), uid 0, was killed: out of swap space
      

      I have these mounts and space status:

      # mount
      /dev/ufs/pfsense0 on / (ufs, local, noatime, synchronous)
      devfs on /dev (devfs, local)
      /dev/ufs/cf on /cf (ufs, local, noatime, synchronous)
      /dev/md0 on /tmp (ufs, local)
      /dev/md1 on /var (ufs, local)
      devfs on /var/dhcpd/dev (devfs, local)
      # df -h
      Filesystem           Size    Used   Avail Capacity  Mounted on
      /dev/ufs/pfsense0    1.8G    682M    1.0G    40%    /
      devfs                1.0K    1.0K      0B   100%    /dev
      /dev/ufs/cf           49M    2.6M     43M     6%    /cf
      /dev/md0              38M    164K     35M     0%    /tmp
      /dev/md1              58M     19M     34M    35%    /var
      devfs                1.0K    1.0K      0B   100%    /var/dhcpd/dev
      
      

      It looks like I have 2GB size card:

      # fdisk
      ******* Working on device /dev/ufs/pfsense0 *******
      parameters extracted from in-core disklabel are:
      cylinders=3813 heads=16 sectors/track=63 (1008 blks/cyl)
      
      Figures below won't work with BIOS for partitions not in cyl 1
      parameters to be used for BIOS calculations are:
      cylinders=3813 heads=16 sectors/track=63 (1008 blks/cyl)
      
      fdisk: invalid fdisk partition table found
      Media sector size is 512
      Warning: BIOS sector numbering starts with sector 1
      Information from DOS bootblock is:
      The data for partition 1 is:
      sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
          start 63, size 3843441 (1876 Meg), flag 80 (active)
              beg: cyl 0/ head 1/ sector 1;
              end: cyl 740/ head 15/ sector 63
      The data for partition 2 is:
       <unused>The data for partition 3 is:
       <unused>The data for partition 4 is:</unused></unused> 
      

      So I am now not sure if this instance o f pfSense if upgradable. I will try to upgrade manually packages and see if later I can upgrade whole distro.

      I could imagine that it might be also good time to start upgrade to amd64 and some larger capacity hdd.. :-)

      1 Reply Last reply Reply Quote 0
      • Y
        yarick123 last edited by

        @archenroot:

        df -h

        Filesystem          Size    Used  Avail Capacity  Mounted on
        …
        /dev/md0              38M    164K    35M    0%    /tmp
        /dev/md1              58M    19M    34M    35%    /var
        ..

        you need more space in /var.

        Just go to System/Advanced/Miscellaneous: RAM Disk Settings (Reboot to Apply Changes), increase size of /var (I have set 800 MB), reboot the system and try to upgrade again. I have also increased size of /tmp to 60 MB.

        P.S. I have two firewalls. One of them could finally upgrade, the second could not upgrade the kernel and I had to reinstall the system.

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