Don't have CONSOLE cable, how do i connect to SG-3100...Three LEDs blinking during bootup
-
I am guessing the firmware is unable to mount any drives....pretty hopeless here....:(
I am thinking of reinstalling netgate 3100 image but i don't have the image either
Any help would be greatly appreciated.
jim
-
@caymann
Image: https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/reinstall-pfsense.htmlCable: you can get (or may have) a replacement cable, it's just USB: https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/connect-to-console.html#connect-a-usb-cable
-
@caymann
The cable is part of the system, and equally important as the the power brick.
There is no VGA/keyboard, so this cable is your entry point if there are any drive or NIC issues. -
Yeah, the console cable is a standard USB to USB-mini cable so if you don't already have one you should be able to get one locally.
Open a ticket with us to get the image:
https://www.netgate.com/tac-support-requestAnd, yes, if all 3 LEDs remain blinking blue that means boot never completes..
Steve
-
I purchased a cable and i am sharing the boot messages...still at 3 LEDs blinking
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 A0 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 9 ms (24.2 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=0x1b4 text=0x8a2778 text=0x1d79c8 data=0x11d55c8 data=0 x0+0x54000 syms=[0x4+0xac370+0x4+0xf86e9] - 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 0x400200... Kernel args: (null) SOC: Marvell 88F6820, TClock 250MHz, Frequency 1600MHz Instruction cache prefetch enabled, data cache prefetch disabled ---<<BOOT>>--- Copyright (c) 1992-2021 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.3-STABLE plus-RELENG_22_05-n202700-3ddaea61055 pfSense-3100 arm FreeBSD clang version 13.0.0 (git@github.com:llvm/llvm-project.git llvmorg-13.0. 0-0-gd7b669b3a303) 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: WARNING: initial seeding bypassed the cryptographic random device be cause it was not yet seeded and the knob 'bypass_before_seeding' was enabled. ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LI CENSE. ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /b oot/loader.conf. module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc013e640, 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, 0xc013e6f8, 0) error 1 iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LIC ENSE. iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /bo ot/loader.conf. module_register_init: MOD_LOAD (iwi_bss_fw, 0xc0146f60, 0) error 1 iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LI CENSE. iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /b oot/loader.conf. module_register_init: MOD_LOAD (iwi_ibss_fw, 0xc0147018, 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, 0xc01470d0, 0) error 1 ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LIC ENSE. ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /bo ot/loader.conf. module_register_init: MOD_LOAD (ipw_bss_fw, 0xc013e588, 0) error 1 wlan: mac acl policy registered random: entropy device external interface WARNING: Device "g_ctl" is Giant locked and may be deleted before FreeBSD 14.0. WARNING: Device "openfirm" is Giant locked and may be deleted before FreeBSD 14. 0. WARNING: Device "pci" is Giant locked and may be deleted before FreeBSD 14.0. [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 simp lebus1 gic0: pn 0x39, arch 0x1, rev 0x2, implementer 0x43b irqs 192 mpic0: <Marvell Integrated Interrupt Controller> mem 0x20a00-0x20ccf,0x21070-0x2 10c7 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 simp lebus1 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 iicbu s0 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-0x182 63 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:11:ff:94 miibus0: <MII bus> on mvneta0 mv88e151x0: <Marvell 88E1512 Gigabit PHY> PHY 1 on miibus0 mv88e151x0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 10 00baseT-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:11:ff:95 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, 100 0baseT-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, 100 0baseT-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, 100 0baseT-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, 100 0baseT-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:11:ff:96 miibus5: <MII bus> on mvneta2 mv88e151x1: <Marvell 88E1512 Gigabit PHY> PHY 0 on miibus5 mv88e151x1: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 10 00baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseSX, 1000baseSX-FDX, auto ehci0: <Marvell Integrated USB 2.0 controller> mem 0x58000-0x584ff irq 29 on sim plebus1 usbus0: EHCI version 1.0 usbus0 on ehci0 cesa0: <Marvell Cryptographic Engine and Security Accelerator> mem 0x90000-0x9ff ff irq 30,31 on simplebus1 rtc0: <Marvell Integrated RTC> mem 0xa3800-0xa381f,0x184a0-0x184ab irq 32 on sim plebus1 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,0x1 8454-0x18457 irq 36 on simplebus1 sdhci_fdt0: 1 slot(s) allocated xhci0: <Marvell Integrated USB 3.0 controller> mem 0xf8000-0xfbfff,0xfc000-0xfff ff irq 38 on simplebus1 xhci0: 32 bytes context size, 32-bit DMA usbus1 on xhci0 cesa1: <Marvell Cryptographic Engine and Security Accelerator> mem 0x90000-0x9ff ff irq 39,40 on simplebus1 spi0: <Marvell SPI controller> mem 0xf001000000010600-0xf00100000001064f irq 1 o n 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 Trying to mount root from ufs:/dev/ufsid/5ed6cbf94a28f210 [rw,noatime]... 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 Root mount waiting for: usbus0 CAM usbus1 uhub1: 2 ports with 2 removable, self powered mmc0: <MMC/SD bus> on sdhci_fdt0 mmcsd0: 8GB <MMCHC Q2J55L 1.0 SN 112ADCEB MFG 07/2020 by 19 0x004e> at mmc0 50.0 MHz/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 Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for: CAM Root mount waiting for:ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: <SanDisk X600 M.2 2280 SATA 128GB X6113012> ACS-4 ATA SATA 3.x device ada0: Serial Number 181702A01357 ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes) ada0: Command Queueing enabled ada0: 122104MB (250069680 512 byte sectors) CAM mountroot: waiting for device /dev/ufsid/5ed6cbf94a28f210... WARNING: / was not properly dismounted WARNING: /: mount pending error: blocks 0 files 5 random: unblocking device. Configuring crash dumps... No suitable dump device was found. ** SU+J Recovering /dev/ufsid/5ed6cbf94a28f210 ** Reading 7503872 byte journal from inode 4. ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. ** 29 journal records in 5632 bytes for 16.48% utilization ** Freed 7 inodes (1 dirs) 0 blocks, and 0 frags. ***** FILE SYSTEM MARKED CLEAN ***** Filesystems are clean, continuing... Mounting filesystems... -
@caymann said in Don't have CONSOLE cable, how do i connect to SG-3100...Three LEDs blinking during bootup:
WARNING: / was not properly dismounted
WARNING: /: mount pending error: blocks 0 files 5Even if the system has been marked clean, do have a look at this video :
How to Run a pfSense Software File System CheckThe video implies : never remove the power from the box without a proper shutdown.
The box seems to boot fine so no hardware issues.
What about salving a copy of the config, and do a clean re install, so you know everything will be fine. -
@gertjan said in Don't have CONSOLE cable, how do i connect to SG-3100...Three LEDs blinking during bootup:
Even if the system has been marked clean, do have a look at this video :
How to Run a pfSense Software File System CheckThis is the way.
https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-check.html
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.