SRX

 My SRX240 device with junos version 10.4R3.4 is strucked at prompt  db>. Some of boot messages are shown as below.  Please help to fix.

 

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)
SMP: AP CPU #1 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #3 Launched!
Trying to create bootdev, rootpartition da0s1a
Trying to mount root from ufs:/dev/da0s1a
WARNING: / was not properly dismounted
Interrupt storm detected on "swi0:"; throttling interrupt source
Ignoring watchdog timeout during boot/reboot
Attaching /cf/packages/junos via /dev/mdctl...
Mounted junos package on /dev/md0...
Ignoring watchdog timeout during boot/reboot

Ignoring watchdog timeout during boot/reboot
Media check on da0
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
Ignoring watchdog timeout during boot/reboot
panic: Hardware watchdog timeout NMI
cpuid = 0
KDB: stack backtrace:
SP 0x0: not in kernel
uart_z8530_class+0x0 (0,0,0,0) ra 0 sz 0
pid 24, process: swi7: clock
###Entering boot mastership relinquish phase
KDB: enter: panic
[thread pid 24 tid 100023 ]
Stopped at breakpoint+0x4: jr ra
db>

Your best bet is to copy JunOS to a USB stick, and boot the device with that in there. Hit space-bar to enter the loader prompt, then run the following: install --format file:///junos-srxsme-11.2R6.3-domestic.tgz Replacing the filename with the particular version of JunOS you are installing of course. This will format the CF card and install a fresh copy of JunOS. Ron

Thanks.  It 's weird but I thinks I found problem is caused by the console cable. Just change to another console cable , everything 's work fine.  The problem console cable is not only cause failure of boot processes but also cause device to continue crash and reboot itself. Trying on other SRX240 and SRX100 in my lab also got the same result.

I seem to be having the same problem - did you ever confirm the pinouts of the "bad" vs "good" cable?  Or do you believe there was a physical fault in the cable that dropped you into the debugger?