Navigation

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

    3100 locked up

    Official Netgate® Hardware
    1
    3
    189
    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.
    • G
      gherkin'd last edited by

      I say locked up, but my device is having performance issues.
      After halting the system from a terminal session and pwr'ing down, then reboot; it seems to have gone wonky.
      For awhile last PM (after mentioned reboot), the Dashboard showed 100% CPU and DHCP service not started.
      So I again halted and pwr'd down for the night.
      Today, I've performed file system consistency checks, reloaded Pfsense > rreloaded last known config.

      This is a residential application self-bootstrapped on maintenance knowledge, so I'm not sure what else to say. But did capture the boot sequence and file consistency responses.
      The 3100 has been running 24/7 since that last version update w/ that subsequent patch.

      Any help and suggestions sure would be good, I'm afraid the hardware has failed somewhere.

      1 Reply Last reply Reply Quote 0
      • G
        gherkin'd last edited by gherkin'd

        Output of a re-boot after loading default factory config.

        ![0_1621715788404_Failure.png](Uploading 100%)

        Here's a section of boot output. is this normal ??

        FreeBSD/armv6 U-Boot loader, Revision 1.2
        (Tue Jul 10 10:26:23 EDT 2018 root@buildbot3)

        DRAM: 2048MB
        Number of U-Boot devices: 4
        U-Boot env: loaderdev not set, will probe all devices.
        Found U-Boot device: disk
        Probing all disk devices...
        Checking unit=0 slice=<auto> partition=<auto>...disk0: read failed, error=1

        Checking unit=1 slice=<auto> partition=<auto>...disk1: read failed, error=1

        Checking unit=2 slice=<auto> partition=<auto>... good.
        Booting from disk2s2a:
        Loading /boot/defaults/loader.conf

        1 Reply Last reply Reply Quote 0
        • G
          gherkin'd last edited by gherkin'd

          Resolved.
          New firmware; 21.02.2

          1 Reply Last reply Reply Quote 0
          • First post
            Last post