Progress update, It was suggested that I try an older USB drive. Managed to dig out an old 4GB verbatim USB drive. I managed to get the Juniper EX3400 to see and start to boot from the connected drive with an image on it. Now I get
start address is not aligned errors, is this device related or USB drive related or command related?
=> usbboot dev 1
Loading from usb device 1, partition 1: Name: usbdb1 Type: U-Boot
ERROR: v7_dcache_inval_range - start address is not aligned - 0x000000de
ERROR: v7_outer_cache_inval_range - start address is not aligned - 0x000000de
data abort
pc : [<dff49ffc>] lr : [<dff4f864>]
reloc pc : [<1e041ffc>] lr : [<1e047864>]
sp : dfeb5ae4 ip : 00000000 fp : 1e000020
r10: 1e0820b6 r9 : dfeb7f00 r8 : 00000000
r7 : 00000000 r6 : dff3aa64 r5 : dff90bf8 r4 : dff7e600
r3 : 00000001 r2 : 0000ffff r1 : 000000de r0 : 000000de
Flags: nZCv IRQs off FIQs off Mode SVC_32
Resetting CPU ...
resetting ...
Argh, AI states:
| junos-install-media-usb-ex-arm-32-23.4R2-S5.8.img | NO | ARM64 | “Unknown image type” |
|---|
| junos-install-media-usb-ex-3400-arm-.img | YES | ARM32 | Boots and installs |
|---|
junos-install-media-usb-ex-arm-32-23.4R2-S5.8.img
is for EX4100/EX4300MP and ACX/QFX ARM platforms, not EX3400.
I have the wrong image...
UPDATE: IMAGE FLASH SUCCESSFUL!
This applies specifically to when you can only reach the
=> prompt and not the
loader> prompt, may work even if you can reach the loader> prompt but still cannot get the firmware to load.
notes:
- Co-Pilot, took me down the garden path and suggested using TFTP, I could connect to the switch and start to load the image. But the connection always reset at 29%, ~100MB transferred
-Gemini, suggested that env boot variables were incorrect for the recovery process I was trying to use, oh?
-Original firmware on the boot-looping switch: JUNOS 20.4R3-S2.6 Kernel 32-bit
required:
-latest USB image from Juniper, I used: junos-install-media-usb-ex-arm-32-25.2R1-S2.3.img
-Write image to an older USB drive (Both an old 4GB verbatim and an even older SanDisk Cruzer 512MB, worked), I used Rufus 4.6p to write the image.
Ctrl + C during boot loop to reach =>
[connect your USB device with the written image to the Juniper Switch]
usb start >to enable the USB host driver
usb info >to find your USB disk number
setenv loaderdev disk1 >to change the default device
saveenv >save the change
reset >causes the switch to reboot
In my case - sit back and watch your switch rise from being bricked.
Watch for
rebooting message on the console, as you need to undo the change to the loaderdev env variable
Ctrl + C during boot to reach
=>
setenv loaderdev >by leaving it blank, restores default boot scan behavior
saveenv >save the change
[disconnect your USB device from the Juniper Switch]
reset >causes the switch to reboot
Watch the switch complete final installation, including create key pairs, apply patches that may be part of the image and create a recovery image.
If there were patches... my image had patches, the switch will boot again.
After the final reboot, I was able to login as root with no password and proceed with configuration.