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

    SG-3100 no reboot

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    11 Posts 2 Posters 569 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.
    • G
      ggpf
      last edited by

      Hi,

      I just follow the documentation.
      https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/initial-configuration.html
      I push the reset button and nve n my PC I configure my unique Ethernet interface with ip Address
      192.168.1.2/255.255.255.0 gateway 192.168.1.1.
      It seems my SG-3100 is reboot for a certain time, but after this time the 3 LED is blinking
      and I try to ping it on 192.168.1.1 I don't get any answer and I try on http://192.168.1.1
      I net get any answer from Netgate 3100.
      When I try to connect over USB port COM5 after installing and try to connect with PUTTY
      I don't get any answer.
      I have connected only on cable on LAN1 plug not other Ethernet cable ?
      Any idea to fix this troubles ? Maybe hardware problem ?

      Regards.
      GG.

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

        @ggpf said in SG-3100 no reboot:

        It seems my SG-3100 is reboot for a certain time, but after this time the 3 LED is blinking

        Do they ever stop blinking and change to just one pulsing? That indicates it has booted correctly:
        https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/io-ports.html#led-patterns

        It's probably stuck in a boot loop after being hard reset. Try connecting to the serial console to see what's happening:
        https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/connect-to-console.html

        Steve

        G 1 Reply Last reply Reply Quote 0
        • stephenw10S stephenw10 moved this topic from Hardware on
        • G
          ggpf @stephenw10
          last edited by

          @stephenw10 said in SG-3100 no reboot:

          @ggpf said in SG-3100 no reboot:

          It seems my SG-3100 is reboot for a certain time, but after this time the 3 LED is blinking

          Do they ever stop blinking and change to just one pulsing? That indicates it has booted correctly:
          https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/io-ports.html#led-patterns

          It's probably stuck in a boot loop after being hard reset. Try connecting to the serial console to see what's happening:
          https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/connect-to-console.html

          Steve

          Hi Steve,

          When the 3 LED are blinking it seems SG-3100 turn all the LED of and Ethernet LED detect is also of like when I plug the power plug.
          and do that indefinitly it seems it reboot. I plug USB Serial with 115200 Bits 1 stop bit no protocol and I don'"t receive nothing. :(

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

            Ok, that sounds like it's stuck in a boot loop then. It's probably not a hardware issue since it's booting far enough to start the LEDs flashing.

            When you connect the console does the client see the new USB/Serial adapter device?

            Did you have to install a driver?

            What terminal program are you using? How is it configured?

            Is this the first time you've tried to connect to the console?

            Steve

            G 3 Replies Last reply Reply Quote 0
            • G
              ggpf @stephenw10
              last edited by

              @stephenw10

              When I connect the console I don't have the menu of Pfsense + I have
              Welcome to Netgate pfSense Plus 21.02.2-RELEASE...

              ...ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/lib/engines /usr/local/lib/compat/pkg /usr/local/lib/ipsec /usr/local/lib/perl5/5.32/mach/CORE
              Soft Float compatibility ldconfig path:
              done.
              panic: softdep_setup_inomapdep: dependency 0xde772800 for newinode already exists
              cpuid = 0
              time = 4261411844
              Uptime: 6s
              Automatic reboot in 15 seconds - press a key on the console to abort
              --> Press a key on the console to reboot,
              --> or switch off the system now.

              That's it. :(

              1 Reply Last reply Reply Quote 0
              • G
                ggpf
                last edited by

                Sorry I don't reply completely
                I am using GTKTERM and I configure /dev/ttyUSB0 and it works fine.
                I configure correctly the speed 115200 8 bits

                1 Reply Last reply Reply Quote 0
                • G
                  ggpf @stephenw10
                  last edited by stephenw10

                  @stephenw10
                  Hi Steve,

                  When the Netgate is rebooting this is the full trace I get it with GTKTerm

                  General initialization - Version: 1.0.0
