Nano 512mb upgrade: filesystem full workaround



  • Hello list,
    I don't know if this has been discussed, maybe someone will find it useful.

    I just got a problem upgrading a pfsense 2.1 to one custom image I made. The issue is about upgrade size: official latest-nanobsd-512mb.img.gz is about 75M, mine is 85M.

    During the upgrade the image is placed in /root along with sha256 file.

    Here is a clean install mount layout

    
    [2.1-RELEASE][root@pfSense.localdomain]/root(1): df -h
    Filesystem           Size    Used   Avail Capacity  Mounted on
    /dev/ufs/pfsense0    215M    164M     33M    83%    /
    devfs                1.0k    1.0k      0B   100%    /dev
    /dev/ufs/cf           49M    743k     44M     2%    /cf
    /dev/md0              38M     56k     35M     0%    /tmp
    /dev/md1              57M     16M     36M    31%    /var
    devfs                1.0k    1.0k      0B   100%    /var/dhcpd/dev
    
    

    /root has only 33M available so the upgrade fails with a "filesystem full" message or "The command '/usr/bin/gzip -t '/root/latest.tgz'' returned exit code '1' "

    So I put in a USB stick (device da0) and mounted it on /root just for the upgrade:

    
    mount -t msdosfs -o large /dev/da0s1 /root
    
    

    The upgrade now completes successfully.
    After the reboot your /root is the same as always.



  • Information is very good information I do not know


Log in to reply