The situation is critical - i have two clients with SRX100 with very similar problem during two days!!!
Strange coincidence. I start to fear for other small branch SRX.
First this SRX about which I was started this topic.
Thanks Spuluka for this links.
I was founded the same model of SRX100 and was copy snapshoot to the usb (unfortunately 16GB because i can't find smaller).
I put this pen to the broken SRX and boot. Unfortunately nothing change, SRX not boot from usb. Boot process looks like this:
U-Boot 1.1.6-JNPR-2.7 (Build time: Nov 26 2013 - 19:04:49)
Initializing memory this may take some time...
Measured DDR clock 266.62 MHz
SRX_100H2 board revision major:1, minor:0, serial #: BZ1234567890
OCTEON CN5020-SCP pass 1.1, Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)
DRAM: 2048 MB
Starting Memory POST...
Checking datalines... OK
Checking address lines... OK
Checking 512K memory for U-Boot... OK.
Running U-Boot CRC Test... OK.
Flash: 4 MB
USB: scanning bus for devices... 4 USB Device(s) found
scanning bus for storage devices... 2 Storage Device(s) found
Clearing DRAM........ done
BIST check passed.
Boot Media: nand-flash usb
Net: pic init done (err = 0)octeth0
POST Passed
Press SPACE to abort autoboot in 5 seconds
=>
Intresting that the first SRX100 from with I try to copy snapshoot did not allow to copy snapshoot. We was decide to restart this SRX and after this restart we have boot process like this:
U-Boot 1.1.6-JNPR-2.8 (Build time: Feb 10 2015 - 01:03:41)
Initializing memory this may take some time...
Measured DDR clock 266.62 MHz
SRX_100_HIGHMEM board revision major:0, minor:0, serial #: AT1234567890
OCTEON CN5020-SCP pass 1.1, Core clock: 500 MHz, DDR clock: 266 MHz (532 Mhz data rate)
DRAM: 1024 MB
Starting Memory POST...
Checking datalines... OK
Checking address lines... OK
Checking 512K memory for U-Boot... OK.
Running U-Boot CRC Test... OK.
Flash: 4 MB
USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
Clearing DRAM........ done
BIST check passed.
Boot Media: nand-flash usb
Net: pic init done (err = 0)octeth0
POST Passed
Press SPACE to abort autoboot in 1 seconds
ELF file is 32 bit
Loading .text @ 0x8f0000a0 (246560 bytes)
Loading .rodata @ 0x8f03c3c0 (14144 bytes)
Loading .reginfo @ 0x8f03fb00 (24 bytes)
Loading .rodata.str1.4 @ 0x8f03fb18 (16516 bytes)
Loading set_Xcommand_set @ 0x8f043b9c (96 bytes)
Loading .rodata.cst4 @ 0x8f043bfc (20 bytes)
Loading .data @ 0x8f044000 (5760 bytes)
Loading .data.rel.ro @ 0x8f045680 (120 bytes)
Loading .data.rel @ 0x8f0456f8 (136 bytes)
Clearing .bss @ 0x8f045780 (11600 bytes)
## Starting application at 0x8f0000a0 ...
Consoles: U-Boot console
Found compatible API, ver. 2.8
FreeBSD/MIPS U-Boot bootstrap loader, Revision 2.8
(slt-builder@svl-ssd-build-vm06.juniper.net, Tue Feb 10 00:32:30 PST 2015)
Memory: 1024MB
[1]Booting from nand-flash slice 1
Un-Protected 1 sectors
writing to flash...
Protected 1 sectors
can't load '/kernel'
can't load '/kernel.old'
Press Enter to stop auto bootsequencing and to enter loader prompt.
Type '?' for a list of commands, 'help' for more detailed help.
loader>
Situation a little better because we have loader prompt. Unfortunately not much better!
Device not finding USB. I put usb pen but there is no reaction and device not boot from this usb.
We try tftp. We set ip,mask, server everything looks grate. We start with command:
loader> install tftp://172.19.50.129/junos-srxsme-12.1X46-D40.2-domestic.tgz
Unfortunately output is always the same:
Target device selected for installation: internal media
octeth0: Up 1000 Mbps Full duplex (port 0)
cannot open package (error 60)
On the TFTP we see on every time the same 8568 bytes downloaded by device and then ERROR.
I was updated files u-boot-crc.bin and loader_crc from version from 2013 to version from 2015 using TFTP and we was trying again. Situation was the same.
In both situation booting from USB dosn't work. In first SRX i don't know what happend and why i can't boot from usb or tftp. In second SRX i think that hdd was destroyed and there is nothing to do with this (but why can't boot from usb?).
Anyone has any idea? Of course there is no support on this device (ehhh) , first of them have 2 years, second have 4.