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

    Another Netgate with storage failure, 6 in total so far

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    305 Posts 38 Posters 81.7k 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.
    • M
      Mission-Ghost @azdeltawye
      last edited by

      @azdeltawye said in Another Netgate with storage failure, 6 in total so far:

      Quick question - Do you have to run the zfs set command on each subsequent reboot or just the first time after adding the tunable?

      I'd be interested in the answer as well. The freeBSD help and Google Gemini (which is often wrong but never in doubt) suggests it's a one-time setting.

      I missed this setting in earlier discussions, so I just executed it and it's set in the zfs config now. I haven't rebooted. Yet.

      fireodoF 1 Reply Last reply Reply Quote 0
      • fireodoF
        fireodo @Mission-Ghost
        last edited by fireodo

        @Mission-Ghost said in Another Netgate with storage failure, 6 in total so far:

        I missed this setting in earlier discussions, so I just executed it and it's set in the zfs config now. I haven't rebooted. Yet.

        If you make a entry in the "system tuning" the setting will survive even a system upgrade (if still necessary)...

        Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
        SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
        pfsense 2.8.0 CE
        Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

        M 1 Reply Last reply Reply Quote 0
        • E
          elvisimprsntr
          last edited by elvisimprsntr

          Even though I have a Kingston mSATA SDD with 2.1 years power on hours, life is down to 90%

          
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  9 Power_On_Hours          0x0000   100   100   000    Old_age   Offline      -       18867
169 Remaining_Lifetime_Perc 0x0000   090   090   000    Old_age   Offline      -       90


          sysctl vfs.zfs.txg.timeout=30

          Lower case "default" on 2.7.2 CE

          zfs list

NAME                                 USED  AVAIL  REFER  MOUNTPOINT
pfSense                             24.1G   205G    96K  /pfSense
pfSense/ROOT                        1.11G   205G    96K  none
pfSense/ROOT/default                1.11G   205G  1.10G  /
pfSense/ROOT/default/cf             6.88M   205G  6.88M  /cf
pfSense/ROOT/default/var_cache_pkg   336K   205G   336K  /var/cache/pkg
pfSense/ROOT/default/var_db_pkg     5.42M   205G  5.42M  /var/db/pkg
pfSense/home                         108K   205G   108K  /home
pfSense/reservation                   96K   227G    96K  /pfSense/reservation
pfSense/tmp                         1.37M   205G  1.37M  /tmp
pfSense/var                         35.9M   205G  3.45M  /var
pfSense/var/cache                     96K   205G    96K  /var/cache
pfSense/var/db                      2.38M   205G  2.38M  /var/db
pfSense/var/empty                     96K   205G    96K  /var/empty
pfSense/var/log                     29.8M   205G  29.8M  /var/log
pfSense/var/tmp                      136K   205G   136K  /var/tmp

zfs set sync=always pfSense/ROOT/default/cf
          M 1 Reply Last reply Reply Quote 0
          • fireodoF
            fireodo @valnar
            last edited by

            @valnar said in Another Netgate with storage failure, 6 in total so far:

            If not, can somebody summarize the recommended tweaks?

            These are my settings:

            vfs.zfs.txg.timeout=120 (you can increase this value as you wish - I was gone until 2400 in experiments with no problems)
