Junos
Junos

Options for SRX240 that won't load JunOS anymore?

‎06-18-2019 01:16 PM

We purchased a used SRX240 and have been using it for about a year.  We just moved offices and when I booted it up I got some drive errors and it will not load JunOS.  What are my options?  It's out of service, but is there any way I can download JunOS and reinstall? Should/can I replace the drive?  Other options?

 

Spoiler


U-Boot 1.1.6-JNPR-2.6 (Build time: Aug 8 2013 - 20:07:50)

Initializing memory this may take some time...
Measured DDR clock 333.28 MHz
SRX_240H2 board revision major:2, minor:11, serial #: ACMH0313
OCTEON CN5230R-SCP pass 2.0, Core clock: 600 MHz, DDR clock: 333 MHz (666 Mhz da ta 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...
Root Hub 0: 3 USB Device(s) found
Root Hub 1: 1 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Clearing DRAM........ done
BIST check passed.
PCIe: Initializing port 0
PCIe: Initializing port 1
Boot Media: nand-flash usb
Net: 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 (5744 bytes)
Loading .data.rel.ro @ 0x8f045670 (120 bytes)
Loading .data.rel @ 0x8f0456e8 (136 bytes)
Clearing .bss @ 0x8f045770 (11600 bytes)
## Starting application at 0x8f0000a0 ...
Consoles: U-Boot console
Found compatible API, ver. 2.6

FreeBSD/MIPS U-Boot bootstrap loader, Revision 2.5
(slt-builder@slt-junos15.juniper.net, Tue Apr 2 12:36:46 PDT 2013)
Memory: 2048MB
[0]Booting from nand-flash slice 1
Un-Protected 1 sectors
writing to flash...
Protected 1 sectors
Loading /boot/defaults/loader.conf
/kernel data=0xb9e924+0x13c950 syms=[0x4+0x91d20+0x4+0xd6145]


Hit [Enter] to boot immediately, or space bar for command prompt.
Booting [/kernel]...
Kernel entry at 0x801000c0 ...
init regular console
Primary ICache: Sets 64 Size 128 Asso 4
Primary DCache: Sets 1 Size 128 Asso 64
Secondary DCache: Sets 512 Size 128 Asso 8
GDB: debug ports: uart
GDB: current port: uart
KDB: debugger backends: ddb gdb
KDB: current backend: ddb
kld_map_v: 0x8ff80000, kld_map_p: 0x0
Copyright (c) 1996-2018, 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 12.3X48-D70.3 #0: 2018-05-17 09:31:28 UTC
builder@kuzuryu.juniper.net:/volume/build/junos/12.3/service/12.3X48-D70.3/o bj-octeon/junos/bsd/kernels/JSRXNLE/kernel
JUNOS 12.3X48-D70.3 #0: 2018-05-17 09:31:28 UTC
builder@kuzuryu.juniper.net:/volume/build/junos/12.3/service/12.3X48-D70.3/o bj-octeon/junos/bsd/kernels/JSRXNLE/kernel
real memory = 2147483648 (2048MB)
avail memory = 1040236544 (992MB)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
Security policy loaded: Junos MAC/veriexec (mac_veriexec)
Security policy loaded: JUNOS MAC/pcap (mac_pcap)
Security policy loaded: JUNOS MAC/runasnonroot (mac_runasnonroot)
MAC/veriexec fingerprint module loaded: SHA256
MAC/veriexec fingerprint module loaded: SHA1
netisr_init: !debug_mpsafenet, forcing maxthreads from 4 to 1
cpu0 on motherboard
: CAVIUM's OCTEON 52XX CPU Rev. 0.8 with no FPU implemented
L1 Cache: I size 32kb(128 line), D size 8kb(128 line), sixty four way.
L2 Cache: Size 512kb, 8 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: <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
dwc1: <Synopsis DWC OTG Controller Driver> on obio0
usb1: <USB Bus for DWC OTG Controller> on dwc1
usb1: USB revision 2.0
uhub2: vendor 0x0000 DWC OTG root hub, class 9/0, rev 2.00/1.00, addr 1
uhub2: 1 port with 1 removable, self powered
cpld0 on obio0
pcib1: <Cavium on-chip PCIe HOST bridge> on obio0
Disabling Octeon big bar support
PCIe: Waiting for port 0 to finish reset
PCIe: Port 0 link active, 2 lanes
PCIe: Waiting for port 1 to finish reset
PCIe: Port 1 link active, 1 lanes
pcib1: Initialized controller
pci0: <PCI bus> on pcib1
pcib2: <PCI-PCI bridge> irq 0 at device 0.0 on pci0
pci1: <PCI bus> on pcib2
pci1: <serial bus, USB> at device 2.0 (no driver attached)
pci1: <serial bus, USB> at device 2.1 (no driver attached)
pci1: <network> at device 7.0 (no driver attached)
pcib0: <Cavium on-chip PCIe HOST bridge> on obio0
pci2: <PCI bus> on pcib0
pci2: <processor> at device 0.0 (no driver attached)
gblmem0 on obio0
octpkt0: <Octeon RGMII> on obio0
cfi0: <AMD/Fujitsu - 4MB> on obio0
Timecounter "mips" frequency 600000000 Hz quality 0
###PCB Group initialized for udppcbgroup
###PCB Group initialized for tcppcbgroup
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: 2000MB (4096000 512 byte sectors: 255H 63S/T 254C)
Kernel thread "wkupdaemon" (pid 48) exited prematurely.
Trying to mount root from ufs:/dev/da0s1a
WARNING: / was not properly dismounted
MFSINIT: Initialising MFSROOT
WARNING: / was not properly dismounted
Process-1 beginning MFSROOT initialization...
Creating MFSROOT...
/dev/md0: 20.0MB (40956 sectors) block size 16384, fragment size 2048
using 4 cylinder groups of 5.00MB, 320 blks, 640 inodes.
super-block backups (for fsck -b #) at:
32, 10272, 20512, 30752
Populating MFSROOT...
Creating symlinks...
Setting up mounts...
Continuing boot from MFSROOT...
Attaching /cf/packages/junos via /dev/mdctl...
Mounted junos package on /dev/md1...
J
Media check on da0
Zone 11 Block 0316 Addr 2d3c00 : Bad read
Recovering Block
Automatic reboot in progress...
** /dev/da0s1a (NO WRITE)
** Last Mounted on /
** Root file system
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
161 files, 91918 used, 220268 free (36 frags, 27529 blocks, 0.0% fragmentation)
mount reload of '/' failed: Operation not supported

Verified jboot signed by PackageProductionEc_2018 method ECDSA256+unknown
Verified junos signed by PackageProductionEc_2018 method ECDSA256+unknown
Verified junos-12.3X48-D70.3-domestic signed by PackageProductionEc_2018 method ECDSA256+unknown
Checking integrity of BSD labels:
s1: Passed
s2: Passed
s3: Passed
s4: Passed
** /dev/bo0s3e
** Last Mounted on /config
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
13 files, 19 used, 23557 free (13 frags, 2943 blocks, 0.1% fragmentation)
** /dev/bo0s3f
** Last Mounted on /cf/var
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
LINK COUNT DIR I=2 OWNER=0 MODE=40755
SIZE=512 MTIME=Jul 10 23:22 2018 COUNT 32 SHOULD BE 31
ADJUST? yes

UNREF FILE I=20253 OWNER=0 MODE=100644
SIZE=0 MTIME=Jul 10 23:27 2018
RECONNECT? yes

NO lost+found DIRECTORY
CREATE? yes

UNREF FILE I=20259 OWNER=0 MODE=100600
SIZE=106496 MTIME=Jul 10 23:27 2018
RECONNECT? yes

UNREF FILE I=20262 OWNER=0 MODE=100600
SIZE=106496 MTIME=Jul 10 23:27 2018
RECONNECT? yes

UNREF FILE I=20265 OWNER=0 MODE=100600
SIZE=106496 MTIME=Jul 10 23:27 2018
RECONNECT? yes

UNREF FILE I=20274 OWNER=0 MODE=100600
SIZE=106496 MTIME=Jul 10 23:27 2018
RECONNECT? yes

UNREF FILE I=20276 OWNER=0 MODE=100600
SIZE=8192 MTIME=Jul 10 23:27 2018
RECONNECT? yes

UNREF FILE I=60331 OWNER=0 MODE=100644
SIZE=0 MTIME=Nov 26 20:46 2018
RECONNECT? yes

** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? yes

SUMMARY INFORMATION BAD
SALVAGE? yes

BLK(S) MISSING IN BIT MAPS
SALVAGE? yes

449 files, 160211 used, 155991 free (183 frags, 19476 blocks, 0.1% fragmentation )

***** FILE SYSTEM WAS MODIFIED *****
Checking integrity of licenses:
Checking integrity of configuration:
rescue.conf.gz: Passed
Loading configuration ...
Time and ticks drifted too much, resetting synchronizatio n...
Application-identification process: <xnm:error xmlns="http://xml.juniper.net/xnm/1.1/xnm" xmlns:xnm="http://xml.juniper.net/xnm/1.1/xnm">
Application-identification process: <source-daemon>appidd</source-daemon>
Application-identification process: <edit-path>[edit services]</edit-path>
Application-identification process: <statement>application-identification</statement>
Application-identification process: <message>Install is in progress, please retry later</message>
Application-identification process: </xnm:error>
mgd: error: configuration check-out failed
Warning: Commit failed, activating partial configuration.
Warning: Edit the router configuration to fix these errors.
Setting initial options: .
Starting optional daemons: usbd.
Doing initial network setup:.
Initial interface configuration:
additional daemons: eventd.
Non-existant dump device /dev/bo0s1b
Additional routing options:kern.module_path: /boot//kernel;/boot/modules -> /boot/modules;/modules/ifpfe_drv;/modules;
kld netpfe drv: ifpfed_dialer ipsec kld.
Doing additional network setup:.
Starting final network daemons:.
setting ldconfig path: /usr/lib /opt/lib
starting standard daemons: cron.
Initial rc.mips initialization:.
Local package initialization:.
starting local daemons:set cores for group access
.
kern.securelevel: -1 -> 1
Creating JAIL MFS partition...
JAIL MFS partition created
boot.upgrade.uboot="0xBFC00000"
boot.upgrade.loader="0xBFE00000"
Boot media /dev/da0 has dual root support
WARNING: JUNOS versions running on dual partitions are not same
** /dev/da0s2a
** Last Mounted on /mfs/tmp/snap-tmp.1295/mnt.1295
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
170 files, 90995 used, 225143 free (31 frags, 28139 blocks, 0.0% fragmentation)
Tue Jun 18 05:25:27 UTC 2019

SPG-JUNIPERP01 (ttyu0)

login:

5 REPLIES 5
Junos

Re: Options for SRX240 that won't load JunOS anymore?

‎06-18-2019 01:20 PM
Junos

Re: Options for SRX240 that won't load JunOS anymore?

‎06-18-2019 01:26 PM

You have encountered this error because your account privileges do not permit access to the information or service requested. Software download entitlement is granted for customers under the following scenarios. 

  • Juniper Product within the first 90 days of the hardware warranty period.
  • Juniper Product which is currently under an active maintenance contract.
  • Juniper Standalone Software Subscription which is currently active.

This is my problem.  I can't figure out how to get a "Standalone Software Subscription" even if my company could afford it...

Junos

Re: Options for SRX240 that won't load JunOS anymore?

‎06-18-2019 01:34 PM

Hi! 

 

Looks like you need to have a valid Serial number to register your account, otherwise it will be guest access only, meaning you could not download Junos software. 

 

Best

 

Mu

Junos

Re: Options for SRX240 that won't load JunOS anymore?

‎06-18-2019 02:44 PM

Hi RoamScott,

 

Please contact our Global Support at 1-888-314-5822 regarding the same to look into this further and get an idea on the available options you might have. 

 

https://support.juniper.net/support/requesting-support/

 

Please Mark My Solution Accepted if it Helped, Kudos are Appreciated too!

 

Regards,

HS

 

 

Junos
Solution
Accepted by topic author RoamScott
‎06-18-2019 03:18 PM

Re: Options for SRX240 that won't load JunOS anymore?

‎06-18-2019 03:17 PM

That won't even help as this is EOL.

 

It looks like the only way I could possibly fix this one is by purchasing a new model and getting the service contract, then my account would have permission to download the OS for the old 240.

 

Smiley Sad