Support Center > Search Results > SecureKnowledge Details
How to perform a fresh/clean install of firmware on Embedded GAIA appliances via USB Technical Level
Solution

To perform a fresh/clean install of firmware on Embedded GAIA appliances via USB, the USB must use a FAT32 file system.

  1. Copy the desired firmware image onto the USB (not in subfolders and not with other firmware images present).

  2. Insert the USB into "USB1" into the front of the appliance.

  3. Wait for the "USB1" LED light to activate, indicating that the USB was detected.

  4. Reboot the appliance via the WebUI, the SSH command #reboot, or by power cycling the appliance.

    During the boot process, the appliance will detect the USB and firmware image.
    The appliance will perform a reset to factory defaults, followed by a fresh install of the selected firmware version.

Note: You may need to use Ctrl-C to interrupt the bootloader and select the relevant option.

    Note: This procedure erases the existing image and settings.

    If this method fails, connect via console and check for error messages.

    Example of successful image verification:
    System Started...
    /sys/devices/soc.0/fd840000.pcie-external2/pci0002:00/0002:00:00.0/0002:01:00.0/usb2/2-1/2-1:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
    rm: cannot remove '/mnt/usb1/.read_only': No such file or directory
    Verifying image : /mnt/usb1/fw1_sx_dep_R77_990172392_20.img
    Installing image : /mnt/usb1/fw1_sx_dep_R77_990172392_20.img
    Upgrade log : /mnt/usb1/usb_image_upgrade_00-1C-7F-73-0A-F2.log

    Example of failed image verification:
    System Started...
    /sys/devices/soc.0/fd840000.pcie-external2/pci0002:00/0002:00:00.0/0002:01:00.0/usb2/2-1/2-1:1.0/host1/target1:0:0/1:0:0:0/block/sdb/sdb1
    /sys/devices/soc.0/fd840000.pcie-external2/pci0002:00/0002:00:00.0/0002:01:00.0/usb1/1-2/1-2:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
    Image verification failed: /mnt/sd/fw1_sx_dep_R77_990172392_20.img
    Image verification failed: /mnt/sd/fw1_sx_dep_R77_990172392_20.img

    In the failed example, a SD card was causing the issue. Removing it solved the problem.

    This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

    Give us Feedback
    Please rate this document
    [1=Worst,5=Best]
    Comment