zfs set sync=disabled zroot/tmp (pfSense/tmp)
zfs set sync=disabled zroot/var (pfSense/var)

            Regards,
            fireodo

            Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
            SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
            pfsense 2.8.0 CE
            Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

            JonathanLeeJ 1 Reply Last reply Reply Quote 2
            • M
              Mission-Ghost @elvisimprsntr
              last edited by

              @elvisimprsntr Interesting. Why the inconsistency, I wonder?

              1 Reply Last reply Reply Quote 0
              • M
                Mission-Ghost @fireodo
                last edited by

                @fireodo said in Another Netgate with storage failure, 6 in total so far:

                If you make a entry in the "system tuning" the setting will survive even a system upgrade (if still necessary)...

                Sweet. Thanks.

                fireodoF 1 Reply Last reply Reply Quote 0
                • fireodoF
                  fireodo @Mission-Ghost
                  last edited by

                  @Mission-Ghost said in Another Netgate with storage failure, 6 in total so far:

                  Sweet.

                  Nice that it tastes good 😁 😁

                  Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
                  SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
                  pfsense 2.8.0 CE
                  Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

                  1 Reply Last reply Reply Quote 0
                  • JonathanLeeJ
                    JonathanLee @fireodo
                    last edited by JonathanLee

                    @fireodo You should set this in cron right? Because this will default every reboot...

                    zfs set sync=disabled pfSense/var
                    zfs set sync=disabled pfSense/tmp

                    should they no longer show if you run "zfs list" also?

                    Make sure to upvote

                    fireodoF 2 Replies Last reply Reply Quote 0
                    • fireodoF
                      fireodo @JonathanLee
                      last edited by

                      @JonathanLee said in Another Netgate with storage failure, 6 in total so far:

                      You use the zfs set sync=disabled pfSense/var in cron right?

                      No.

                      Because this will default every reboot...

                      Not here - once set it remains that way even after reboot. (btw. on 23.04.2025 the system was rebooted, after an long power outage that exhausted the UPS, caused by work on the power line by the provider)

                      Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
                      SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
                      pfsense 2.8.0 CE
                      Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

                      cmcdonaldC 1 Reply Last reply Reply Quote 0
                      • fireodoF
                        fireodo @JonathanLee
                        last edited by

                        @JonathanLee said in Another Netgate with storage failure, 6 in total so far:

                        should they no longer show if you run "zfs list" also?

                        You should see the status if you run:

                        zfs get -r sync pfSense

                        or

                        zfs get -r sync zroot

                        depending on what pfsense system you are.

                        Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
                        SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
                        pfsense 2.8.0 CE
                        Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

                        JonathanLeeJ 1 Reply Last reply Reply Quote 2
                        • JonathanLeeJ
                          JonathanLee @fireodo
                          last edited by JonathanLee

                          @fireodo Thank you for the reply,

                          Shell Output - zfs get -r sync pfSense
