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

    How do I tell which Image I have installed?

    Scheduled Pinned Locked Moved 1.2.3-PRERELEASE-TESTING snapshots - RETIRED
    5 Posts 4 Posters 2.9k Views
    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
      avp
      last edited by

      Sorry for the stupid question…

      I forgot the size of the CF in my alix box, so I'm not sure what image to use for the upgrade to RC3...  I ran df and I believe it told me the size is 512Mb approx, so is this the size of one slice?  does this mean I need to use the 1gb image or the 512mb image.  Is there a cmd that can be run to display which version is being used?

      Thanks

      1 Reply Last reply Reply Quote 0
      • G
        gloomrider
        last edited by

        I think you're on the right track with "df". I'm running a 2GB image:

        
        router:~#  df -h
        Filesystem           Size    Used   Avail Capacity  Mounted on
        /dev/ufs/pfsense0    913M     79M    761M     9%    /
        devfs                1.0K    1.0K      0B   100%    /dev
        /dev/md0              38M    4.0K     35M     0%    /var/tmp
        /dev/md1              58M    5.0M     48M     9%    /var
        /dev/ufs/cf           49M    1.0M     44M     2%    /cf
        devfs                1.0K    1.0K      0B   100%    /var/dhcpd/dev
        
        

        Each slice is less than 1GB.  The "cf" partition rounds it out.  Don't forget the developers shrunk the slice sizes a little to accommodate slightly smaller CF cards.

        1 Reply Last reply Reply Quote 0
        • jimpJ
          jimp Rebel Alliance Developer Netgate
          last edited by

          On new snapshots you should also be able to do:

          cat /etc/nanosize.txt

          Though you can also figure it out with df, fdisk /dev/ad0, boot0cfg -v /dev/ad0, etc. As with many unix processes, there are multiple ways to get to the same conclusion.

          fdisk may be easiest though:

          alix:/etc#  fdisk /dev/ad0
          ******* Working on device /dev/ad0 *******
          parameters extracted from in-core disklabel are:
          cylinders=7964 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=7964 heads=16 sectors/track=63 (1008 blks/cyl)

          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 3861585 (1885 Meg), flag 80 (active)
                  beg: cyl 0/ head 1/ sector 1;
                  end: cyl 758/ head 15/ sector 63
          The data for partition 2 is:
          sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
              start 3861711, size 3861585 (1885 Meg), flag 0
                  beg: cyl 759/ head 1/ sector 1;
                  end: cyl 493/ head 15/ sector 63
          The data for partition 3 is:
          sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
              start 7723296, size 102816 (50 Meg), flag 0
                  beg: cyl 494/ head 0/ sector 1;
                  end: cyl 595/ head 15/ sector 63
          The data for partition 4 is:
          <unused>alix:/etc#

          Or if you want to get fancy:

          alix:/etc#  fdisk /dev/ad0 | grep Meg | cut -f2 -d'(' | cut -f1 -d' ' | awk '{s+=$1} END {print s}'
          3820

          So I have a 4GB image (3820MB)</unused>

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

          1 Reply Last reply Reply Quote 0
          • R
            rcpao
            last edited by

            Consider this a Request for Enhancement.  Please add the exact version including the image size in the System Overview page where the firmware version is displayed.  Another place to display the exact image name such as "pfSense-1.2.3-1g-20091011-1525-nanobsd.img.gz" would be in System: Firmware: Manual Update.  Thank you.

            pfSense 2.2.2 in ESXi with 5 static IPs via 4 CARP Virtual IPs on WAN to Pace 3801HGV (AT&T U-verse).

            1 Reply Last reply Reply Quote 0
            • jimpJ
              jimp Rebel Alliance Developer Netgate
              last edited by

              That information is not retained after updating, the filename doesn't really matter at that point.

              The NanoBSD size will already be displayed in the gui on newer snapshots under Diagnostics > NanoBSD.

              See:
              https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/c43ed2f92df169a80b81feb85d80223e9710ac5b

              I'll put it on my TODO list to add that to the dashboard system info as well.

              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

              Need help fast? Netgate Global Support!

              Do not Chat/PM for help!

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.