SRX

 View Only
last person joined: 2 days ago 

Ask questions and share experiences about the SRX Series, vSRX, and cSRX.
  • 1.  Errors related to the SPI stage 3 bootloader

    This message was posted by a user wishing to remain anonymous
    Posted 14 days ago
    This message was posted by a user wishing to remain anonymous

    Hello , I am currently experiencing an issue with my Juniper SRX300 device.

    Upon booting, I encounter errors related to the SPI stage 3 bootloader.

    Below are the details of the messages displayed during the boot process, even if I click space bar(Hit any key to stop autoboot: 0): SPI stage 1 bootloader (Build time: Apr 26 2020 - 21:42:44) U-Boot 2013.07-JNPR-3.9 (Build time: Apr 26 2020 - 21:42:45) Octeon unique ID: 0bc00402007ca59e0502 N0.LMC0 Configuration Completed: 4096 MB SRX_300 board revision major:1, minor:9, serial #: CV5020AF1707 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 SF: Detected SF with page size 256 Bytes, erase size 64 KiB, total 8 MiB Found corrupted image at offset 0x68000, 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 0x68000, 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

    => #help bootjuniperstage3 - Load and execute the stage 3 bootloader bootstage3 - Load and execute the stage 3 bootloader echo - echo args to console eeprom - EEPROM sub-system env - environment handling commands fdt - flattened device tree utility commands go - start application at address 'addr' help - print command description/usage loadb - load binary file over serial line (kermit mode) loads - load S-Record file over serial line loadx - load binary file over serial line (xmodem mode) loady - load binary file over serial line (ymodem mode) md5sum - compute MD5 message digest printenv - print environment variables reset - Perform RESET of the CPU run - run commands in an environment variable saves - save S-Record file over serial line setenv - set environment variables sf - SPI flash sub-system sha1sum - compute SHA1 message digest sleep - delay execution for some time sspi - SPI utility command version - print monitor, compiler and linker version



  • 2.  RE: Errors related to the SPI stage 3 bootloader

    Posted 13 days ago

    Sounds like hard reset or contacting Juniper for this one:

    https://supportportal.juniper.net/s/article/SRX-Stuck-at-boot-stage-3-after-attempting-a-Routing-Engine-BIOS-U-boot-firmware-upgrade?language=en_US



    ------------------------------
    Nikolay Semov
    ------------------------------



  • 3.  RE: Errors related to the SPI stage 3 bootloader

    This message was posted by a user wishing to remain anonymous
    Posted 13 days ago
    This message was posted by a user wishing to remain anonymous

    Nikolay Semov, thank you for reaching out.

     I have seen that link before, but unfortunately, it doesn't address my specific issue.

    I've had similar situations where the device would freeze, and I would interrupt the boot process and upgrade the system, and that would fix the issue.

    However, this time I am stuck in the "=> #" field, which doesn't respond to any input at 'Hit any key to stop autoboot: 0'. It doesn't register anything and just keeps looping as it is. Below are the commands I can use, and 'request' is not among them.

    => #help
    bootjuniperstage3 - Load and execute the stage 3 bootloader
    bootstage3  - Load and execute the stage 3 bootloader
    echo        - echo args to console
    eeprom      - EEPROM sub-system
    env         - environment handling commands
    fdt         - flattened device tree utility commands
    go          - start application at address 'addr'
    help        - print command description/usage
    loadb       - load binary file over serial line (kermit mode)
    loads       - load S-Record file over serial line
    loadx       - load binary file over serial line (xmodem mode)
    loady       - load binary file over serial line (ymodem mode)
    md5sum      - compute MD5 message digest
    printenv    - print environment variables
    reset       - Perform RESET of the CPU
    run         - run commands in an environment variable
    saves       - save S-Record file over serial line
    setenv      - set environment variables
    sf          - SPI flash sub-system
    sha1sum     - compute SHA1 message digest
    sleep       - delay execution for some time
    sspi        - SPI utility command
    version     - print monitor, compiler and linker version




  • 4.  RE: Errors related to the SPI stage 3 bootloader

    Posted 13 days ago

    Perhaps the rule of thumb applies here that you cannot get past what seemingly looks like an operator type error. When I say operator I mean the => operator. If immediately after follows a 0 at some point we are sure that is an integer error. If it's having trouble recognizing ANY integer it is a sign of a hard error. At this point it will not process anything because it's an underlying problem. Yes at first glance it seems programmatic. But if it skips this part we are now thinking a disc write thing, but now we worry about hardware failure. From what ive seen these 300's just go blank. The biggest sign is that all the interfaces at the front will stay on. The link lights will stay on. That's toast.



    ------------------------------
    Adrian Aguinaga
    B.S.C.M. I.T.T. Tech
    (Construction Management)
    A.A.S. I.T.T. Tech
    (Drafting & Design)
    ------------------------------