NAME                                                                                PROPERTY  VALUE     SOURCE
pfSense                                                                             sync      standard  default
pfSense/ROOT                                                                        sync      standard  default
pfSense/ROOT/23_05_01_clone                                                         sync      standard  default
pfSense/ROOT/23_05_01_clone/cf                                                      sync      standard  default
pfSense/ROOT/23_05_01_clone/var_db_pkg                                              sync      standard  default
pfSense/ROOT/23_05_01_ipv4                                                          sync      standard  default
pfSense/ROOT/23_05_01_ipv4@2024-01-12-11:46:05-0                                    sync      -         -
pfSense/ROOT/23_05_01_ipv4@2024-02-29-08:52:57-0                                    sync      -         -
pfSense/ROOT/23_05_01_ipv4@2024-04-01-12:32:27-0                                    sync      -         -
pfSense/ROOT/23_05_01_ipv4@2024-06-27-11:52:26-0                                    sync      -         -
pfSense/ROOT/23_05_01_ipv4@2024-07-03-09:09:28-0                                    sync      -         -
pfSense/ROOT/23_05_01_ipv4@2025-01-20-10:11:49-0                                    sync      -         -
pfSense/ROOT/23_05_01_ipv4/cf                                                       sync      standard  default
pfSense/ROOT/23_05_01_ipv4/cf@2025-01-20-10:11:49-0                                 sync      -         -
pfSense/ROOT/23_05_01_ipv4/var_cache_pkg                                            sync      standard  default
pfSense/ROOT/23_05_01_ipv4/var_cache_pkg@2025-01-20-10:11:49-0                      sync      -         -
pfSense/ROOT/23_05_01_ipv4/var_db_pkg                                               sync      standard  default
pfSense/ROOT/23_05_01_ipv4/var_db_pkg@2025-01-20-10:11:49-0                         sync      -         -
pfSense/ROOT/23_05_01_ipv4_Backup                                                   sync      standard  default
pfSense/ROOT/23_05_01_ipv4_Backup/cf                                                sync      standard  default
pfSense/ROOT/23_05_01_ipv4_Backup/var_cache_pkg                                     sync      standard  default
pfSense/ROOT/23_05_01_ipv4_Backup/var_db_pkg                                        sync      standard  default
pfSense/ROOT/23_05_01_ipv6                                                          sync      standard  default
pfSense/ROOT/23_05_01_ipv6@2025-04-30-11:18:04-0                                    sync      -         -
pfSense/ROOT/23_05_01_ipv6/cf                                                       sync      standard  default
pfSense/ROOT/23_05_01_ipv6/cf@2025-04-30-11:18:04-0                                 sync      -         -
pfSense/ROOT/23_05_01_ipv6/var_db_pkg                                               sync      standard  default
pfSense/ROOT/23_05_01_ipv6/var_db_pkg@2025-04-30-11:18:04-0                         sync      -         -
pfSense/ROOT/23_05_01_ipv6_non_website_test_proxy                                   sync      standard  default
pfSense/ROOT/23_05_01_ipv6_non_website_test_proxy/cf                                sync      standard  default
pfSense/ROOT/23_05_01_ipv6_non_website_test_proxy/cf@2024-01-12-11:46:05-0          sync      -         -
pfSense/ROOT/23_05_01_ipv6_non_website_test_proxy/cf@2024-02-29-08:52:57-0          sync      -         -
pfSense/ROOT/23_05_01_ipv6_non_website_test_proxy/cf@2024-04-01-12:32:27-0          sync      -         -
pfSense/ROOT/23_05_01_ipv6_non_website_test_proxy/cf@2024-06-27-11:52:26-0          sync      -         -
pfSense/ROOT/23_05_01_ipv6_non_website_test_proxy/cf@2024-07-25-15:54:45-0          sync      -         -
pfSense/ROOT/23_05_01_ipv6_non_website_test_proxy/cf@2025-04-30-12:10:00-0          sync      -         -
pfSense/ROOT/23_05_01_ipv6_non_website_test_proxy/var_db_pkg                        sync      standard  default
pfSense/ROOT/23_05_01_ipv6_non_website_test_proxy/var_db_pkg@2024-01-12-11:46:05-0  sync      -         -
pfSense/ROOT/23_05_01_ipv6_non_website_test_proxy/var_db_pkg@2024-02-29-08:52:57-0  sync      -         -
pfSense/ROOT/23_05_01_ipv6_non_website_test_proxy/var_db_pkg@2024-04-01-12:32:27-0  sync      -         -
pfSense/ROOT/23_05_01_ipv6_non_website_test_proxy/var_db_pkg@2024-06-27-11:52:26-0  sync      -         -
pfSense/ROOT/23_05_01_ipv6_non_website_test_proxy/var_db_pkg@2024-07-25-15:54:45-0  sync      -         -
pfSense/ROOT/23_05_01_ipv6_non_website_test_proxy/var_db_pkg@2025-04-30-12:10:00-0  sync      -         -
pfSense/ROOT/23_05_01_ipv6_website_test_proxy_clone                                 sync      standard  default
pfSense/ROOT/23_05_01_ipv6_website_test_proxy_clone@2024-07-25-15:54:45-0           sync      -         -
pfSense/ROOT/23_05_01_ipv6_website_test_proxy_clone@2025-04-30-12:10:00-0           sync      -         -
pfSense/ROOT/23_05_01_ipv6_website_test_proxy_clone/cf                              sync      standard  default
pfSense/ROOT/23_05_01_ipv6_website_test_proxy_clone/var_db_pkg                      sync      standard  default
pfSense/ROOT/23_09_01_ipv4_20240703094025                                           sync      standard  default
pfSense/ROOT/23_09_01_ipv4_20240703094025/cf                                        sync      standard  default
pfSense/ROOT/23_09_01_ipv4_20240703094025/var_cache_pkg                             sync      standard  default
pfSense/ROOT/23_09_01_ipv4_20240703094025/var_db_pkg                                sync      standard  default
pfSense/ROOT/24_03_01_ipv4                                                          sync      standard  default
pfSense/ROOT/24_03_01_ipv4/cf                                                       sync      standard  default
pfSense/ROOT/24_03_01_ipv4/var_cache_pkg                                            sync      standard  default
pfSense/ROOT/24_03_01_ipv4/var_db_pkg                                               sync      standard  default
pfSense/ROOT/24_03_01_ipv6_20250113135850                                           sync      standard  default
pfSense/ROOT/24_03_01_ipv6_20250113135850@2024-07-03-09:40:36-0                     sync      -         -
pfSense/ROOT/24_03_01_ipv6_20250113135850@2024-07-23-10:05:22-0                     sync      -         -
pfSense/ROOT/24_03_01_ipv6_20250113135850@2025-01-13-13:59:02-0                     sync      -         -
pfSense/ROOT/24_03_01_ipv6_20250113135850/cf                                        sync      standard  default
pfSense/ROOT/24_03_01_ipv6_20250113135850/cf@2024-07-03-09:09:28-0                  sync      -         -
pfSense/ROOT/24_03_01_ipv6_20250113135850/cf@2024-07-03-09:40:36-0                  sync      -         -
pfSense/ROOT/24_03_01_ipv6_20250113135850/cf@2024-07-23-10:05:22-0                  sync      -         -
pfSense/ROOT/24_03_01_ipv6_20250113135850/cf@2025-01-13-13:59:02-0                  sync      -         -
pfSense/ROOT/24_03_01_ipv6_20250113135850/var_cache_pkg                             sync      standard  default
pfSense/ROOT/24_03_01_ipv6_20250113135850/var_cache_pkg@2024-07-03-09:09:28-0       sync      -         -
pfSense/ROOT/24_03_01_ipv6_20250113135850/var_cache_pkg@2024-07-03-09:40:36-0       sync      -         -
pfSense/ROOT/24_03_01_ipv6_20250113135850/var_cache_pkg@2024-07-23-10:05:22-0       sync      -         -
pfSense/ROOT/24_03_01_ipv6_20250113135850/var_cache_pkg@2025-01-13-13:59:02-0       sync      -         -
pfSense/ROOT/24_03_01_ipv6_20250113135850/var_db_pkg                                sync      standard  default
pfSense/ROOT/24_03_01_ipv6_20250113135850/var_db_pkg@2024-07-03-09:09:28-0          sync      -         -
pfSense/ROOT/24_03_01_ipv6_20250113135850/var_db_pkg@2024-07-03-09:40:36-0          sync      -         -
pfSense/ROOT/24_03_01_ipv6_20250113135850/var_db_pkg@2024-07-23-10:05:22-0          sync      -         -
pfSense/ROOT/24_03_01_ipv6_20250113135850/var_db_pkg@2025-01-13-13:59:02-0          sync      -         -
pfSense/ROOT/auto-default-20240112115753                                            sync      standard  default
pfSense/ROOT/auto-default-20240112115753@2024-01-12-11:57:53-0                      sync      -         -
pfSense/ROOT/auto-default-20240112115753/cf                                         sync      standard  default
pfSense/ROOT/auto-default-20240112115753/cf@2024-01-12-11:57:53-0                   sync      -         -
pfSense/ROOT/auto-default-20240112115753/var_cache_pkg                              sync      standard  default
pfSense/ROOT/auto-default-20240112115753/var_cache_pkg@2024-01-12-11:57:53-0        sync      -         -
pfSense/ROOT/auto-default-20240112115753/var_db_pkg                                 sync      standard  default
pfSense/ROOT/auto-default-20240112115753/var_db_pkg@2024-01-12-11:57:53-0           sync      -         -
pfSense/ROOT/quick-20240401123227                                                   sync      standard  default
pfSense/ROOT/quick-20240401123227/cf                                                sync      standard  default
pfSense/ROOT/quick-20240401123227/var_db_pkg                                        sync      standard  default
pfSense/home                                                                        sync      standard  default
pfSense/reservation                                                                 sync      standard  default
pfSense/tmp                                                                         sync      disabled  local
pfSense/var                                                                         sync      disabled  local
pfSense/var/cache                                                                   sync      disabled  inherited from pfSense/var
pfSense/var/db                                                                      sync      disabled  inherited from pfSense/var
pfSense/var/log                                                                     sync      disabled  inherited from pfSense/var
pfSense/var/tmp                                                                     sync      disabled  inherited from pfSense/var

                          logs and temp are now excluded from sync

                          and I also set

                          vfs.zfs.txg.timeout=120

                          I also use a secondary nvme drive just for package logs I have a mount point and created linker files that direct everything that is write intensive over to it. That helps alot also, and or you can use a usb thumb drive for package logs if anyone is really worried.

                          691b97ae-7284-4f19-af85-e2f8ac1c14a8-image.png

                          https://forum.netgate.com/topic/195843/unofficial-guide-have-package-logs-record-to-a-secondary-ssd-drive-snort-syslog-squid-and-or-squid-cache-system/

                          Make sure to upvote

                          1 Reply Last reply Reply Quote 2
                          • cmcdonaldC
                            cmcdonald Netgate Developer @fireodo
                            last edited by

                            @fireodo said in Another Netgate with storage failure, 6 in total so far:

                            Not here - once set it remains that way even after reboot.

                            Yes. This is correct. ZFS properties persist across reboots (unless they are changed by something during startup, say in pfSense-rc, though I don't think we do any of that)

                            Need help fast? https://www.netgate.com/support

                            1 Reply Last reply Reply Quote 1
                            • w0wW w0w referenced this topic on
                            • D
                              dugeem
                              last edited by

                              One additional issue to be aware of is that up until pfSense+ 24.03 the Netgate SG-1100 (& SG-2100) installation images resulted in eMMC having non aligned flash partitions. This can result in file system activity causing sub optimal block writing (due to sectors crossing erase boundaries) resulting in increased flash wear.

                              pfSense Redmine reference -> https://redmine.pfsense.org/issues/15126

                              Easy to check - from shell use the command:

                              gpart show mmcsd0

                              and check numbers in first column for either freebsd / freebsd-zfs partitions are divisible by 8 (or a higher power of 2).

                              Generally if your SG-1100 (also SG-2100) was originally commissioned prior to pfSense+ 24.03 then you should consider reinstalling and restoring config.

                              Relevant Netgate SG-1100 documentation -> https://docs.netgate.com/pfsense/en/latest/solutions/sg-1100/reinstall-pfsense.html

                              1 Reply Last reply Reply Quote 3
                              • w0wW
                                w0w
                                last edited by

                                Netgate has finally implemented the fix.
                                https://redmine.pfsense.org/issues/16210#change-76840
                                Thank you, @marcosm, @fireodo, @andrew_cb

                                P 1 Reply Last reply Reply Quote 5
                                • P
                                  Patch @w0w
                                  last edited by Patch

                                  Looks like it changes the vfs.zfs.txg.timeout default from
                                  FreeBSD vfs.zfs.txg.timeout = 5
                                  pfsense vfs.zfs.txg.timeout = 30

                                  So not as high as 120 suggested but consistent with andrew_cb recommendation

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

                                    That patch code also has this: "zfs set sync=always pfSense/ROOT/default/cf"
                                    Looking at my own system, I don't have that path, as I have only manually named Boot Environments, I have paths like "pfSense/ROOT/24.11_stable/cf ", so that part would fail.

                                    Should the command be run manually on the current default/active BE path, "pfSense/ROOT/24.11_stable/cf " in my case?

                                    pfSense Plus 24.11-RELEASE (amd64)
                                    Dell Optiplex 7040 SFF
                                    Core i5-6500, 8GB RAM, 2x 240GB SSD (ZFS Mirror)
                                    HPE 561T (X540-AT2), 2-port 10Gb RJ45
                                    HPE 562SFP+ (X710-DA2), 2-port 10Gb SFP+

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

                                      Yup. Fix incoming.

                                      JonathanLeeJ M 2 Replies Last reply Reply Quote 3
                                      • JonathanLeeJ
                                        JonathanLee @stephenw10
                                        last edited by

                                        @stephenw10 should the timeout be 120 or 30?

                                        Make sure to upvote

                                        1 Reply Last reply Reply Quote 1
                                        • JonathanLeeJ
                                          JonathanLee @andrew_cb
                                          last edited by

                                          @andrew_cb

                                          zfs set sync=always pfSense/ROOT/default/cf

                                          does not work on my 2100 I have a SSD should I run a different command for this?

                                          Make sure to upvote

                                          1 Reply Last reply Reply Quote 0
                                          • M
                                            marcosm Netgate
                                            last edited by

                                            A fix will be provided once it's ready on the following redmine:
                                            https://redmine.pfsense.org/issues/16212

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