SG 2100 - Fails after update and cannot reinstall PFsense
-
Hello,
after updating to the last version my PFsense, my SG2100 failed to reboot.
when trying to reinstall PFsense via usb recovery (with the image pfSense-plus-installer-24.06-BETA7-aarch64-20240614-1949), I have the following message :
I have changed my USB stick but no improvment
Please, what can I do to make it works ?
-
You are using Etcher, right, as describe in the pfSense documentation ?
You do use the correct firmware - 2100 is arm based ?
If that's an all yes, then I dono ... get a USB drive that works ? -
@Gertjan
Thank you for your replyyes to both.
I use Etcher (on MacOS and windows) and two different usb keys.I downloaded the image from Netgate store by picking up the ARM2100 image.
-
Be sure to do a full power cycle between attempts. If you see EHCI errors like that it can be a USB controller issue and that may not be reset by simply soft rebooting.
-
@stephenw10 than you for your answer. What do you mean by "full power cycle" ?
I opened a ticket on Netgate support, but they were not very helpful, only suggest to try another usbstick. So far I have tested 3 different USB stick.
One seems to work better but I am stuck here :AArch32 Media and VFP Features 0 = <FPRound,FPSqrt,FPDivide,DP VFPv3+v4,SP VFPv3+v4,AdvSIMD> AArch32 Media and VFP Features 1 = <SIMDFMAC,FPHP DP Conv,SIMDHP SP Conv,SIMDSP,SIMDInt,SIMDLS,FPDNaN,FPFtZ> CPU 1: ARM Cortex-A53 r0p4 affinity: 1 gic0: using for IPIs Release APs...done Trying to mount root from ufs:/dev/ufs/pfSense_Install [ro,noatime]... TCP_ratelimit: Is now initialized uhub0: 2 ports with 2 removable, self powered uhub1: 1 port with 1 removable, self powered mountroot: waiting for device /dev/ufs/pfSense_Install... e6000sw0port1: link state changed to DOWN e6000sw0port2: link state changed to DOWN e6000sw0port3: link state changed to DOWN e6000sw0port4: link state changed to DOWN Mounting from ufs:/dev/ufs/pfSense_Install failed with error 19. Loader variables: vfs.root.mountfrom=ufs:/dev/ufs/pfSense_Install vfs.root.mountfrom.options=ro,noatime Manual root filesystem specification: <fstype>:<device> [options] Mount <device> using filesystem <fstype> and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:zroot/ROOT/default cd9660:/dev/cd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) <empty line> Abort manual input mountroot> ? List of GEOM managed disk devices: mmcsd0boot1 mmcsd0boot0 mmcsd0 flash/ubootenv flash/uboot flash/spi0s.ubootenv flash/spi0s.uboot flash/spi0 mountroot> [A[B[B[Brandom: unblocking device. mmcsd0 Invalid file system specification. -
@benjaminSTW said in SG 2100 - Fails after update and cannot reinstall PFsense:
What do you mean by "full power cycle" ?
I mean pull the power plug to completely reset the USB controller/bus. We have seen uboot object to some USB devices and fail to detect them. Once that happens simply running 'reset' at the prompt is insufficient to clear the issue.
Do you have the full boot log? It's failing to see the USB device to mount the UFS root partition. You should see da0s1 etc in that list.
-
I did a full power cycle so I can "interrupt" the boot process and be able to "run usb reset" & run usbrecovery"
Please find the full log:
\[?25h|[?25h/[?25h-[?25h\[?25h|[?25ht[?25he[?25hx[?25ht[?25h=[?25h0[?25hx[?25h1[?25h4[?25h6[?25h1[?25h5[?25he[?25hc[?25h [?25h/[?25hˇ�TIM-1.0 WTMI-devel-1.0.0-1115f12 WTMI: system early-init SVC REV: 5, CPU VDD voltage: 1.225V NOTICE: Booting Trusted Firmware NOTICE: BL1: v1.5(release):ROGUE2-01.00.00.01-cpu1_2G-0-g06b570a8d (Marvell-release-1.3.0) NOTICE: BL1: Built : 14:34:11, Feb 7 2020 NOTICE: BL1: Booting BL2 NOTICE: BL2: v1.5(release):ROGUE2-01.00.00.01-cpu1_2G-0-g06b570a8d (Marvell-release-1.3.0) NOTICE: BL2: Built : 14:34:13, Feb 7 2020 NOTICE: BL1: Booting BL31 NOTICE: BL31: v1.5(release):ROGUE2-01.00.00.01-cpu1_2G-0-g06b570a8d (Marvell-release-1.3.0) NOTICE: BL31: Built : 14 U-Boot 2018.03-devel-1.2.0ROGUE2-01.00.00.02+ (Feb 07 2020 - 14:33:22 -0500) Model: Silicom Rogue-2 CPU 1200 [MHz] L2 800 [MHz] TClock 200 [MHz] DDR 750 [MHz] DRAM: 3.4 GiB Comphy chip #0: Comphy-0: SGMII1 3.125 Gbps Comphy-1: PEX0 2.5 Gbps Comphy-2: SATA0 6 Gbps PCIE-0: Link down MMC: sdhci@d8000: 0 Loading Environment from SPI Flash... mvebu_spi_ofdata_to_platdata: ofdata clock 200000000, frequency 20000000 SF: Detected w25q32bv with page size 256 Bytes, erase size 4 KiB, total 4 MiB OK Model: Silicom Rogue-2 Net: eth0: neta@30000 [PRIME], eth1: neta@40000 Hit any key to stop autoboot: 2 0 Marvell>> usb reset resetting USB... USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 2 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found Marvell>> usb reset run usbrecovery MMC erase: dev # 0, block # 0, count 4194304 ... 4194304 blocks erased: OK resetting USB... USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... EHCI timed out on TD - token=0x80008d80 USB device not accepting new address (error=22) 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found ** Bad device usb 0 ** Marvell>> run usbrecovery MMC erase: dev # 0, block # 0, count 4194304 ... 4194304 blocks erased: OK resetting USB... USB0: Register 2000104 NbrPorts 2 Starting the controller USB XHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 2 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found 17302 armada-3720-gti-doorkeeper.dtb 18022 armada-3720-netgate-1100.dtb 18022 armada-3720-sg1100.dtb 12944 armada-3720-netgate-2100.dtb 12944 armada-3720-sg2100.dtb .fseventsd/ 5 file(s), 1 dir(s) 12944 bytes read in 17 ms (743.2 KiB/s) 2097152 bytes read in 74 ms (27 MiB/s) ## Starting EFI application at 01000000 ... [18tScanning disk sdhci@d8000.blk... Scanning disk usb_mass_storage.lun0... Found 5 disks [?25h[2J >> FreeBSD EFI boot block Loader path: /boot/loader.efi Initializing modules: ZFS UFS Load Path: /\efi\boot\bootaa64.efi Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/USBClass(0,0,9,0,1)/USBClass(2009,16af,0,0,0)/HD(1,0x01,0,0x1,0x64000) Probing 5 block devices...not supported not supported not supported not supported better done ZFS found no pools UFS found 1 partition command args: -S115200 -D -[?25h---<<BOOT>>--GDB: current port: uart KDB: debugger backends: ddb gdb KDB: current backend: ddb Copyright (c) 1992-2024 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 15.0-CURRENT #0 installer-RELENG_24_06-n256324-d3763a473a3: Fri Jun 14 20:21:53 UTC 2024 root@freebsd:/var/jenkins/workspace/pfSense-installer-snapshots-24_06-main/obj/aarch64/BB6FIoLP/var/jenkins/workspace/pfSense-installer-snapshots-24_06-main/sources/FreeBSD-src-installer-RELENG_24_06/arm64.aarch64/sys/pfSense arm64 FreeBSD clang version 17.0.6 (https://github.com/llvm/llvm-project.git llvmorg-17.0.6-0-g6009708b4367) VT: init without driver. module scmi already present! real memory = 3602862080 (3435 MB) avail memory = 3467382784 (3306 MB) Starting CPU 1 (1) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs arc4random: WARNING: initial seeding bypassed the cryptographic random device because it was not yet seeded and the knob 'bypass_before_seeding' was enabled. 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, 0xffff0000002698f4, 0) error 1 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, 0xffff0000002699ac, 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, 0xffff000000269a64, 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, 0xffff000000269b1c, 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, 0xffff000000269bd4, 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, 0xffff000000269c8c, 0) error 1 random: entropy device external interface wlan: mac acl policy registered kbd0 at kbdmux0 ofwbus0: <Open Firmware Device Tree> simplebus0: <Flattened device tree simple bus> on ofwbus0 simplebus1: <Flattened device tree simple bus> on simplebus0 simple_mfd0: <Simple MFD (Multi-Functions Device)> mem 0x13800-0x138ff,0x13c00-0x13c1f on simplebus1 simple_mfd1: <Simple MFD (Multi-Functions Device)> mem 0x18800-0x188ff,0x18c00-0x18c1f on simplebus1 psci0: <ARM Power State Co-ordination Interface Driver> on ofwbus0 netgate0: <Netgate 2100> gic0: <ARM Generic Interrupt Controller v3.0> mem 0x1d00000-0x1d0ffff,0x1d40000-0x1d7ffff,0x1d80000-0x1d81fff,0x1d90000-0x1d91fff,0x1da0000-0x1dbffff irq 27 on simplebus1 gpio0: <Armada 37x0 North Bridge GPIO Controller> mem 0x13800-0x138ff,0x13c00-0x13c1f irq 28,29,30,31,32,33,34,35,36,37,38,39 on simple_mfd0 gpiobus0: <OFW GPIO bus> on gpio0 gpio1: <Armada 37x0 South Bridge GPIO Controller> mem 0x18800-0x188ff,0x18c00-0x18c1f irq 40,41,42,43,44 on simple_mfd1 gpiobus1: <OFW GPIO bus> on gpio1 gpiomdio0: <GPIO MDIO bit-banging Bus driver> at pins 21,23 on gpiobus1 gpiomdio0: MDC pin: 21, MDIO pin: 23 a37x0-xtal0: <Marvell Armada 3700 Oscillator> mem 0x13800-0x138ff,0x13c00-0x13c1f on simple_mfd0 generic_timer0: <ARMv8 Generic Timer> irq 0,1,2,3 on ofwbus0 Timecounter "ARM MPCore Timecounter" frequency 12500000 Hz quality 1000 Event timer "ARM MPCore Eventtimer" frequency 12500000 Hz quality 1000 a37x0_tbg0: <Marvell Armada 3700 time base generators> mem 0x13200-0x132ff on simplebus1 a37x0_nb_periph_driver0: <marvell,armada-3700-nb-periph-clock> mem 0x13000-0x130ff on simplebus1 a37x0_sb_periph_driver0: <marvell,armada-3700-sb-periph-clock> mem 0x18000-0x180ff on simplebus1 cpulist0: <Open Firmware CPU Group> on ofwbus0 cpu0: <Open Firmware CPU> on cpulist0 pmu0: <Performance Monitoring Unit> irq 4 on ofwbus0 spi0: <Armada 37x0 SPI controller> mem 0x10600-0x10fff irq 6 on simplebus1 iichb0: <Marvell Armada 37x0 IIC controller> mem 0x11000-0x11023 irq 7 on simplebus1 iicbus0: <OFW I2C bus> on iichb0 iic0: <I2C generic I/O> on iicbus0 iichb1: <Marvell Armada 37x0 IIC controller> mem 0x11080-0x110a3 irq 8 on simplebus1 iicbus1: <OFW I2C bus> on iichb1 iic1: <I2C generic I/O> on iicbus1 nxprtc0: <NXP PCF8563 RTC> at addr 0xa2 on iicbus1 gpio2: <ISSI IS31FL3199 9 channel light effect LED driver> at addr 0xce on iicbus1 gpiobus2: <OFW GPIO bus> on gpio2 gpioc2: <GPIO controller> on gpio2 uart0: <Marvell Armada 3700 UART> mem 0x12000-0x121ff irq 9,10,11 on simplebus1 uart0: console (115200,n,8,1) gpioc0: <GPIO controller> on gpio0 gpioc1: <GPIO controller> on gpio1 mvneta0: <NETA controller> mem 0x30000-0x33fff irq 14 on simplebus1 mvneta0: version is 10 miibus0: <MII bus> on gpiomdio0 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 mvneta0: Ethernet address: 90:ec:77:0d:e9:e8 mvneta1: <NETA controller> mem 0x40000-0x43fff irq 15 on simplebus1 mvneta1: version is 10 mdio0: <MDIO> on mvneta1 mdioproxy0: <MII/MDIO proxy, MDIO side> on mdio0 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 mvneta1: Ethernet address: 90:ec:77:0d:e9:e9 xhci0: <Generic USB 3.0 controller> mem 0x58000-0x5bfff irq 16 on simplebus1 xhci0: 32 bytes context size, 32-bit DMA usbus0 on xhci0 ehci0: <Marvell Integrated USB 2.0 controller> mem 0x5e000-0x5ffff irq 17 on simplebus1 usbus1: EHCI version 1.0 usbus1 on ehci0 sdhci_xenon0: <Armada Xenon SDHCI controller> mem 0xd8000-0xd82ff,0x17808-0x1780b irq 25 on simplebus1 mmc0: <MMC/SD bus> on sdhci_xenon0 ahci0: <AHCI SATA controller> mem 0xe0000-0xe1fff irq 26 on simplebus1 ahci0: AHCI v1.30 with 1 6Gbps ports, Port Multiplier supported with FBS ahcich0: <AHCI channel> at channel 0 on ahci0 pcib0: <Marvell Armada 3700 PCIe Bus Controller> mem 0xd0070000-0xd008ffff irq 5 on simplebus0 pcib0: link never came up pci0: <OFW PCI bus> on pcib0 armv8crypto0: <AES-CBC,AES-XTS,AES-GCM> 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 w25q32, size 4096K in 64 sectors of 64K, erase size 4K nxprtc0: registered as a time-of-day clock, resolution 0.015625s usbus0: 5.0Gbps Super Speed USB v3.0 usbus1: 480Mbps High Speed USB v2.0 ugen0.1: <Generic XHCI root HUB> at usbus0 uhub0 on usbus0 uhub0: <Generic XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 ugen1.1: <Marvell EHCI root HUB> at usbus1 uhub1 on usbus1 uhub1: <Marvell EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1 mmc0: Failed to set VCCQ for card at relative address 2 mmcsd0: 8GB <MMCHC DG4008 0.1 SN 44F82B12 MFG 02/2020 by 69 0x0000> at mmc0 50.0MHz/8bit/65535-block mmcsd0boot0: 4MB partition 1 at mmcsd0 mmcsd0boot1: 4MB partition 2 at mmcsd0 mmcsd0rpmb: 4MB partition 3 at mmcsd0 CPU 0: ARM Cortex-A53 r0p4 affinity: 0 Cache Type = <64 byte D-cacheline,64 byte I-cacheline,VIPT ICache,64 byte ERG,64 byte CWG> Instruction Set Attributes 0 = <CRC32,SHA2,SHA1,AES+PMULL> Instruction Set Attributes 1 = <> Instruction Set Attributes 2 = <> Processor Features 0 = <GIC,AdvSIMD,FP,EL3 32,EL2 32,EL1 32,EL0 32> Processor Features 1 = <> Memory Model Features 0 = <TGran4,TGran64,SNSMem,BigEnd,16bit ASID,1TB PA> Memory Model Features 1 = <8bit VMID> Memory Model Features 2 = <32bit CCIDX,48bit VA> Debug Features 0 = <DoubleLock,2 CTX BKPTs,4 Watchpoints,6 Breakpoints,PMUv3,Debugv8> Debug Features 1 = <> Auxiliary Features 0 = <> Auxiliary Features 1 = <> AArch32 Instruction Set Attributes 5 = <CRC32,SHA2,SHA1,AES+VMULL,SEVL> AArch32 Media and VFP Features 0 = <FPRound,FPSqrt,FPDivide,DP VFPv3+v4,SP VFPv3+v4,AdvSIMD> AArch32 Media and VFP Features 1 = <SIMDFMAC,FPHP DP Conv,SIMDHP SP Conv,SIMDSP,SIMDInt,SIMDLS,FPDNaN,FPFtZ> CPU 1: ARM Cortex-A53 r0p4 affinity: 1 gic0: using for IPIs Release APs...done Trying to mount root from ufs:/dev/ufs/pfSense_Install [ro,noatime]... TCP_ratelimit: Is now initialized uhub0: 2 ports with 2 removable, self powered uhub1: 1 port with 1 removable, self powered mountroot: waiting for device /dev/ufs/pfSense_Install... e6000sw0port1: link state changed to DOWN e6000sw0port2: link state changed to DOWN e6000sw0port3: link state changed to DOWN e6000sw0port4: link state changed to DOWN Mounting from ufs:/dev/ufs/pfSense_Install failed with error 19. Loader variables: vfs.root.mountfrom=ufs:/dev/ufs/pfSense_Install vfs.root.mountfrom.options=ro,noatime Manual root filesystem specification: <fstype>:<device> [options] Mount <device> using filesystem <fstype> and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:zroot/ROOT/default cd9660:/dev/cd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) <empty line> Abort manual input mountroot> ? List of GEOM managed disk devices: mmcsd0boot1 mmcsd0boot0 mmcsd0 flash/ubootenv flash/uboot flash/spi0s.ubootenv flash/spi0s.uboot flash/spi0 mountroot> [A[B[B[Brandom: unblocking device. mmcsd0 Invalid file system specification. mountroot> -
Hmm, still seems unhappy with that USB drive for some reason. Were both drives you tried the same? What are they?
-
@stephenw10
Thank you for your answer.I tested with 3 usb drives :
- SanDisk 64 Go Ultra Fit, USB 3.2 : Brand new
- SanDisk 16g ultra (compact flash connected with an adapter) : it is the new I always use to install other system; worked fine for the others one
- Kingston 16g datatraveler
the last one works a little better (the last logs correspond to this stick).
For the two former one, always stop at the beginning of the "run usbrecovery" process
https://forum.netgate.com/assets/uploads/files/1721909408972-capture-d-écran-2024-07-25-à-14.09.47.png -
Hmm, do you have anything smaller? Anything that's USB2?
When you see that EHCI time out error you should do a full power cycle before testing anything else.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.