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

    Fatal error when trying to edit rules (Solved - Bad Drive)

    webGUI
    2
    6
    1.4k
    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.
    • V
      Visseroth
      last edited by

      I've been getting a fatal error whenever I try to edit a rule, any rule, if it's in NAT or on a interface.

      Here is one…

      Fatal error: Call to undefined function user_rule_descr_maxlen() in /usr/local/www/firewall_rules_edit.php on line 1503 Call Stack: 0.0003 232320 1\. {main}() /usr/local/www/firewall_rules_edit.php:0 PHP ERROR: Type: 1, File: /usr/local/www/firewall_rules_edit.php, Line: 1503, Message: Call to undefined function user_rule_descr_maxlen()

      Here's another…

      Fatal error: Call to undefined function is_port_or_alias() in /usr/local/www/firewall_nat_edit.php on line 301 Call Stack: 0.0001 243680 1\. {main}() /usr/local/www/firewall_nat_edit.php:0 PHP ERROR: Type: 1, File: /usr/local/www/firewall_nat_edit.php, Line: 301, Message: Call to undefined function is_port_or_alias()
      1 Reply Last reply Reply Quote 0
      • S
        Steve_B Netgate
        last edited by

        Which version of pfSense?

        I am unable to reproduce on 2.3.4 and latest snapshots.

        Als ik kan

        1 Reply Last reply Reply Quote 0
        • V
          Visseroth
          last edited by

          Yea, sorry about that. I forgot to post my version…

          2.3.3-RELEASE (amd64)
          built on Thu Mar 09 07:17:41 CST 2017
          FreeBSD 10.3-RELEASE-p19

          The system is on the latest version.

          Everything had been fine before. I'm not sure when this bug started.

          If the latest is 2.3.4 then my system isn't showing that there is a update.

          1 Reply Last reply Reply Quote 0
          • V
            Visseroth
            last edited by

            So that last one was from the dashboard.

            Apparently this is from the upgrade option…

            Current Base System
            2.3.4
            Latest Base System
            2.3.4
            Status
            Up to date.

            1 Reply Last reply Reply Quote 0
            • V
              Visseroth
              last edited by

              I'm actually starting to think there may be corruption as I just noticed I'm getting cam errors from the console…

              May 24 13:38:01 	kernel 		(ada0:ahcich4:0:0:0): Error 5, Retries exhausted
May 24 13:38:01 	kernel 		(ada0:ahcich4:0:0:0): RES: 51 40 38 01 f5 40 37 00 00 57 00
May 24 13:38:01 	kernel 		(ada0:ahcich4:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC )
May 24 13:38:01 	kernel 		(ada0:ahcich4:0:0:0): CAM status: ATA Status Error
May 24 13:38:01 	kernel 		(ada0:ahcich4:0:0:0): READ_FPDMA_QUEUED. ACB: 60 80 0f 01 f5 40 37 00 00 00 00 00
May 24 13:38:01 	kernel 		(ada0:ahcich4:0:0:0): Retrying command 

              SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   062    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   040    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   131   131   033    Pre-fail  Always       -       1
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       25
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   040    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   087   087   000    Old_age   Always       -       6062
 10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       25
191 G-Sense_Error_Rate      0x000a   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       2
193 Load_Cycle_Count        0x0012   074   074   000    Old_age   Always       -       268673
194 Temperature_Celsius     0x0002   206   206   000    Old_age   Always       -       29 (Min/Max 20/34)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       12
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       8
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0
223 Load_Retry_Count        0x000a   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
ATA Error Count: 11660 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 11660 occurred at disk power-on lifetime: 6062 hours (252 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 57 38 01 f5 07  Error: UNC at LBA = 0x07f50138 = 133497144

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 80 c0 0f 01 f5 40 00   3d+04:41:18.058  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   3d+04:41:18.053  READ LOG EXT
  60 80 b0 0f 01 f5 40 00   3d+04:41:17.925  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   3d+04:41:17.920  READ LOG EXT
  60 80 a0 0f 01 f5 40 00   3d+04:41:17.800  READ FPDMA QUEUED

Error 11659 occurred at disk power-on lifetime: 6062 hours (252 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 57 38 01 f5 07  Error: UNC at LBA = 0x07f50138 = 133497144

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 80 b0 0f 01 f5 40 00   3d+04:41:17.925  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   3d+04:41:17.920  READ LOG EXT
  60 80 a0 0f 01 f5 40 00   3d+04:41:17.800  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   3d+04:41:17.795  READ LOG EXT
  60 80 90 0f 01 f5 40 00   3d+04:41:17.667  READ FPDMA QUEUED

Error 11658 occurred at disk power-on lifetime: 6062 hours (252 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 57 38 01 f5 07  Error: UNC at LBA = 0x07f50138 = 133497144

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 80 a0 0f 01 f5 40 00   3d+04:41:17.800  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   3d+04:41:17.795  READ LOG EXT
  60 80 90 0f 01 f5 40 00   3d+04:41:17.667  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   3d+04:41:17.661  READ LOG EXT
  60 80 80 0f 01 f5 40 00   3d+04:41:17.537  READ FPDMA QUEUED

Error 11657 occurred at disk power-on lifetime: 6062 hours (252 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 57 38 01 f5 07  Error: UNC at LBA = 0x07f50138 = 133497144

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 80 90 0f 01 f5 40 00   3d+04:41:17.667  READ FPDMA QUEUED
  2f 00 01 10 00 00 00 00   3d+04:41:17.661  READ LOG EXT
  60 80 80 0f 01 f5 40 00   3d+04:41:17.537  READ FPDMA QUEUED
  60 08 78 2f 01 f5 40 00   3d+04:41:17.494  READ FPDMA QUEUED
  61 01 70 e5 a0 00 40 00   3d+04:41:17.063  WRITE FPDMA QUEUED

Error 11656 occurred at disk power-on lifetime: 6062 hours (252 days + 14 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 57 38 01 f5 07  Error: UNC at LBA = 0x07f50138 = 133497144

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 80 80 0f 01 f5 40 00   3d+04:41:17.537  READ FPDMA QUEUED
  60 08 78 2f 01 f5 40 00   3d+04:41:17.494  READ FPDMA QUEUED
  61 01 70 e5 a0 00 40 00   3d+04:41:17.063  WRITE FPDMA QUEUED
  61 08 68 c7 e0 df 40 00   3d+04:41:16.112  WRITE FPDMA QUEUED
  60 08 60 27 68 bf 40 00   3d+04:41:13.836  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Interrupted (host reset)      90%      6062         -
# 2  Extended offline    Completed: read failure       60%      5334         725753056
# 3  Short offline       Completed without error       00%      2072         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
              1 Reply Last reply Reply Quote 0
              • V
                Visseroth
                last edited by

                Problem was definately a failing drive which was NOT reported in the dashboard!!!  >:(

                So, off to make another post

                Failing.JPG
                Failing.JPG_thumb

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