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

    SG-1100 update from 23.09.1 to 24.03 keeps failing

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    79 Posts 8 Posters 7.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.
    • T
      terryzb @mrneutron
      last edited by

      @mrneutron

      Have a look at System->Advanced->Miscellaneous->RAM Disk Settings

      https://docs.netgate.com/pfsense/en/latest/config/advanced-misc.html#ram-disk-settings

      M 1 Reply Last reply Reply Quote 0
      • M
        mrneutron @terryzb
        last edited by

        @terryzb said in SG-1100 update from 23.09.1 to 24.03 keeps failing:

        @mrneutron

        Have a look at System->Advanced->Miscellaneous->RAM Disk Settings

        https://docs.netgate.com/pfsense/en/latest/config/advanced-misc.html#ram-disk-settings

        @terryzb
        Thanks! I'll check and see if my SG-1100 has that enabled.

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Indeed there is checkbox to turn it on. But perhaps a further question might be whether it should be enabled by default in some configurations. It does restrict what you can use. And it obviously uses RAM which is important on the 1100 which only has 1GB.

          One potential option here is that the new Net Installer will install to any available drive including USB. It's possible to install to a USB drive and boot from that.
          It does require manually changing the bootcmd env in uboot though.

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

            Here's the log from the failed Online Network Installer attempt.
            I can't see any big clues as to the failed partitioning.

            root@pfSense-install:~ # cd /tmp
            root@pfSense-install:/tmp # ls
            .ICE-unix               .font-unix              bsdinstall_etc          recovered_config
            .X11-unix               bsdinstall-tmp-fstab    bsdinstall_log          tmp.zf1blw5xTi
            .XIM-unix               bsdinstall_boot         mnt_recovery
            root@pfSense-install:/tmp # cat bsdinstall_log
            DEBUG: Running installation step: auto
            DEBUG: dialog.subr: DEBUG_SELF_INITIALIZE=[]
            DEBUG: UNAME_S=[FreeBSD] UNAME_P=[aarch64] UNAME_R=[15.0-CURRENT]
            DEBUG: common.subr: Successfully loaded.
            DEBUG: f_include: file=[/usr/share/bsdconfig/dialog.subr]
            DEBUG: dialog.subr: loading includes...
            DEBUG: f_include: file=[/usr/share/bsdconfig/strings.subr]
            DEBUG: strings.subr: Successfully loaded.
            DEBUG: f_include: file=[/usr/share/bsdconfig/variable.subr]
            DEBUG: variable.subr: loading includes...
            DEBUG: f_include: file=[/usr/share/bsdconfig/dialog.subr]
            DEBUG: f_include: file=[/usr/share/bsdconfig/strings.subr]
            DEBUG: variable.subr: New variable VAR_CONFIG_FILE -> configFile
            DEBUG: variable.subr: New variable VAR_DEBUG -> debug
            DEBUG: variable.subr: New variable VAR_DEBUG_FILE -> debugFile
            DEBUG: variable.subr: New variable VAR_DIRECTORY_PATH -> _directoryPath
            DEBUG: variable.subr: New variable VAR_DOMAINNAME -> domainname
            DEBUG: variable.subr: New variable VAR_EDITOR -> editor
            DEBUG: variable.subr: New variable VAR_EXTRAS -> ifconfig_
            DEBUG: variable.subr: New variable VAR_GATEWAY -> defaultrouter
            DEBUG: variable.subr: New variable VAR_GROUP -> group
            DEBUG: variable.subr: New variable VAR_GROUP_GID -> groupGid
            DEBUG: variable.subr: New variable VAR_GROUP_MEMBERS -> groupMembers
            DEBUG: variable.subr: New variable VAR_GROUP_PASSWORD -> groupPassword
            DEBUG: variable.subr: New variable VAR_HOSTNAME -> hostname
            DEBUG: variable.subr: New variable VAR_HTTP_DIR -> httpDirectory
            DEBUG: variable.subr: New variable VAR_HTTP_FTP_MODE -> httpFtpMode
            DEBUG: variable.subr: New variable VAR_HTTP_HOST -> httpHost
            DEBUG: variable.subr: New variable VAR_HTTP_PATH -> _httpPath
            DEBUG: variable.subr: New variable VAR_HTTP_PORT -> httpPort
            DEBUG: variable.subr: New variable VAR_HTTP_PROXY -> httpProxy
            DEBUG: variable.subr: New variable VAR_HTTP_PROXY_HOST -> httpProxyHost
            DEBUG: variable.subr: New variable VAR_HTTP_PROXY_PATH -> _httpProxyPath
            DEBUG: variable.subr: New variable VAR_HTTP_PROXY_PORT -> httpProxyPort
            DEBUG: variable.subr: New variable VAR_IFCONFIG -> ifconfig_
            DEBUG: variable.subr: New variable VAR_IPADDR -> ipaddr
            DEBUG: variable.subr: New variable VAR_IPV6ADDR -> ipv6addr
            DEBUG: variable.subr: New variable VAR_IPV6_ENABLE -> ipv6_activate_all_interfaces
            DEBUG: variable.subr: New variable VAR_KEYMAP -> keymap
            DEBUG: variable.subr: New variable VAR_MEDIA_TIMEOUT -> MEDIA_TIMEOUT
            DEBUG: variable.subr: New variable VAR_MEDIA_TYPE -> mediaType
            DEBUG: variable.subr: New variable VAR_NAMESERVER -> nameserver
            DEBUG: variable.subr: New variable VAR_NETINTERACTIVE -> netInteractive
            DEBUG: variable.subr: New variable VAR_NETMASK -> netmask
            DEBUG: variable.subr: New variable VAR_NETWORK_DEVICE -> netDev
            DEBUG: variable.subr: New variable VAR_NFS_HOST -> nfsHost
            DEBUG: variable.subr: New variable VAR_NFS_PATH -> nfsPath
            DEBUG: variable.subr: New variable VAR_NFS_SECURE -> nfs_reserved_port_only
            DEBUG: variable.subr: New variable VAR_NFS_TCP -> nfs_use_tcp
            DEBUG: variable.subr: New variable VAR_NFS_V3 -> nfs_use_v3
            DEBUG: variable.subr: New variable VAR_NONINTERACTIVE -> nonInteractive
            DEBUG: variable.subr: New variable VAR_NO_CONFIRM -> noConfirm
            DEBUG: variable.subr: New variable VAR_NO_ERROR -> noError
            DEBUG: variable.subr: New variable VAR_NO_INET6 -> noInet6
            DEBUG: variable.subr: New variable VAR_PACKAGE -> package
            DEBUG: variable.subr: New variable VAR_PKG_TMPDIR -> PKG_TMPDIR
            DEBUG: variable.subr: New variable VAR_PORTS_PATH -> ports
            DEBUG: variable.subr: New variable VAR_RELNAME -> releaseName
            DEBUG: variable.subr: New variable VAR_SLOW_ETHER -> slowEthernetCard
            DEBUG: variable.subr: New variable VAR_TRY_DHCP -> tryDHCP
            DEBUG: variable.subr: New variable VAR_TRY_RTSOL -> tryRTSOL
            DEBUG: variable.subr: New variable VAR_UFS_PATH -> ufs
            DEBUG: variable.subr: New variable VAR_USER -> user
            DEBUG: variable.subr: New variable VAR_USER_ACCOUNT_EXPIRE -> userAccountExpire
            DEBUG: variable.subr: New variable VAR_USER_DOTFILES_CREATE -> userDotfilesCreate
            DEBUG: variable.subr: New variable VAR_USER_GECOS -> userGecos
            DEBUG: variable.subr: New variable VAR_USER_GID -> userGid
            DEBUG: variable.subr: New variable VAR_USER_GROUPS -> userGroups
            DEBUG: variable.subr: New variable VAR_USER_GROUP_DELETE -> userGroupDelete
            DEBUG: variable.subr: New variable VAR_USER_HOME -> userHome
            DEBUG: variable.subr: New variable VAR_USER_HOME_CREATE -> userHomeCreate
            DEBUG: variable.subr: New variable VAR_USER_HOME_DELETE -> userHomeDelete
            DEBUG: variable.subr: New variable VAR_USER_LOGIN_CLASS -> userLoginClass
            DEBUG: variable.subr: New variable VAR_USER_PASSWORD -> userPassword
            DEBUG: variable.subr: New variable VAR_USER_PASSWORD_EXPIRE -> userPasswordExpire
            DEBUG: variable.subr: New variable VAR_USER_SHELL -> userShell
            DEBUG: variable.subr: New variable VAR_USER_UID -> userUid
            DEBUG: variable.subr: New variable VAR_ZFSINTERACTIVE -> zfsInteractive
            DEBUG: variable.subr: VARIABLE_SELF_INITIALIZE=[1]
            DEBUG: f_variable_set_defaults: Initializing defaults...
            DEBUG: f_getvar: var=[debug] value=[1] r=0
            DEBUG: f_getvar: var=[editor] value=[/usr/bin/ee] r=0
            DEBUG: f_getvar: var=[hostname] value=[pfSense-install] r=0
            DEBUG: f_getvar: var=[MEDIA_TIMEOUT] value=[300] r=0
            DEBUG: f_getvar: var=[nfs_reserved_port_only] value=[NO] r=0
            DEBUG: f_getvar: var=[nfs_use_tcp] value=[NO] r=0
            DEBUG: f_getvar: var=[nfs_use_v3] value=[YES] r=0
            DEBUG: f_getvar: var=[PKG_TMPDIR] value=[/var/tmp] r=0
            DEBUG: f_getvar: var=[releaseName] value=[15.0-CURRENT] r=0
            DEBUG: f_variable_set_defaults: Defaults initialized.
            DEBUG: variable.subr: Successfully loaded.
            DEBUG: f_include_lang: file=[/usr/libexec/bsdconfig/include/messages.subr] lang=[C.UTF-8]
            DEBUG: dialog.subr: DIALOG_SELF_INITIALIZE=[1]
            DEBUG: f_dialog_init: ARGV=[] GETOPTS_STDARGS=[dD:SX]
            DEBUG: f_dialog_init: SECURE=[] USE_XDIALOG=[]
            DEBUG: f_dialog_init: dialog(1) API initialized.
            DEBUG: dialog.subr: Successfully loaded.
            DEBUG: Began Installation at Tue Mar 12 07:19:10 UTC 2024
            DEBUG: dialog.subr: DEBUG_SELF_INITIALIZE=[]
            DEBUG: UNAME_S=[FreeBSD] UNAME_P=[aarch64] UNAME_R=[15.0-CURRENT]
            DEBUG: common.subr: Successfully loaded.
            DEBUG: f_debug_init: ARGV=[pfSense-config-restore] GETOPTS_STDARGS=[dD:]
            DEBUG: f_debug_init: debug=[1] debugFile=[/tmp/bsdinstall_log]
            DEBUG: Running installation step: pfSense-config-restore
            DEBUG: dialog.subr: DEBUG_SELF_INITIALIZE=[]
            DEBUG: UNAME_S=[FreeBSD] UNAME_P=[aarch64] UNAME_R=[15.0-CURRENT]
            DEBUG: common.subr: Successfully loaded.
            DEBUG: f_debug_init: ARGV=[pfSense-netconfig] GETOPTS_STDARGS=[dD:]
            DEBUG: f_debug_init: debug=[1] debugFile=[/tmp/bsdinstall_log]
            DEBUG: Running installation step: pfSense-netconfig
            DEBUG: dialog.subr: DEBUG_SELF_INITIALIZE=[]
            DEBUG: UNAME_S=[FreeBSD] UNAME_P=[aarch64] UNAME_R=[15.0-CURRENT]
            DEBUG: common.subr: Successfully loaded.
            DEBUG: f_debug_init: ARGV=[pfSense-sysinfo] GETOPTS_STDARGS=[dD:]
            DEBUG: f_debug_init: debug=[1] debugFile=[/tmp/bsdinstall_log]
            DEBUG: Running installation step: pfSense-sysinfo
            DEBUG: f_getvar: var=[nonInteractive] value=[] r=1
            DEBUG: smbios.system.maker=[Marvell]
            DEBUG: smbios.system.product=[mvebu_armada-37xx]
            DEBUG: smbios.system.version=[]
            DEBUG: smbios.planar.maker=[Marvell]
            DEBUG: smbios.planar.product=[mvebu_armada-37xx]
            DEBUG: dialog.subr: DEBUG_SELF_INITIALIZE=[]
            DEBUG: UNAME_S=[FreeBSD] UNAME_P=[aarch64] UNAME_R=[15.0-CURRENT]
            DEBUG: common.subr: Successfully loaded.
            DEBUG: f_debug_init: ARGV=[pfSense-disk-part] GETOPTS_STDARGS=[dD:]
            DEBUG: f_debug_init: debug=[1] debugFile=[/tmp/bsdinstall_log]
            DEBUG: Running installation step: pfSense-disk-part
            DEBUG: dialog.subr: DEBUG_SELF_INITIALIZE=[]
            DEBUG: UNAME_S=[FreeBSD] UNAME_P=[aarch64] UNAME_R=[15.0-CURRENT]
            DEBUG: common.subr: Successfully loaded.
            DEBUG: f_debug_init: ARGV=[umount] GETOPTS_STDARGS=[dD:]
            DEBUG: f_debug_init: debug=[1] debugFile=[/tmp/bsdinstall_log]
            DEBUG: Running installation step: umount
            DEBUG: f_dialog_max_size: bsddialog --print-maxsize = [MaxSize: 53, 121]
            DEBUG: f_getvar: var=[height] value=[8] r=0
            DEBUG: f_getvar: var=[width] value=[57] r=0
            root@pfSense-install:/tmp #
            
            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              Does it not create the install-log.txt file then?

              M 1 Reply Last reply Reply Quote 0
              • M
                mrneutron @stephenw10
                last edited by

                @stephenw10 said in SG-1100 update from 23.09.1 to 24.03 keeps failing:

                Does it not create the install-log.txt file then?

                I entered the ls command for the /tmp directory so we could see the contents.
                There is no install-log.txt file.
                Maybe that can give an indication of where in the upgrade process it all stopped?

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  Yes, exactly it fails before it starts installing which makes sense since it appears to be while trying to partition the disk.

                  Ok so to boot the installer I assume you are running run usbrecovery at the marvell>> prompt? That should erase the eMMC but may fail to do so if the eMMC cannot be written.
                  You can confirm that by the number disks uboot reports at boot. It should show 5 disks if the eMMC has been correctly wiped:

                  USB1:   USB EHCI 1.00
                  scanning bus 0 for devices... 1 USB Device(s) found
                  scanning bus 1 for devices... 2 USB Device(s) found
                         scanning usb for storage devices... 1 Storage Device(s) found
                      18022   armada-3720-netgate-1100.dtb
                      18022   armada-3720-sg1100.dtb
                      12944   armada-3720-netgate-2100.dtb
                      12944   armada-3720-sg2100.dtb
                  
                  4 file(s), 0 dir(s)
                  
                  845140 bytes read in 53 ms (15.2 MiB/s)
                  18022 bytes read in 22 ms (799.8 KiB/s)
                  ## Starting EFI application at 07000000 ...
                  Card did not respond to voltage select!
                  Scanning disk sdhci@d0000.blk...
                  Disk sdhci@d0000.blk not ready
                  Scanning disk sdhci@d8000.blk...
                  Scanning disk usb_mass_storage.lun0...
                  Found 5 disks
                  

                  If it shows 8 disks there after appearing to wipe the eMMC then it's likely become read-only.

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    mrneutron @stephenw10
                    last edited by mrneutron

                    @stephenw10 said in SG-1100 update from 23.09.1 to 24.03 keeps failing:

                    Yes, exactly it fails before it starts installing which makes sense since it appears to be while trying to partition the disk.

                    Ok so to boot the installer I assume you are running run usbrecovery at the marvell>> prompt? That should erase the eMMC but may fail to do so if the eMMC cannot be written.

                    Yes, I'm running run usbrecovery at the marvell>> prompt.

                    You can confirm that by the number disks uboot reports at boot. It should show 5 disks if the eMMC has been correctly wiped:
                    If it shows 8 disks there after appearing to wipe the eMMC then it's likely become read-only.

                    I do recall seeing 8 disks in the serial text that flew by.

                    I turned on the RAMDISK last night.
                    I am seeing files (such as log files) being written with today's date/time.
                    I believe the /var/log directory is in the RAMDISK, so I guess that may explain why there are current log files being written today.

                    I guess I should turn off the RAMDISK again and see if new log file updates are possible?

                    [23.09.1-RELEASE][admin@tonka-gw1.duckdns.org]/var/log: ls -al | grep "May"
                    drwxr-xr-x   4 root wheel     59 May  9 09:50 .
                    -rw-------   1 root wheel 433505 May  9 10:06 auth.log
                    -rw-------   1 root wheel 337722 May  9 10:03 dhcpd.log
                    -rw-------   1 root wheel 512741 May  8 20:23 dhcpd.log.0
                    -rw-------   1 root wheel 243470 May  9 10:07 filter.log
                    -rw-------   1 root wheel 520284 May  9 09:50 filter.log.0
                    -rw-------   1 root wheel 521295 May  9 09:13 filter.log.1
                    -rw-------   1 root wheel 530007 May  9 08:36 filter.log.2
                    -rw-------   1 root wheel 523821 May  9 07:58 filter.log.3
                    -rw-------   1 root wheel 512765 May  9 07:20 filter.log.4
                    -rw-------   1 root wheel 515820 May  9 06:43 filter.log.5
                    -rw-------   1 root wheel 519551 May  9 06:06 filter.log.6
                    -rw-------   1 root wheel 208469 May  8 21:12 nginx.log
                    -rw-------   1 root wheel 177758 May  8 20:10 ntpd.log
                    -rw-------   1 root wheel  66845 May  9 10:06 openvpn.log
                    -rw-------   1 root wheel 512236 May  9 08:57 openvpn.log.0
                    -rw-------   1 root wheel 511737 May  8 23:55 openvpn.log.1
                    -rw-------   1 root wheel  23252 May  8 19:48 resolver.log
                    -rw-------   1 root wheel    970 May  9 10:05 system.log
                    -rw-------   1 root wheel 511106 May  9 07:21 system.log.0
                    -rw-r--r--   1 root wheel    394 May  9 10:05 utx.lastlogin
                    -rw-------   1 root wheel   2037 May  9 10:05 utx.log
                    
                    1 Reply Last reply Reply Quote 0
                    • stephenw10S
                      stephenw10 Netgate Administrator
                      last edited by

                      Hmm, perhaps only the partition table area then. Interesting, I don't think we've seen that before.

                      If you can confirm that it still shows 8 disks after erasing the emmc though something is not allowing that.

                      Or if you run usbrecovery without a USB drive present and then then reset and it still boots from emmc.

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        mrneutron @stephenw10
                        last edited by mrneutron

                        @stephenw10 said in SG-1100 update from 23.09.1 to 24.03 keeps failing:

                        Hmm, perhaps only the partition table area then. Interesting, I don't think we've seen that before.

                        If you can confirm that it still shows 8 disks after erasing the emmc though something is not allowing that.

                        Or if you run usbrecovery without a USB drive present and then then reset and it still boots from emmc.

                        I just revised my previous message regarding the log files, because I turned on the RAMDISK last night and I just realized that could confuse the diagnosis.

                        I will try the update again and capture as much of the serial data as I can, so I can have a snapshot of what messages are going by.

                        1 Reply Last reply Reply Quote 1
                        • M
                          mrneutron
                          last edited by mrneutron

                          I looked at the RAMDISK settings and they were off?!
                          I guess my turn-on of the RAMDISK didn't take effect, even though I did restart, as advised by the pop-up message.

                          I just clicked the RAMDISK box to ON and then OFF and then rebooted to be sure the RAMDISK was off.

                          It shows it's off and the /var/log still has entries being written during the last 5 minutes.
                          RAMDISK settings off 5-9-2024 12pm.jpg

                          [23.09.1-RELEASE][admin@redacted]/var/log: ls -la | grep "May"
                          drwxr-xr-x   4 root wheel     56 May  9 11:41 .
                          -rw-------   1 root wheel 400581 May  9 12:05 auth.log
                          -rw-------   1 root wheel 256298 May  9 12:06 dhcpd.log
                          -rw-------   1 root wheel 500703 May  9 12:06 filter.log
                          -rw-------   1 root wheel 549513 May  9 11:41 filter.log.0
                          -rw-------   1 root wheel 195573 May  9 12:03 nginx.log
                          -rw-------   1 root wheel 177772 May  9 11:57 ntpd.log
                          -rw-------   1 root wheel 295779 May  9 12:05 openvpn.log
                          -rw-------   1 root wheel  41370 May  9 11:40 resolver.log
                          -rw-------   1 root wheel 507949 May  9 12:03 system.log
                          -rw-r--r--   1 root wheel    394 May  9 12:02 utx.lastlogin
                          -rw-------   1 root wheel   2037 May  9 12:02 utx.log
                          
                          S 1 Reply Last reply Reply Quote 0
                          • S
                            SteveITS Galactic Empire @mrneutron
                            last edited by

                            @mrneutron The RAM disk setting requires a restart to turn on.

                            The log file will always have current timestamps. It's just a matter of where they are being saved.

                            If you are concerned about logs, you may want to put a number in that Log Directory field, for instance, to copy logs to eMMC storage every "n" hours. Otherwise they are copied during a clean halt/restart.

                            if on it will show in the dashboard Disks widget:
                            ed4a7691-aeeb-4fe4-a27e-769be2d90286-image.png

                            Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                            When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                            Upvote 👍 helpful posts!

                            M 1 Reply Last reply Reply Quote 0
                            • M
                              mrneutron @SteveITS
                              last edited by

                              @SteveITS said in SG-1100 update from 23.09.1 to 24.03 keeps failing:

                              @mrneutron The RAM disk setting requires a restart to turn on.

                              The log file will always have current timestamps. It's just a matter of where they are being saved.

                              If you are concerned about logs, you may want to put a number in that Log Directory field, for instance, to copy logs to eMMC storage every "n" hours. Otherwise they are copied during a clean halt/restart.

                              if on it will show in the dashboard Disks widget:
                              ed4a7691-aeeb-4fe4-a27e-769be2d90286-image.png

                              @SteveITS, right now, I'm trying to determine if my emmc chip is still working correctly. Thus, I'm trying to determine if any files are being successfully written to it.

                              S 1 Reply Last reply Reply Quote 0
                              • S
                                SteveITS Galactic Empire @mrneutron
                                last edited by

                                @mrneutron Ah, I see. IIRC you need to restart to "lose" files with ZFS(?) since hides it due to caching. Try creating a file and restarting, to see if it's still there.

                                Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                                When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                                Upvote 👍 helpful posts!

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

                                  I used the touch command to create files in the / directory and /var/log directories.
                                  Both files were gone after a normal reboot.
                                  I guess this is more evidence that the emmc is read-only, now?

                                  I read that the mount command is supposed to show if the mounted partitions are ro or rw. It doesn't show ro or rw for any of them.

                                  [23.09.1-RELEASE][admin@redacted]/: mount
                                  pfSense/ROOT/default on / (zfs, local, noatime, nfsv4acls)
                                  devfs on /dev (devfs)
                                  pfSense/tmp on /tmp (zfs, local, noatime, nosuid, nfsv4acls)
                                  pfSense/home on /home (zfs, local, noatime, nfsv4acls)
                                  pfSense/var on /var (zfs, local, noatime, nfsv4acls)
                                  pfSense/var/cache on /var/cache (zfs, local, noatime, noexec, nosuid, nfsv4acls)
                                  pfSense/var/tmp on /var/tmp (zfs, local, noatime, nosuid, nfsv4acls)
                                  pfSense/var/log on /var/log (zfs, local, noatime, noexec, nosuid, nfsv4acls)
                                  pfSense/var/db on /var/db (zfs, local, noatime, noexec, nosuid, nfsv4acls)
                                  pfSense/ROOT/default/cf on /cf (zfs, local, noatime, noexec, nosuid, nfsv4acls)
                                  pfSense/ROOT/default/var_cache_pkg on /var/cache/pkg (zfs, local, noatime, noexec, nosuid, nfsv4acls)
                                  pfSense/ROOT/default/var_db_pkg on /var/db/pkg (zfs, local, noatime, noexec, nosuid, nfsv4acls)
                                  tmpfs on /var/run (tmpfs, local)
                                  devfs on /var/dhcpd/dev (devfs)
                                  
                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by stephenw10

                                    I don't thing mount would show it. They are not mounted read-only. mount -p should show it though if they were.

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

                                      Huh...all the Linux examples I saw of the mount command had only mount (no -p).
                                      Is BSD usage different?

                                      Using mount -p they are all supposedly mounted rw, but they don't hold what I write to them.

                                      [23.09.1-RELEASE][admin@redacted]/: mount -p
                                      pfSense/ROOT/default    /                       zfs     rw,noatime,nfsv4acls    0 0
                                      devfs                   /dev                    devfs   rw              0 0
                                      pfSense/tmp             /tmp                    zfs     rw,nosuid,noatime,nfsv4acls     0 0
                                      pfSense/home            /home                   zfs     rw,noatime,nfsv4acls    0 0
                                      pfSense/var             /var                    zfs     rw,noatime,nfsv4acls    0 0
                                      pfSense/var/cache       /var/cache              zfs     rw,noexec,nosuid,noatime,nfsv4acls      0 0
                                      pfSense/var/tmp         /var/tmp                zfs     rw,nosuid,noatime,nfsv4acls     0 0
                                      pfSense/var/log         /var/log                zfs     rw,noexec,nosuid,noatime,nfsv4acls      0 0
                                      pfSense/var/db          /var/db                 zfs     rw,noexec,nosuid,noatime,nfsv4acls      0 0
                                      pfSense/ROOT/default/cf /cf                     zfs     rw,noexec,nosuid,noatime,nfsv4acls      0 0
                                      pfSense/ROOT/default/var_cache_pkg /var/cache/pkg               zfs     rw,noexec,nosuid,noatime,nfsv4acls      0 0
                                      pfSense/ROOT/default/var_db_pkg /var/db/pkg             zfs     rw,noexec,nosuid,noatime,nfsv4acls      0 0
                                      tmpfs                   /var/run                tmpfs   rw              0 0
                                      devfs                   /var/dhcpd/dev          devfs   rw              0 0
                                      
                                      1 Reply Last reply Reply Quote 0
                                      • stephenw10S
                                        stephenw10 Netgate Administrator
                                        last edited by

                                        The -p switch cause it to print the output in fstab format and includes verbose info.
                                        https://man.freebsd.org/cgi/man.cgi?query=mount

                                        Yes so ZFS think it's all mounted read-write but that doesn't help if the actual storage is read-only.

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

                                          Yeah, it sure looks like the emmc in my SG-1100 is no longer writable (upgradable).
                                          It still boots in the configuration I had it set in, but I wonder how long before it goes non-functional?

                                          "Certain types of disks, such as SSD and eMMC disks, may fail into a read only state where disk writes fail or are discarded, but data can still be read."

                                          from: https://docs.netgate.com/pfsense/en/latest/troubleshooting/disk-lifetime.html

                                          1 Reply Last reply Reply Quote 0
                                          • stephenw10S
                                            stephenw10 Netgate Administrator
                                            last edited by

                                            Yes unfortunately I have to agree. You can try installing to USB. I tested that yesterday.

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