AVS selection from EFUSE disabled (Skip reading EFUSE values)
Overriding default AVS value to: 0x23
Detected Device ID 6820
High speed PHY - Version: 2.0

Init Customer board board SerDes lanes topology details:
 | Lane # | Speed|    Type     |
 ------------------------------|
 |   0    |  3   |  SATA0      |
 |   1    |  5   |  PCIe0      |
 |   2    |  3   |  SATA1      |
 |   3    |  4   |  SGMII2     |
 |   4    |  5   |  PCIe1      |
 |   5    |  5   |  USB3 HOST1 |
 -------------------------------
PCIe Ref. Clock Buffer Control is 0xf00015bf, setting to 0xf00015bf
SOC_CONTROL_REG1 is 0xf00015bf, setting to 0x0707c0f3
PCIe, Idx 0: detected no link
PCIe, Idx 1: detected no link
High speed PHY - Ended Successfully
mv_ddr: mv_ddr-armada-17.06.1-g07f8294 (Oct  8 2018 - 12:59:22)
DDR4 Training Sequence - Switching XBAR Window to FastPath Window
mv_ddr: completed successfully

 __   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_ 
        | | | |___|  _ \ / _ \ / _ \| __| 
        | |_| |___| |_) | (_) | (_) | |_ 
         \___/    |____/ \___/ \___/ \__| 
 ** LOADER **


U-Boot 2013.01-02879-geb5cbf6642 (Oct 08 2018 - 12:59:19) Marvell version: devel-17.06.0

Board: Rogue-1
SoC:   MV88F6820 Rev B0
       running 2 CPUs
CPU:   ARM Cortex A9 MPCore (Rev 1) LE
       CPU 0
       CPU    @ 1600 [MHz]
       L2     @ 800 [MHz]
       TClock @ 250 [MHz]
       DDR4    @ 800 [MHz]
       DDR4 32 Bit Width,FastPath Memory Access, DLB Enabled, ECC Disabled
DRAM:  2 GiB
MMC:   mv_sdh: 0
DBG: Calling spi_flash_probe from env_relocate_spec()
SF: Probing bus 0 cs 0 @ 20000000Hz mode 3
SF: Detected W25Q32JV with page size 4 KiB, total 4 MiB
PCI-e 0: Detected No Link.
PCI-e 1: Detected No Link.
USB2.0 0: Host Mode
USB3.0 1: Host Mode

Map:   Code:			0x7fedc000:0x7ff9741c
       BSS:			0x7ffef600
       Stack:			0x7f4cbf20
       Heap:			0x7f4cc000:0x7fedc000
       U-Boot Environment:	0x00100000:0x00110000 (SPI)

Board configuration detected:
Net:   
|  port  | Interface | PHY address  |
|--------|-----------|--------------|
| egiga0 |   RGMII   |     0x00     |
| egiga1 |   RGMII   |     0x01     |
| egiga2 |   SGMII   |   In-Band    |
egiga0 [PRIME], egiga1, egiga2
Hit any key to stop autoboot:  0 
reading ubldr.bin
228648 bytes read in 10 ms (21.8 MiB/s)
## Starting application at 0x00200000 ...
Consoles: U-Boot console  
Compatible U-Boot API signature found @0x7f4dc280

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
console comconsole is invalid!
no valid consoles!
Available consoles:
    uboot
/boot/kernel/kernel text=0xa8d62c data=0x11d47b4 data=0x0+0x54000 syms=[0x4+0xa8f40+0x4+0xf376a]
/
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...               
/boot/dtb/armada-385-80300-0148-G00-X100.dtb size=0x60ed
Loaded DTB from file 'armada-385-80300-0148-G00-X100.dtb'.
Kernel entry at 0x400180...
Kernel args: (null)
SOC: Marvell 88F6820, TClock 250MHz, Frequency 1600MHz
  Instruction cache prefetch enabled, data cache prefetch disabled
