Knowledge Search


×
 

[SRX] Stuck at boot stage 3 after attempting a Routing Engine BIOS (U-boot) firmware upgrade

  [KB34120] Show Article Properties


Summary:

This article explains the recommended U-boot upgrade method for SRX devices to reduce encountering 'boot stage3' errors after Routing Engine BIOS firmware upgrades.

Symptoms:

The following messages are reported on the console:

SRX_320 board revision major:1, minor:5, serial #: xxxxxxxxxxxxxx
OCTEON CN7020-AAP pass 1.2, Core clock: 1200 MHz, IO clock: 600 MHz, DDR clock: 667 MHz (1334 Mhz DDR)
DRAM: 4 GiB
Clearing DRAM...... done
Using default environment
 
SF: Detected SF with page size 256 Bytes, erase size 64 KiB, total 8 MiB
Found csrx_320 (SPI stage 2) corrupted image at offset 0x80000, continuing search
Could not find stage 3 bootloader
bootjuniperstage3 - Load and execute the stage 3 bootloader
 
Usage:
bootjuniperstage3 Load and execute the stage 3 bootloader
Hit any key to stop autoboot:  0
SF: Detected SF with page size 256 Bytes, erase size 64 KiB, total 8 MiB
Found corrupted image at offset 0x80000, continuing search
Could not find stage 3 bootloader
bootjuniperstage3 - Load and execute the stage 3 bootloader
 
Usage:
bootjuniperstage3 Load and execute the stage 3 bootloader
srx_320 (SPI stage 2)
 
bootjuniperstage3 Load and execute the stage 3 bootloader



It has been observed that under the following conditions that the SRX might be stuck in boot stage 3 due to a corruption encountered during the BIOS upgrades:

  • Routing Engine BIOS has been upgraded on the device from the CLI:
    > request system firmware upgrade re bios
  • The backup BIOS is upgraded first and then the upgrade of the primary BIOS (with or without reboot between upgrades).
Solution:

SRX300 devices provide for dual BIOS allowing the backup BIOS to attempt recovery of primary BIOS.

Using BIOS upgrade steps provided in the KB19452 - [SRX] How to upgrade U-Boot via the CLI, it is highly recommended to upgrade the primary BIOS first to validate a successful upgrade before performing an update on the backup BIOS,

Use the following commands to check for the BIOS CRC errors before any reboot.

For Primary:

root% bootupgrade -c u-boot

For Backup BIOS:

root% bootupgrade -c -s u-boot 

If you encounter bootup errors after the BIOS upgrade:

  • Issue a hard reboot of the device.
  • If a hard reboot does NOT restore this situation, open a case with your technical support representative.

 

Related Links: