SRX

Expand all | Collapse all

Cannot load SRX image from bootloader

Jump to Best Answer
  • 1.  Cannot load SRX image from bootloader

    Posted 09-04-2012 20:00

    Hi Everyone,

    Iam currently stuck with a SRX 210, which failed when I  tried to upgrade from 9.6 to 10.0.

    I followed the KB  http://kb.juniper.net/InfoCenter/index?page=content&id=KB14175&smlogin=true

    but this did not help.

    Iam getting stuck at db> prompt

     

    loader> install tftp://IPADDRESS OF TFPT SERVER/junos-srxsme-10.0R1.8-domestic.tgz
    /kernel data=0x90a784+0xc6a78 syms=[0x4+0x74120+0x4+0xa4230]
    Kernel entry at 0x801000d8 ...
    getbootinfo: magic 0x0 md 0x8173f000 memsize 0x4
    getbootinfo: boothowto 0x1000 kernend 0x81800000 memsize 1024MB i2cid 0x522 kernelname /kernel

    Platform Starting
    init regular console
    Initializing octeon watchdog
    GDB: debug ports: uart
    GDB: current port: uart
    KDB: debugger backends: ddb gdb
    KDB: current backend: ddb
    getmemsize: msgbufp[size=32768] = 0x8000cfe4
    Copyright (c) 1996-2009, Juniper Networks, Inc.
    All rights reserved.
    Copyright (c) 1992-2006 The FreeBSD Project.
    Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
            The Regents of the University of California. All rights reserved.
    JUNOS 10.0R1.8 #0: 2009-11-03 10:06:39 UTC
        builder@ormonth.juniper.net:/volume/build/junos/10.0/release/10.0R1.8/obj-octeon/bsd/sys/compile/JSRXNLE
    JUNOS 10.0R1.8 #0: 2009-11-03 10:06:39 UTC
        builder@ormonth.juniper.net:/volume/build/junos/10.0/release/10.0R1.8/obj-octeon/bsd/sys/compile/JSRXNLE
    real memory  = 1073741824 (1024MB)
    avail memory = 561143808 (535MB)
    cpuid: 0, btlb_cpumap:0xffffffff
    FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
    Initializing watchdog interupt

    Loading RT Fifo module.....
    Loaded RT Fifo module
    pmap_helper loaded (interface version 6, syscall 210)
    cpu0 on motherboard
    : CAVIUM's Octeon CPU Rev. 0.1 with no FPU implemented
            L1 Cache: I size 32kb(128 line), D size 8kb(128 line), sixty four way.
            L2 Cache: Size 128kb, ? way
    obio0 on motherboard
    uart0: <Octeon-16550 channel 0> on obio0
    uart0: console (9600,n,8,1)
    twsi0 on obio0
    dwc0: <Synopsis DWC OTG Controller Driver> on obio0
    usb0: DWC OTG Controller
    Using DMA mode
    Init: Port Power? op_state=1
    Init: Power Port (0)
    usb0: <USB Bus for DWC OTG Controller> on dwc0
    usb0: USB revision 2.0
    uhub0: vendor 0x0000 DWC OTG root hub, class 9/0, rev 2.00/1.00, addr 1
    uhub0: 1 port with 1 removable, self powered
    uhub1: vendor 0x0409 product 0x005a, class 9/0, rev 2.00/1.00, addr 2
    uhub1: single transaction translator
    uhub1: 3 ports with 2 removable, self powered
    umass0: STMicroelectronics ST72682  High Speed Mode, rev 2.00/2.10, addr 3
    umass1: CBM CBM, rev 2.00/1.00, addr 4
    pcib0: <Cavium on-chip PCI bridge> on obio0
    Disabling Octeon big bar support
    PCI Status: PCI 32-bit: 0xc041b
    pcib0: Initialized controller
    pci0: <PCI bus> on pcib0
    pci0: <simple comms> at device 1.0 (no driver attached)
    pci0: <serial bus, USB> at device 2.0 (no driver attached)
    pci0: <serial bus, USB> at device 2.2 (no driver attached)
    cpld0 on obio0
    gblmem0 on obio0
    octpkt0: <Octeon RGMII> on obio0
    cfi0: <AMD/Fujitsu - 4MB> on obio0
    platform_cookie_read not implemented
    octpkt_attach: Initializing octpkt0 interface
    Timecounter "mips" frequency 400000000 Hz quality 0
    Timecounters tick every 1.000 msec
    md0: Preloaded image </isofs-install-srxsme> 11878400 bytes at 0x80be9554
    fxp_ctrlif_attach:fxpctrldev = c1d23000
    fxp2_ctrlif_attach:fxpctrldev = 0xc1d23000
    Loading the NETPFE ethernet module
    Loading E1/T1/J1 driver
    Loading the DS1/E1 Media Layer; Attaching to media services layer
    Loading common multilink module.
    Loading the NETPFE PPPoE module
    Loading the netpfe services driver
    Loading the XDSL Media Layer; Attaching to media services layer
    Loading the IPSec driver
     Loading the PTM driver

    Loading the DIALER driver
    Loading Link Services PICs module.
    IPsec: Initialized Security Association Processing.
    da1 at umass-sim1 bus 1 target 0 lun 0
    da1: <CBM CBM 5.00> Removable Direct Access SCSI-2 device
    da1: 40.000MB/s transfers
    da1: 4020MB (8232960 512 byte sectors: 255H 63S/T 512C)
    da0 at umass-sim0 bus 0 target 0 lun 0
    da0: <ST ST72682 2.10> Removable Direct Access SCSI-2 device
    da0: 40.000MB/s transfers
    da0: 1000MB (2048000 512 byte sectors: 64H 32S/T 1000C)
    if_pfe_open: listener socket opened, listening on ...
    panic: Loss of soft watchdog
    cpuid = 0
    KDB: stack backtrace:
    SP 0x0: not in kernel
    0x0+0x0 (0,0,0,0) ra 0 sz 0
    pid 0
    KDB: enter: panic
    [thread pid 0 tid 0 ]
    Stopped at      0x808a0b30:     jr      ra
    db>

    Can someone please help me ?

    cheers

    Nik



  • 2.  RE: Cannot load SRX image from bootloader

     
    Posted 09-04-2012 20:27

    10.0R1.8 is the first release to support the SRX-210. Can you try with something a little more recent?



  • 3.  RE: Cannot load SRX image from bootloader
    Best Answer

    Posted 09-05-2012 16:00

    Sounds like the unit needs a bootloader upgrade. Starting with 10.0 releases the SRX went into a dual-partition mode so you can have two different version of code installed at the same time. After a failed boot the SRX will fall back to the backup partition so the system can attempt to come online.

     

    In addition, try booting without the watchdog process being enabled. In the loader prompt try running watchdog disable before loading the software.

     

    Lastly, if you can extract out the boot loader from a current version of software that will help greatly. Open the tar.gz file and find the junos-boot-srxsme-VERSION.tgz in the extracted tarball. from there, open that second tgz file and extract loader and uboot files to place on your tftp server. From there:

     

    1. tftpboot 0x100000 uboot
    2. bootloader upgrade uboot active 0x100000
    3. reset
    4. Get back into the loader
    5. tftpboot 0x100000 loader
    6. bootloader upgrade loader 0x100000
    7. reset
    8. Try upgrading your software again.

    Good luck!



  • 4.  RE: Cannot load SRX image from bootloader

    Posted 09-05-2012 21:40

    Thanks for the reply

    I will give that a try

    Cheers

    Nik



  • 5.  RE: Cannot load SRX image from bootloader

    Posted 09-05-2012 22:28

    Hi,

    I followed your instructions but could not find boot folder.

    I managed to get u-boot-crc.bin'. and loader.crc files from JTAC.

    I then followed your instructions, however  Iam getting a Checksum error

     

    ===================================

    => tftpboot 0x100000 u-boot-crc.bin
    Using octeth0 device
    TFTP from server 192.168.2.2; our IP address is 192.168.2.10
    Filename 'u-boot-crc.bin'.
    Load address: 0x100000
    Loading: #################################################################
             ###############################
    done
    Bytes transferred = 489102 (7768e hex)
    => bootloader upgrade u-boot active 0x100000
    Checking sanity of backup u-boot...OK

    WARNING: Image data checksum failure.
    => tftpboot 0x100000 loader_crc.bin
    Using octeth0 device
    TFTP from server 192.168.2.2; our IP address is 192.168.2.10
    Filename 'loader_crc.bin'.
    Load address: 0x100000
    Loading: T
    Abort
    =>
    =>
    => ping 192.168.2.2
    Using octeth0 device
    host 192.168.2.2 is alive
    =>
    Using octeth0 device
    host 192.168.2.2 is alive
    => tftpboot 0x100000 loader_crc
    Using octeth0 device
    TFTP from server 192.168.2.2; our IP address is 192.168.2.10
    Filename 'loader_crc'.
    Load address: 0x100000
    Loading: T
    Abort
    =>
    =>
    => ping 192.168.2.2
    Unknown command 'ping' - try 'help'
    => ping 192.168.2.2
    Using octeth0 device
    host 192.168.2.2 is alive
    => tftpboot 0x100000 loader_crc.bin
    Using octeth0 device
    TFTP from server 192.168.2.2; our IP address is 192.168.2.10
    Filename 'loader_crc.bin'.
    Load address: 0x100000
    Loading: ##########################################################
    done
    Bytes transferred = 294039 (47c97 hex)
    =>
    Using octeth0 device
    TFTP from server 192.168.2.2; our IP address is 192.168.2.10
    Filename 'loader_crc.bin'.
    Load address: 0x100000
    Loading: ##########################################################
    done
    Bytes transferred = 294039 (47c97 hex)
    => bootloader upgrade loader 0x100000

    WARNING: Image data checksum failure.
    Can you please advise how to fix this ?

    Cheers

    Nik



  • 6.  RE: Cannot load SRX image from bootloader

    Posted 09-05-2012 23:17

    thanks mate, it worked

    cheers

    Nik



  • 7.  RE: Cannot load SRX image from bootloader

    Posted 09-06-2012 05:33

    Good to hear! So you can now boot 10.0 (and later) code?



  • 8.  RE: Cannot load SRX image from bootloader

    Posted 11-07-2012 17:42

    Yes. Iam currently running 10.4 r11 without any issue



  • 9.  RE: Cannot load SRX image from bootloader

    Posted 08-16-2017 03:14

    download any Junos OS example and you can find this files under the boot folder. For example,

    1. Download junos-srxsme-12.1X44-D10.4-domestic.tgz. 
    2. Unzip this file and you will get the file junos-srxsme-12.1X44-D10.4-domestic.tar.
    3. Unzip this file to get the file junos-srxsme-12.1X44-D10.4-domestic.
    4. Open this folder and you will find the file junos-boot-srxsme-12.1X44-D10.4.tgz.
    5. Unzip this file to get the file junos-boot-srxsme-12.1X44-D10.4.tar.
    6. Unzip this file to find junos-boot-srxsme-12.1X44-D10.4.
    7. Open this folder and you will find the boot folder, under which the loader and uboot files are kept.
    8. Copy the loader and uboot files to a TFTP server.
    9. rename them to loader_crc and u-boot-crc.bin respectively.