---<<BOOT>>---
Copyright (c) 1992-2020 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.2-STABLE c1120650645f(plus-RELENG_21_02) pfSense-SG-3100 arm
FreeBSD clang version 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611aa2)
CPU: ARM Cortex-A9 r4p1 (ECO: 0x00000000)
CPU Features: 
  Multiprocessing, Thumb2, Security, VMSAv7, Coherent Walk
Optional instructions: 
  UMULL, SMULL, SIMD(ext)
LoUU:2 LoC:2 LoUIS:2 
Cache level 1:
 32KB/32B 4-way data cache WB Read-Alloc Write-Alloc
 32KB/32B 4-way instruction cache Read-Alloc
real memory  = 2147479552 (2047 MB)
avail memory = 2071031808 (1975 MB)
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
arc4random: no preloaded entropy cache
ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc014deb0, 0) error 1
ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc014df60, 0) error 1
iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_bss_fw, 0xc0156f50, 0) error 1
iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_ibss_fw, 0xc0157000, 0) error 1
iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_monitor_fw, 0xc01570b0, 0) error 1
ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_bss_fw, 0xc014de00, 0) error 1
wlan: mac acl policy registered
random: entropy device external interface
[ath_hal] loaded
ofwbus0: <Open Firmware Device Tree>
simplebus0: <Flattened device tree simple bus> on ofwbus0
simplebus1: <Flattened device tree simple bus> on simplebus0
l2cache0: <PL310 L2 cache controller> mem 0x8000-0x8fff on simplebus1
l2cache0: cannot allocate IRQ, not using interrupt
l2cache0: Part number: 0x3, release: 0x9
l2cache0: L2 Cache enabled: 1024KB/32B 16 ways
gic0: <ARM Generic Interrupt Controller> mem 0xd000-0xdfff,0xc100-0xc1ff on simplebus1
gic0: pn 0x39, arch 0x1, rev 0x2, implementer 0x43b irqs 192
mpic0: <Marvell Integrated Interrupt Controller> mem 0x20a00-0x20ccf,0x21070-0x210c7 irq 17 on simplebus1
gpio0: <Marvell Integrated GPIO Controller> mem 0x18100-0x1813f,0x181c0-0x181c7 irq 9,10,11,12 on simplebus1
gpio0: 4 IRQs available
gpio0: Disable interrupts (offset = 0 + EDGE(0x18)
gpio0: Disable interrupts (offset = 0 + LEV(0x1C))
gpio0: Setup intr 0
gpio0: Setup intr 1
gpio0: Setup intr 2
gpio0: Setup intr 3
gpio0: Clear int status (offset = 0)
gpiobus0: <GPIO bus> on gpio0
gpio1: <Marvell Integrated GPIO Controller> mem 0x18140-0x1817f,0x181c8-0x181cf irq 13,14,15,16 on simplebus1
gpio1: 4 IRQs available
gpio1: Disable interrupts (offset = 0 + EDGE(0x18)
gpio1: Disable interrupts (offset = 0 + LEV(0x1C))
gpio1: Setup intr 0
gpio1: Setup intr 1
gpio1: Setup intr 2
gpio1: Setup intr 3
gpio1: Clear int status (offset = 0)
gpiobus1: <GPIO bus> on gpio1
mp_tmr0: <ARM MPCore Timers> mem 0xc200-0xc21f irq 3 on simplebus1
Timecounter "MPCore" frequency 800000000 Hz quality 800
mp_tmr1: <ARM MPCore Timers> mem 0xc600-0xc61f irq 4 on simplebus1
Event timer "MPCore" frequency 800000000 Hz quality 1000
twsi0: <Marvell Integrated I2C Bus Controller> mem 0x11000-0x1101f irq 5 on simplebus1
iicbus0: <OFW I2C bus> on twsi0
iic0: <I2C generic I/O> on iicbus0
gpio2: <NXP PCA9552 LED driver> at addr 0xc0 on iicbus0
device_attach: gpio2 attach returned 6
gpio2: <ISSI IS31FL3199 9 channel light effect LED driver> at addr 0xce on iicbus0
gpiobus2: <OFW GPIO bus> on gpio2
gpioc2: <GPIO controller> on gpio2
uart0: <16550 or compatible> mem 0x12000-0x120ff irq 7 on simplebus1
uart0: console (-1,n,8,1)
uart1: <16550 or compatible> mem 0x12100-0x121ff irq 8 on simplebus1
gpioc0: <GPIO controller> on gpio0
gpioc1: <GPIO controller> on gpio1
wdt0: <Marvell Watchdog Timer> mem 0x20300-0x20333,0x20704-0x20707,0x18260-0x18263 irq 24,25 on simplebus1
pmsu0: <Power Management Service Unit> mem 0x22000-0x22fff on simplebus1
mvneta0: <NETA controller> mem 0x30000-0x33fff irq 26 on simplebus1
mvneta0: version is 10
mvneta0: Ethernet address: 00:08:a2:12:47:cf
miibus0: <MII bus> on mvneta0
mv88e151x0: <Marvell 88E1512 Gigabit PHY> PHY 1 on miibus0
mv88e151x0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseSX, 1000baseSX-FDX, auto
mvneta1: <NETA controller> mem 0x34000-0x37fff irq 27 on simplebus1
mvneta1: version is 10
mvneta1: Ethernet address: 00:08:a2:12:47:d0
mdio0: <MDIO> on mvneta1
e6000sw0: <Marvell 88E6141> on mdio0
e6000sw0: single-chip addressing mode
e6000sw0: PHY at port 1
miibus1: <MII bus> on e6000sw0
e1000phy0: <Marvell 88E1000 Gigabit PHY> PHY 17 on miibus1
e1000phy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
e6000sw0: PHY at port 2
miibus2: <MII bus> on e6000sw0
e1000phy1: <Marvell 88E1000 Gigabit PHY> PHY 18 on miibus2
e1000phy1:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
e6000sw0: PHY at port 3
miibus3: <MII bus> on e6000sw0
e1000phy2: <Marvell 88E1000 Gigabit PHY> PHY 19 on miibus3
e1000phy2:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
e6000sw0: PHY at port 4
miibus4: <MII bus> on e6000sw0
e1000phy3: <Marvell 88E1000 Gigabit PHY> PHY 20 on miibus4
e1000phy3:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
e6000sw0: CPU port at 5
e6000sw0: fixed port at 5
e6000sw0: switch is ready.
etherswitch0: <Switch controller> on e6000sw0
mvneta2: <NETA controller> mem 0x70000-0x73fff irq 28 on simplebus1
mvneta2: version is 10
mvneta2: Ethernet address: 00:08:a2:12:47:d1
miibus5: <MII bus> on mvneta2
mv88e151x1: <Marvell 88E1512 Gigabit PHY> PHY 0 on miibus5
mv88e151x1:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseSX, 1000baseSX-FDX, auto
ehci0: <Marvell Integrated USB 2.0 controller> mem 0x58000-0x584ff irq 29 on simplebus1
usbus0: EHCI version 1.0
usbus0 on ehci0
cesa0: <Marvell Cryptographic Engine and Security Accelerator> mem 0x90000-0x9ffff irq 30,31 on simplebus1
rtc0: <Marvell Integrated RTC> mem 0xa3800-0xa381f,0x184a0-0x184ab irq 32 on simplebus1
rtc0: registered as a time-of-day clock, resolution 1.000000s
ahci0: <Marvell AHCI Controller> mem 0xa8000-0xa9fff irq 33 on simplebus1
ahci0: AHCI v1.00 with 2 6Gbps ports, Port Multiplier supported with FBS
ahci0: quirks=0x200010<2CH,MRVL_SR_DEL>
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
armada_thermal0: <Armada380 Thermal Control> mem 0xe4078-0xe407b,0xe4070-0xe4077 on simplebus1
sdhci_fdt0: <ARMADA38X SDHCI controller> mem 0xd8000-0xd8fff,0xdc000-0xdc0ff,0x18454-0x18457 irq 36 on simplebus1
sdhci_fdt0: 1 slot(s) allocated
xhci0: <Marvell Integrated USB 3.0 controller> mem 0xf8000-0xfbfff,0xfc000-0xfffff irq 38 on simplebus1
xhci0: 32 bytes context size, 32-bit DMA
usbus1 on xhci0
cesa1: <Marvell Cryptographic Engine and Security Accelerator> mem 0x90000-0x9ffff irq 39,40 on simplebus1
spi0: <Marvell SPI controller> mem 0xf001000000010600-0xf00100000001064f irq 1 on simplebus0
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
cpu1: <Open Firmware CPU> on cpulist0
cryptosoft0: <software crypto>
Timecounters tick every 1.000 msec
mvneta1: link state changed to UP
spibus0: <OFW SPI bus> on spi0
mx25l0: <M25Pxx Flash Family> at cs 0 mode 0 on spibus0
mx25l0: device type w25q32jv, size 4096K in 64 sectors of 64K, erase size 4K
Release APs
e6000sw0port1: link state changed to DOWN
usbus0: e6000sw0port2: link state changed to DOWN
480Mbps High Speed USB v2.0
e6000sw0port3: link state changed to DOWN
usbus1: e6000sw0port4: link state changed to DOWN
5.0Gbps Super Speed USB v3.0
ugen0.1: <Marvell EHCI root HUB> at usbus0
uhub0: <Marvell EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
ugen1.1: <Marvell XHCI root HUB> at usbus1
uhub1: <Marvell XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1
arc4random: no preloaded entropy cache
Trying to mount root from ufs:/dev/diskid/DISK-11298DFEs2a [rw,noatime]...
Root mount waiting for: usbus0 usbus1
uhub1: 2 ports with 2 removable, self powered
mmc0: <MMC/SD bus> on sdhci_fdt0
mmcsd0: 8GB <MMCHC Q2J55L 1.0 SN 11298DFE MFG 07/2020 by 19 0x004e> at mmc0 50.0MHz/8bit/65535-block
mmcsd0boot0: 2MB partition 1 at mmcsd0
mmcsd0boot1: 2MB partition 2 at mmcsd0
mmcsd0rpmb: 4MB partition 3 at mmcsd0
uhub0: 1 port with 1 removable, self powered
mountroot: waiting for device /dev/diskid/DISK-11298DFEs2a...
WARNING: / was not properly dismounted
Configuring crash dumps...
No suitable dump device was found.
** SU+J Recovering /dev/diskid/DISK-11298DFEs2a
** Reading 11436032 byte journal from inode 4.
** Building recovery table.
** Resolving unreferenced inode list.
** Processing journal entries.
** 4152 journal records in 275968 bytes for 48.14% utilization
** Freed 0 inodes (0 dirs) 12 blocks, and 0 frags.

***** FILE SYSTEM MARKED CLEAN *****
Filesystems are clean, continuing...
Mounting filesystems...
random: read_random_uio unblock wait
random: unblocking device.

        __
 _ __  / _|___  ___ _ __  ___  ___      _
| '_ \| |_/ __|/ _ \ '_ \/ __|/ _ \   _| |_
| |_) |  _\__ \  __/ | | \__ \  __/  |_   _|
| .__/|_| |___/\___|_| |_|___/\___|    |_|
|_|


Welcome to Netgate pfSense Plus 21.02.2-RELEASE...

...ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/lib/engines /usr/local/lib/compat/pkg /usr/local/lib/ipsec /usr/local/lib/perl5/5.32/mach/CORE
Soft Float compatibility ldconfig path:
done.
panic: softdep_setup_inomapdep: dependency 0xde76a500 for newinode already exists
cpuid = 0
time = 4261411844
Uptime: 6s
Automatic reboot in 15 seconds - press a key on the console to abort
--> Press a key on the console to reboot,
--> or switch off the system now.
                  1 Reply Last reply Reply Quote 0
                  • G
                    ggpf @stephenw10
                    last edited by

                    @stephenw10

                    One more info I open the Netgate and I change the battery for a good new one.
                    I test it.

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

                      Ok great so the first thing to try is to boot into single user mode and run a manual FSCK:
                      https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-check.html#manual-filesystem-check

                      However given that are running such an old version anyway it may be easier to just reinstall 23.09.1 clean.
                      Open a ticket with us to get the install image:
                      https://www.netgate.com/tac-support-request

                      Steve

                      G 1 Reply Last reply Reply Quote 0
                      • G
                        ggpf @stephenw10
                        last edited by

                        @stephenw10 said in SG-3100 no reboot:

                        https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-check.html#manual-filesystem-check

                        It works much better. I get this, and I would like to get menu of PFsense on my GTKTerm
                        to get wich IP address are assigned to LAN1 interface.
                        But after "Boot Complete" I don't know how to get Menu of PFsense I know much the web configurator. ;)

                        Regards.
                        Gils.

                        Welcome to Netgate pfSense Plus 21.02.2-RELEASE...

                        ...ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg /usr/lib/engines /usr/local/lib/compat/pkg /usr/local/lib/ipsec /usr/local/lib/perl5/5.32/mach/CORE
                        Soft Float compatibility ldconfig path:
                        done.
                        ERROR: It was not possible to identify which pfSense kernel is installed
                        External config loader 1.0 is now starting...
                        Launching the init system....... done.
                        Initializing.................. done.
                        Starting device manager (devd)...done.
                        Loading configuration......done.
                        ..............................Updating configuration...done.
                        Checking config backups consistency...done.
                        Setting up extended sysctls...done.
                        Setting timezone...done.
                        Configuring looplo0: link state changed to UP
                        back interface...done.
                        Starting syslog...done.
                        Starting Secure Shell Services...done.
                        Configuring switch...done.
                        Setting up interfaces microcode...done.
                        Starting PC/SC Smart Card Services...done.
                        Configuring loopback interface...done.
                        Creating wireless clone interfaces...done.
                        Configuring LAGG interfaces...done.
                        Configuring VLAN interfaces...done.
                        Configuring QinQ interfaces...done.
                        Configuring LAN interface...done.
                        Configuring WAN interface...done.
                        Configuring IPsec VTI interfaces...done.
                        Configuring CARP settings...done.
                        Syncing OpenVPN settings...done.
                        Configuring firewall......done.
                        Starting PFLOG...done.
                        Setting up gateway monitors...done.
                        Setting up static routes...done.
                        Setting up DNSs...
                        Starting DNS Resolver...done.
                        Synchronizing user settings...done.
                        Starting webConfigurator...done.
                        Configuring CRON...done.
                        Starting NTP Server...done.
                        Starting DHCP service...done.
                        Starting DHCPv6 service...done.
                        Configuring firewall......done.
                        Generating RRD graphs...done.
                        Starting watchdog daemon...done.
                        Starting syslog...done.
                        Starting CRON... done.
                        ERROR: It was not possible to identify which pfSense kernel is installed
                        Netgate pfSense Plus 21.02.2-RELEASE arm Mon Apr 12 07:50:07 EDT 2021
                        Bootup complete

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

                          I would recommend just re-installing clean. 21.02 is a very old version and trying to upgrade to 23.09.1 from that will require several steps.

                          Make sure you have a backup on the config.

                          Steve

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