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

    Something went wrong when trying to update the fstab entry. Aborting upgrade

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    4 Posts 3 Posters 3.6k 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.
    • F
      FooFighter
      last edited by

      system: Alix box with latest firmware

      (slice ad0s1 is currently running)
      1.2.3-RC3
      built on Mon Oct 5 23:56:45 UTC 2009
      FreeBSD 7.2-RELEASE-p4 i386

      I tried to update to this release:
      pfSense-1.2.3-RC3-512mb-nanobsd-upgrade.img.gz - 2009-Nov-05 16:02:33 36.6M

      (systemlog)
      Nov  5 18:33:00 pfsense php: : New alert found: Something went wrong when trying to update the fstab entry.  Aborting upgrade.

      (updatelog)
      Misc log:

      mkdir: /tmp/pfsense1: File exists
      mount: /dev/ufs/pfsense1 : Operation not permitted
      cp: /tmp/pfsense1/etc/fstab: No such file or directory
      sed: /tmp/pfsense1/etc/fstab: No such file or directory
      umount: /tmp/pfsense1: not a file system root directory

      fdisk/bsdlabel log:

      (shell)
      pfsense:/dev#  mount
      /dev/ufs/pfsense1 on / (ufs, local, read-only)
      devfs on /dev (devfs, local)
      /dev/md0 on /var/tmp (ufs, local)
      /dev/md1 on /var (ufs, local)
      /dev/ufs/cf on /cf (ufs, local, read-only)
      devfs on /var/dhcpd/dev (devfs, local)

      Is there a solution besides unscrewing my alix and manually flashing my CF?

      best regards,

      Foo

      1 Reply Last reply Reply Quote 0
      • B
        brasilnut
        last edited by

        ???

        Did anyone ever reply. Am having same here…
        2Gig CF card here...

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

          nope, no feedback so far  :'(

          as the copy process before this error seems to be ok, a manual guide for the last few steps in the shell would help me out.

          Regards,

          Foo

          1 Reply Last reply Reply Quote 0
          • S
            sullrich
            last edited by

            October is pretty old, unfortunately.  NanoBSD was a moving target up until a brief bit ago.

            In these cases you will have to reflash.

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