Rebooted SG-3100 / Multiple Errors on reboot
-
Hi - I am running 2.4.5p1 on my SG-3100. I had tried to upgrade a few weeks ago, but had issues and so reinstalled 2.4.5p1 on 3/4/21. It's been working fine. I was experiencing some slow internet, so was rebooting all hardware.
When the Sg-3100 rebooted, I could not access it, so I checked the CLI. It is showing multiple errors on the boot. See below.
spoilerBootROM - 1.73 Booting from SPI flash 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, 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 (Aug 11 2017 - 13:12:46) DDR4 Training Sequence - Switching XBAR Window to FastPath Window mv_ddr: completed successfully BootROM: Image checksum verification PASSED __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** LOADER ** U-Boot 2013.01-02873-g5e4ac3c (Aug 11 2017 - 13:12:40) 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 N25Q128 with page size 64 KiB, total 16 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:0x7ff975a8 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 277020 bytes read in 17 ms (15.5 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 (Thu Feb 13 14:37:14 EST 2020 root@buildbot1-nyi.netgate.com) 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 <unknown> devices... Checking unit=0 slice=<auto> partition=<auto>... Checking unit=1 slice=<auto> partition=<auto>... 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 data=0x19e4818+0x777e8 sdhci_transfer_data: Error detected in status(0x108000)! disk2: real size != size elf32_loadimage: read failed can't load file '/boot/kernel/kernel': input/output error Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... disk2: real size != size disk2: real size != size disk2: real size != size can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed help. loader> Board: Rogue-1 Board: not found loader> SoC: MV88F6820 Rev A0 SoC: not found loader> running 2Core (Rev 1) LE running not found loader> CPU 0 CPU not found loader>
So the first error is "console comconsole is invalid!"
Then there are disk errors.Do I need to reinstall, or is there any troubleshooting available?
Thanks!
-
I did a reinstall of 2.4.5-p1, I still had the image on my USB.
Still, if anyone can share insight as to why a simple reboot would brick the install, it would be helpful. I don't want to have to reinstall every time the SG-3100 reboots.
-
@newberger It could be corrupted partition or boot method error. Just fresh install pfsense. A lot user upgraded to 2.5.1 pfsense without rebooting the device first.