Junos OS

Expand all | Collapse all

Juniper EX3400 stuck in boot loop after upgrade

  • 1.  Juniper EX3400 stuck in boot loop after upgrade

    Posted 04-25-2017 07:07

    Hii All,

     

    after trying to update Juniper Ex3400 to latest jtac firmware, switch stuck in a boot loop.

     

    Anyone have any ideas how to get to the loader ant boot it from usb?

    Console output:

     

    U-Boot 2016.01-rc1 (May 23 2016 - 08:45:58 -0700) VERSION=1.2.0

    DRAM:  AVS: 0x0
    DEV ID = 0xdc14
    SKU ID = 0xb547
    DDR type: DDR3
    MEMC 0 DDR speed = 750MHz
    PHY revision version: 0x00044006
    SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
    In:    serial
    Out:   serial
    Err:   serial
    FLASH bank: 1
    Board: EX3400-48T
    Base MAC: 28A24B80CC62
    Net:   bcmiproc_eth-0
    Last Reset Reason: 8
    Hit ^C to stop autoboot:  0
    SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
    device 0 offset 0x3c0000, size 0x10000
    SF: 65536 bytes @ 0x3c0000 Read: OK

    ## Checking Image at 61000000 ...
       Legacy image found
       Image Name:   Juniper U-Boot Script File
       Image Type:   ARM Unknown OS Script (uncompressed)
       Data Size:    1803 Bytes = 1.8 KiB
       Load Address: 00000000
       Entry Point:  00000000
       Contents:
          Image 0: 1795 Bytes = 1.8 KiB
       Verifying Checksum ... OK
    ## Executing script at 61000000
    Setting bus to 0
    SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB, mapped at 00000a30
    device 0 offset 0x140000, size 0x140000
    SF: 1310720 bytes @ 0x140000 Read: OK
    6113fffc: f1c1fb43                               C...
    crc32 for 61000000 ... 6113ffff ==> 43fbc1f1
    Total of 1 word(s) were the same
    starting USB...
    USB0:   phy ctrl 01d36440
    Initial usb2h clock is: 000003fc
    Initial usb2h clock is: 000003fd
    iClk = 00000078, USBClk = 01536440

    Bring usb2h_out of reset.......
    usb2_reset_state is set and now it is: 00000000
    usb2_reset_state is: 00000000
    USB EHCI 1.00
    scanning bus 0 for devices... 3 USB Device(s) found
           scanning usb for storage devices... 1 Storage Device(s) found
    SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB, mapped at 00000088
    ## Starting application at 0x00000074 ...
    Consoles: U-Boot console  

    FreeBSD/armv6 U-Boot loader, Revision 1.2
    (fbsd-builder@svl-bsdx-05.juniper.net, Wed May 18 12:32:06 PDT 2016)

    DRAM: 2048MB
    Number of U-Boot devices: 2
    U-Boot env: loaderdev not set, will probe all devices.
    Found U-Boot device: disk
      Probing all disk devices...
      Checking unit=0 slice=<auto> partition=<auto>... good.
    /
    Resetting...
    resetting ...


    U-Boot 2016.01-rc1 (May 23 2016 - 08:45:58 -0700) VERSION=1.2.0

    DRAM:  AVS: 0x0
    DEV ID = 0xdc14
    SKU ID = 0xb547
    DDR type: DDR3
    MEMC 0 DDR speed = 750MHz
    PHY revision version: 0x00044006
    SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB



  • 2.  RE: Juniper EX3400 stuck in boot loop after upgrade

     
    Posted 04-29-2017 03:37

    From the output it looks like you are not getting the options to stop at the boot loader which should be present.

     

    https://kb.juniper.net/InfoCenter/index?page=content&id=KB31462

     

    If you do have another switch, you can create a bootable USB using the snapshot to USB command.  When this is inserted into this switch and then powered up it should boot from USB before the internal media so you can regain control of the switch and reformat the internal media install from there.



  • 3.  RE: Juniper EX3400 stuck in boot loop after upgrade

    Posted 08-24-2018 05:19

    Same problem with EX2300-C.

    It was not a bright decision to put bootloader vars into a bootloader script file.

    To change currdev var you have to get to loader> prompt, and even inserting valid USB stick doesn't help.

    To get to loader prompt,

     

     

    setenv loaderdev usb1:0
    boot

     

    From loader prompt tftp --format is failing with 

    cannot open package (error 60)

     

    boot -s also failing (Enter full pathname of shell or RETURN for /bin/sh: ), supposedly something wrong with chroot.

     

    UPDATE: All 15.1X53-D59 images(tftp, USB install package+media) failed just as 15.1X53-D50, but 15.1X53-D58 USB install succeeded, however after install again a loaderdev override to usb0:0 was required.

    @Juniper please bring back normal QA/release testing.