SRX Services Gateway
SRX Services Gateway

SRX100H2-VA Upgrade fails.

‎11-10-2019 11:10 AM

Currently on JUNOS 12.3X48-D75.4

Unable to load 12.3X48-D85.1

 

I did upgrade once, and it booted, but a subsequent boot reverted to the backup partition.  (still running D75).   I have tried to load the newer firmware, copying it to /cf/var/tmp using WinSCP and then running the upgrade command:

 

  request system software add /var/tmp/junos-srxsme-12.3X48-D85.1-domestic.tgz partition no-copy 

 

I also did a request system storage cleanup before I started.

 

I have a copy of my config, so is there a way to start again, both partitions running this newer firmware?  (I don't have access to D90, as this is a home router, and I don't have a service agreement).

 

 

NOTICE: Validating configuration against junos-srxsme-12.3X48-D85.1-domestic.tgz .
NOTICE: Use the 'no-validate' option to skip this if desired.
Formatting alternate root (/dev/ad0s1a)...
/dev/ad0s1a: 629.5MB (1289196 sectors) block size 16384, fragment size 2048
using 4 cylinder groups of 157.38MB, 10072 blks, 20224 inodes.
super-block backups (for fsck -b #) at:
32, 322336, 644640, 966944
saving package file in /var/sw/pkg ...
Checking compatibility with configuration
Initializing...
Using junos-12.3X48-D85.1-domestic from /altroot/cf/packages/install-tmp/junos-1 2.3X48-D85.1-domestic
Copying package ...
mkdir: /cf/var/validate/chroot/tmp: No such file or directory
mount_nullfs: /cf/var/validate/chroot/tmp: No such file or directory
cd: can't cd to /cf/var/validate/chroot/tmp/junos
/usr/libexec/ui/validate-config: cannot create /cf/var/validate/chroot/tmp/junos /+INSTALL.x: No such file or directory
chroot: /bin/sh: No such file or directory
ERROR: validate-config: /cf/var/validate/chroot/tmp/junos/+INSTALL fails
WARNING: Current configuration not compatible with /altroot/cf/packages/install- tmp/junos-12.3X48-D85.1-domestic

 

3 REPLIES 3
SRX Services Gateway

Re: SRX100H2-VA Upgrade fails.

‎11-10-2019 01:09 PM

Put the alternative partition back using:

 

request system snapshot slice alternate

 

and rebooted, and I have 2 working paritions again, but the upgrade stil fails:

 

request system software add unlink no-copy /cf/var/tmp/junos-srxsme-12.3X48-D85.1-domestic.tgz

 

NOTICE: Validating configuration against junos-srxsme-12.3X48-D85.1-domestic.tgz .
NOTICE: Use the 'no-validate' option to skip this if desired.
Formatting alternate root (/dev/ad0s2a)...
/dev/ad0s2a: 630.0MB (1290204 sectors) block size 16384, fragment size 2048
using 4 cylinder groups of 157.50MB, 10080 blks, 20224 inodes.
super-block backups (for fsck -b #) at:
32, 322592, 645152, 967712
Removing /cf/var/tmp/junos-srxsme-12.3X48-D85.1-domestic.tgz
Checking compatibility with configuration
Initializing...
Using junos-12.3X48-D85.1-domestic from /altroot/cf/packages/install-tmp/junos-1 2.3X48-D85.1-domestic
Copying package ...
mkdir: /cf/var/validate/chroot/tmp: No such file or directory
mount_nullfs: /cf/var/validate/chroot/tmp: No such file or directory
cd: can't cd to /cf/var/validate/chroot/tmp/junos
/usr/libexec/ui/validate-config: cannot create /cf/var/validate/chroot/tmp/junos /+INSTALL.x: No such file or directory
chroot: /bin/sh: No such file or directory
ERROR: validate-config: /cf/var/validate/chroot/tmp/junos/+INSTALL fails
WARNING: Current configuration not compatible with /altroot/cf/packages/install- tmp/junos-12.3X48-D85.1-domestic

SRX Services Gateway

Re: SRX100H2-VA Upgrade fails.

‎11-10-2019 05:56 PM
I’m pretty sure the various file and directory errors are spurious and that you’re just hitting what it thinks is a configuration validation error.

WARNING: Current configuration not compatible with /altroot/cf/packages/install- tmp/junos-12.3X48-D85.1-domestic

I would just try reinstalling with the no-validate option, There won’t be any configuration incompatibilities between these two minor revisions.
SRX Services Gateway

Re: SRX100H2-VA Upgrade fails.

‎11-11-2019 02:15 PM

In the end, I upgraded via the J web interface, and that worked, rebooted and applied the new working system to the alternative partition, it's all OK again.   Just some random weirdness it seems.