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

    If i enable Ram disks i have a "Unable to check for updates" message in dashboard

    Scheduled Pinned Locked Moved 2.3-RC Snapshot Feedback and Issues - ARCHIVED
    12 Posts 7 Posters 6.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.
    • Raul RamosR
      Raul Ramos
      last edited by

      If i enable Ram disks i have a "Unable to check for updates" message in dashboard information. If i disable it i have "Version 2.3.b.20160211.0929 is available. " this is on version built on Thu Feb 11 00:16:09 CST 2016.

      This Firewall are in hyper-V machine

      pfSense:
      ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
      Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
      NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

      1 Reply Last reply Reply Quote 0
      • F
        foonus
        last edited by

        Confirmed.

        1 Reply Last reply Reply Quote 0
        • K
          Keyser Soze
          last edited by

          I also had this problem when my RAM disk was enabled.

          When I turned off the RAM disk, it was then immediately able to check and perform the upgrade to latest RC (built on Thu Mar 31 23:48:37 CDT 2016 ).

          After rebooting it's back to complaining it is unable to check for updates with or without the RAM disk enabled.

          Before I enabled the RAM disk it was updating fine, I have been running the v2.3 beta for over a month updating regularly.

          1 Reply Last reply Reply Quote 0
          • P
            pLu
            last edited by

            I was running 2.2.6 with RAM disks when RC was released. Disabled RAM disks, rebooted, upgraded to 2.3 RC, enabled RAM disks again.

            Update works fine for me with RAM disks but I lost my old RRD data.

            1 Reply Last reply Reply Quote 0
            • M
              M_Devil
              last edited by

              Little offtopic, but with Ram-disk enabled system, pfSense did not come back after update to new snapshot. Error messages about read-only filesystem. Solved by reinstall of fresh pfSense installation.

              1 Reply Last reply Reply Quote 0
              • K
                Keyser Soze
                last edited by

                @pLu:

                I was running 2.2.6 with RAM disks when RC was released. Disabled RAM disks, rebooted, upgraded to 2.3 RC, enabled RAM disks again.

                I did not reboot immediately after disabling the RAM disk, and upgraded right afterwards because the option then became available.  :(

                1 Reply Last reply Reply Quote 0
                • C
                  cmb
                  last edited by

                  https://redmine.pfsense.org/issues/6068

                  1 Reply Last reply Reply Quote 0
                  • K
                    Keyser Soze
                    last edited by

                    @cmb:

                    https://redmine.pfsense.org/issues/6068

                    Thanks. I see this is already fixed, very nice.

                    How do we patch if already affected by this? Is there some way to force check/apply updates via the CLI?

                    1 Reply Last reply Reply Quote 0
                    • C
                      cmb
                      last edited by

                      If you just reboot, it should work post-reboot.

                      1 Reply Last reply Reply Quote 0
                      • K
                        Keyser Soze
                        last edited by

                        @cmb:

                        If you just reboot, it should work post-reboot.

                        I have rebooted many times, and the problem persists even without having the RAM disk set.

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

                          @Keyser:

                          I have rebooted many times, and the problem persists even without having the RAM disk set.

                          Had the same problem, the workaround from https://forum.pfsense.org/index.php?topic=107665.msg600840#msg600840 did fix it for me.
                          But I only executed:

                          /usr/sbin/pkg update -f
/usr/sbin/pkg install -yf pkg pfSense pfSense-kernel-pfSense pfSense-base pfSense-default-config
                          1 Reply Last reply Reply Quote 0
                          • K
                            Keyser Soze
                            last edited by

                            @grandslam:

                            Had the same problem, the workaround from https://forum.pfsense.org/index.php?topic=107665.msg600840#msg600840 did fix it for me

                            Thanks a lot for the link, your abbreviated version of the fix is what I used and it worked perfectly.

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