SG-3100 Recovery issue after adding m.2 ssd)



  • I installed an Adata 128gb m.2 ssd (https://www.adata.com/en/specification/440). The SG-3100 continued to boot up normally with the built-in memory. I let it boot up and checked the SMART status and it's indeed recognized there. Any ideas on what the issue could be? Thanks in advance.

    smartctl 6.6 2017-11-05 r4594 [FreeBSD 11.2-RELEASE-p10 arm] (local build)
    Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

    === START OF INFORMATION SECTION ===
    Device Model: ADATA SU800NS38
    Serial Number: 2J292000XXXX
    LU WWN Device Id: 0 000000 000000000
    Firmware Version: R0427AC
    User Capacity: 128,035,676,160 bytes [128 GB]
    Sector Size: 512 bytes logical/physical
    Rotation Rate: Solid State Device
    Form Factor: M.2
    Device is: Not in smartctl database [for details use: -P showall]
    ATA Version is: ACS-3 T13/2161-D revision 5
    SATA Version is: SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
    Local Time is: Thu Oct 24 22:44:05 2019 EDT
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled

    When I try to run a recovery to reinstall pfsense to the SSD, I'm getting a USB error and it just reboots. Here's the logs from console:
    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
    Marvell>> run recovery
    (Re)start USB...
    USB0: mvBoardUsbVbusSet: gppNo = 35
    Port (usbActive) : 1 Interface (usbType = 3) : USB XHCI 1.00
    scanning bus 0 for devices...
    Couldn't reset port 1
    1 USB Device(s) found
    Bad detection, need a second reset...
    USB0: mvBoardUsbVbusSet: gppNo = 35
    Port (usbActive) : 1 Interface (usbType = 3) : USB XHCI 1.00
    scanning bus 0 for devices... 2 USB Device(s) found
    scanning usb for storage devices... WARN halted endpoint, queueing URB anyway.
    Unexpected XHCI event TRB, skipping... (7f4dd130 00000000 13000000 01008401)
    BUG: failure at xhci-ring.c:500/abort_td()!
    BUG!
    resetting ...



  • Is this the first time using the USB port? Looks like a bad USB stick.



  • Yes, I've never used the USB port on the SG-3100 before. I already tried to reimage the USB stick but I'll grab another one and try it again. Any ideas on why it's still booting up on internal memory with m.2 installed?
    Thx!



  • @nonvtec
    To make full use of the ssd, here’s what i had to do.

    1. in gui, make a full config backup of what is working now (to a computer)
    2. hookup fw to serial console
    3. (optional) use CLI to reset the firewall to factory default
    4. write the special pfsense image file to usb, then plug into fw usb port.
    5. boot fw and choose recovery (My memory is a bit foggy here. Search this forum.)
    6. install the image on the SSD device
    7. once functional, remove usb device
    8. log into gui and restore previous backup.

    Hope that helps.


  • Netgate Administrator

    The boot device is determined by the uboot envs. When you reinstall to the m.2 drive it re-writes those to make it boot from m.2. You can manually switch them but there's no point since you need to boot and install from USB anyway.

    That is failing just trying to detect the USB stick as a storage device. It would do that whether or not the image is on there correctly. Use a different USB memory stick.

    Steve



  • Thanks for the help folks! I'm up and running on the m.2 now, it didn't like my Kingston USB3 stick so I switched it out and it's good now.


Log in to reply