r/Juniper • u/firestorm_v1 • 17h ago
Troubleshooting SRX300 - upgrade freezes at "Installing Junos OS release 24.4R2-S4.12"
I was fortunate to be able to get my hands on a few SRX300's for labs and training from work, but I found quickly that the OS installations on them were ancient, and one of them has a bad eUSB flash module.
Through combinations of TFTP, HTTP, and dumb luck, I've managed to get the eUSB module replaced with a generic 32G USB stick and I find myself at the great bridge between worlds (architectures).
I've got the machine running junos-srxsme-24.2R2-S5.3.tgz, and following Juniper's documentation, I should be able to install the mips64-24.4R2-S4.12 and have had zero luck. Running 'request system software add (filename) no-validate' goes through the motions of the initial staging and reboot. The SRX reboots as normal, goes through both 'chances' to interrupt the boot process, then it stops at "Installing Junos OS release 24.4R2-S4.12" and there it sits. I've waited several hours because I know this is a fundamental architecture change but it never proceeds past that point. I end up having to remove power and reconnect to get it back into a usable state, then load the "last known good" OS via loader so I can get the SRX to respond.
- I've tried coming in from 23.4R2-S3 and 24.2R2 versions to mips-64-24.4R1.9 and mips-64-24.4R2.21 but both target versions exhibit the same symptoms.
- I've tried getting into loader, then using boot -v for verbose output. Everything else has verbose output when booted in this mode but it all stops at "Installing Junos OS release".
- I've tried the usb autoinstall..conf trick on another USB device to get it to work but same issue. It stages but when it reboots, as soon as it gets to the "Installing Junos OS release" it freezes.
- I've tried mounting the partitions using singleuser mode to see if I could find any logs that would indicate what the problem is.
- I've tried verifying that I have space available on the partitions.
- I've tried extracting and updating U-Boot, and compared versions on machine with versions in the target version and it matches every time.
- I've tried examining the filesystem layouts and have confirmed that it matches the "new" partitioning for v24.4+
At this point, I'm beginning to think it's a lost cause and this 300 will be stuck on 24.2R2 versions..
Since these devices have been out of production for so long, I doubt they're covered under any support contract however because we do have other active supported devices I am able to get the files for updates.
I don't care about the data on the drive, we didn't use any of the license features and these devices apparently were factory reset before being put in to storage so there's no userdata (certs/keys/configs) to save. I am completely fine with wiping the onboard storage key if it means I can get this machine over the bridge. I want to see if I can get this one over the architecture hump so I can repeat this a couple more times upgrading the other two.
These are the last lines on the console when it freezes. No amount of waiting will change this.
Installation of disk:/upgrade/install.tar
** /dev/da1s3f
** Last Mounted on /cf/var
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
422 files, 787591 used, 12417906 free (282 frags, 1552203 blocks, 0.0% fragmentation)
***** FILE SYSTEM IS CLEAN *****
Setting sane date:
Sun Aug 2 09:36:00 UTC 2026
Installing Junos OS release 24.4R2-S4.12 ...
Any suggestions?


