SRX Services Gateway
Showing results for 
Search instead for 
Do you mean 
Reply
Recognized Expert
Posts: 286
Registered: ‎04-03-2009
0 Kudos

Upgrading to 10.3R1 . . . but I have no space!

Hey all,

 

I'm trying to put 10.3R1 on an SRX210 to do some testing with, but I don't have enough space

 

Yes I have done 'request system storage cleanup' and 'request system software delete-backup'

 

Current version is 10.2R2, and I am running IDP (again, doing some testing).  I had this same problem with 10.2R2, but I think I just broke down and used the USB drive that time.

 

 

It looks like the reason I have not enough space is because of the IDP, but surely I don't have to disable IDP, delete some / all of the IDP packages (and which ones, I haven no clue), just to upgrade -- and then reinstall the IDP packages and re-enable.

 

Here's my storage dilemma:

 

admin@SRX210> show system storage 
Filesystem              Size       Used      Avail  Capacity   Mounted on
/dev/da0s1a             293M       203M        67M       75%  /
devfs                   1.0K       1.0K         0B      100%  /dev
/dev/md0                567M       567M         0B      100%  /junos
/cf                     293M       203M        67M       75%  /junos/cf
devfs                   1.0K       1.0K         0B      100%  /junos/dev/
procfs                  4.0K       4.0K         0B      100%  /proc
/dev/bo0s3e              24M        50K        22M        0%  /config
/dev/bo0s3f             342M       116M       199M       37%  /cf/var
/dev/md1                168M        15M       139M       10%  /mfs
/dev/md2                 39M       4.0K        36M        0%  /mfs/var/run/utm
/dev/md3                1.8M       4.0K       1.7M        0%  /jail/mfs

 

 

Notice I have 199M free space in /cf/var -- but the 10.3R1 (and 10.2R2 for that matter) image is ~210 MB.

 

 

What I can't remember is if I used the 'unlink no-copy' options when I upgraded to 10.2R2, so if there is a 'backup' 10.2R2 image stored somewhere, I think if I delete that i'll be fine.  But lets just say I don't want to go around randomly force-deleting files from the shell Smiley Tongue

 

Thanks,

 

Will

Trusted Contributor
Posts: 447
Registered: ‎11-11-2008
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

Did you try adding the unlink and no-copy to the command?

 

Also from what i can see your CF card is small.  The one on my SRX210 is a 1GB where you seems to be way under that.

 

My SRX

 

Filesystem              Size       Used      Avail  Capacity   Mounted on
/dev/da0s1a             898M       473M       353M       57%  /
devfs                   1.0K       1.0K         0B      100%  /dev
/dev/md0                566M       566M         0B      100%  /junos
/cf                     898M       473M       353M       57%  /junos/cf
devfs                   1.0K       1.0K         0B      100%  /junos/dev/
procfs                  4.0K       4.0K         0B      100%  /proc
/dev/bo0s1e              24M        52K        22M        0%  /config
/dev/bo0s1f              61M       4.1M        52M        7%  /cf/var/log
/dev/md1                168M        15M       140M       10%  /mfs
/cf/var/jail            898M       473M       353M       57%  /jail/var
/cf/var/log              61M       4.1M        52M        7%  /jail/var/log
devfs                   1.0K       1.0K         0B      100%  /jail/dev
/dev/md2                 39M       4.0K        36M        0%  /mfs/var/run/utm
/dev/md3                1.8M       4.0K       1.7M        0%  /jail/mfs

Recognized Expert
Posts: 255
Registered: ‎07-24-2009
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

I think the /cf partition size may be related to the dual-boot partition, which was introduced in 10.0.  After converting to a dual-root partition my /cf partition shows the same 293M on an SRX210.

 

You may also want to look if you have any images or large files save locally that are taking up space with 'file list'.

Juniper Elite Partner
JNCIE-ENT #63, JNCIE-SP #705, JNCIE-SEC #17, JNCIS-FWV, JNCIS-SSL
Trusted Expert
Posts: 601
Registered: ‎11-21-2009
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

[ Edited ]

If you found that there is no sufficient space , you can upgrade without copying the file to the SRX beofre the upgrade using the below method   

1-run ftp server  ( like : 3CDaemon)  on your pc   & let it point to the directory containing the image

2- use the command :   request sytem software add        ftp://username  :   password@ip/packagename.tgz

 

 username & password are the same as created at step1   , ip is ip of your ftp server ( Your PC )

Recognized Expert
Posts: 286
Registered: ‎04-03-2009
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

the SRX is a dual-root partitioned SRX, I think that probably has something to do with it.

 

The SRX is just a 210H-POE -- I'm pretty sure the CF is the same in all of them

 

 

admin@SRX210> show chassis hardware            
Hardware inventory:
Item             Version  Part number  Serial number     Description
Chassis                                AE2709AA0244      SRX210h-poe
Routing Engine   REV 32   750-021780   AAAJ5953          RE-SRX210H-POE
FPC 0                                                    FPC
  PIC 0                                                  2x GE, 6x FE, 1x 3G
Power Supply 0  

 

 

I can't use the unlink no-copy options yet as I can't even copy the image over Smiley Tongue

 

i've tried to load via FTP but get a 'can't fetch' error -- possible i'm fat fingering something, but I don't think so -- will try it again all the same

Recognized Expert
Posts: 286
Registered: ‎04-03-2009
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

[ Edited ]

well I tried FTP method using the no-copy unlink option, and it started to download . . . and then failed due to space Smiley Sad

 

 

admin@SRX210> ...me-10.3R1.9-domestic.tgz no-copy unlink no-validate    
/tmp/incoming-package.7287                             182 kB  182 kBps
fetch: /tmp/incoming-package.7287: No space left on device
ERROR: Cannot fetch file: junos-srxsme-10.3R1.9-domestic.tgz

 

 

I guess i'll just resort to the USB method for now . . . but thats pretty nasty.

 

are 2GB flash cards really that expensive Juniper?  Smiley Tongue

Recognized Expert
Posts: 255
Registered: ‎07-24-2009
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

FYI, just tried upgrading from 10.1R1.8 to 10.3 on SRX210 and it succeeded just using the no-validate option.  Below is output:

 

root@SRX210> show system storage
node0:
--------------------------------------------------------------------------
Filesystem              Size       Used      Avail  Capacity   Mounted on
/dev/da0s1a             293M       190M        80M       70%  /
devfs                   1.0K       1.0K         0B      100%  /dev
/dev/md0                528M       528M         0B      100%  /junos
/cf                     293M       190M        80M       70%  /junos/cf
devfs                   1.0K       1.0K         0B      100%  /junos/dev/
procfs                  4.0K       4.0K         0B      100%  /proc
/dev/bo0s3e              24M        38K        22M        0%  /config
/dev/bo0s3f             342M       7.3M       308M        2%  /cf/var
/dev/md1                168M        14M       140M        9%  /mfs
/cf/var/jail            342M       7.3M       308M        2%  /jail/var
devfs                   1.0K       1.0K         0B      100%  /jail/dev
/dev/md2                 39M       4.0K        36M        0%  /mfs/var/run/utm
/dev/md3                1.8M       4.0K       1.7M        0%  /jail/mfs


root@SRX210> request system software add ftp://x.x.x.x/junos-srxsme-10.3R1.9-domestic.tgz no-validate                
/var/tmp/incoming-package.39856                        519 kB  519 kBps
Package contains junos-10.3R1.9.tgz ; renaming ...
Formatting alternate root (/dev/da0s2a)...
/dev/da0s2a: 298.0MB (610284 sectors) block size 16384, fragment size 2048
        using 4 cylinder groups of 74.50MB, 4768 blks, 9600 inodes.
super-block backups (for fsck -b #) at:
 32, 152608, 305184, 457760
Not enough space in /var to save the package file
Installing package '/altroot/cf/packages/install-tmp/junos-10.3R1.9-domestic' ...
Verified junos-boot-srxsme-10.3R1.9.tgz signed by PackageProduction_10_3_0
Verified junos-srxsme-10.3R1.9-domestic signed by PackageProduction_10_3_0
Saving boot file package in /var/sw/pkg/junos-boot-srxsme-10.3R1.9.tgz
JUNOS 10.3R1.9 will become active at next reboot
WARNING: A reboot is required to load this software correctly
WARNING:     Use the 'request system reboot' command
WARNING:         when software installation is complete
Saving package file in /var/sw/pkg/junos-10.3R1.9 ...
cp: /altroot/cf/packages/install-tmp/junos-10.3R1.9-domestic is a directory (not copied).
Saving state for rollback ...

Juniper Elite Partner
JNCIE-ENT #63, JNCIE-SP #705, JNCIE-SEC #17, JNCIS-FWV, JNCIS-SSL
Highlighted
Recognized Expert
Posts: 286
Registered: ‎04-03-2009
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

yea I think the issue for me is combination of Dual-root plus IDP taking up all the space.

 

not a super huge deal right now since its a local test device, but could be a major PITA if it was a remote site that needed upgrading.

 

not sure what I can delete to make more room . . . as I said i'm hesitant to just go into shell and start force-deleting stuff Smiley Tongue

Regular Visitor
Posts: 7
Registered: ‎01-04-2010
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

root@SRX210> request system software add no-validate no-copy /var/tmp/junos-srxsme-10.3R1.9-domestic.tgz reboot
Installing package '/var/tmp/junos-srxsme-10.3R1.9-domestic.tgz' ...
Verified junos-boot-srxsme-10.3R1.9.tgz signed by PackageProduction_10_3_0
Verified junos-srxsme-10.3R1.9-domestic signed by PackageProduction_10_3_0
Available space: -744 require: 28036

WARNING: The /cf filesystem is low on free disk space.
WARNING: This package requires 28036k free, but there
WARNING: is only -744k available.

WARNING: This installation attempt will be aborted.
ERROR: junos-10.3R1.9-domestic fails requirements check
Installation failed for package '/var/tmp/junos-srxsme-10.3R1.9-domestic.tgz'

 

Solution:

1.Insert USB Memory Stick(included JunOS)(2G or 4G)

2. mount 

create mount point   ---->mkdir /var/tmp/usb

mount -t msdos /dev/da1s1 /var/tmp/usb

3. Confirm junos file
 ls -altr /var/tmp/usb

4. upgrade

root@SRX210>request system software add no-validate no-copy /var/tmp/usb/junos-srxsme-10.3R1.9-domestic.tgz reboot

Contributor
Posts: 68
Registered: ‎03-24-2008
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

Hi Will,

I was having a similar issue with j-series(trying to upgrade from 9.6 to 10.0)...it kept saying no space in cf(even though i did cleanup,remove backup etc)

I tried the ftp method as mentioned in previous post (with no-copy, unlink and no-validate option) But i kept doing this as "root" user it did not work.

I got fed up with this, did a reboot, logged in as another user(a super-user) and tried the command i was able to upgrade. I did not get any error message. Don't know if this would help

Regards,

Haze

Contributor
Posts: 200
Registered: ‎05-05-2010
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

Hi kang_ki-yong ,

What kind of Flash can be used ? any Flash ?

Should i format the flash before copying junos to it ?  NTFS or FAT ?

Recognized Expert
Posts: 286
Registered: ‎04-03-2009
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

just to followup on this -- I came across this KB article:  http://kb.juniper.net/KB17365

 

 

and the output was as follows, along with my 'show system storage' output:

 

root@SRX-210% find -x /cf/var -type f -exec du -k {} \; | sort -n
0       /cf/var/jail/etc/hosts
0       /cf/var/jail/etc/hosts.allow
0       /cf/var/jail/etc/issue
0       /cf/var/jail/etc/pam_radius.conf
0       /cf/var/jail/etc/pam_tacplus.conf
0       /cf/var/log/authd_profilelib
0       /cf/var/log/dfwc
0       /cf/var/log/idpd
0       /cf/var/log/license
0       /cf/var/log/pfed_event_trace.log
0       /cf/var/log/pfed_trace.log
0       /cf/var/log/utmd-av
2       /cf/var/crash/minfree
2       /cf/var/db/certs/system-cert/system-generated.cert
2       /cf/var/db/certs/system-key-pair/system-generated.priv
2       /cf/var/db/commits
2       /cf/var/db/idpd/db/cache.dbd
2       /cf/var/db/idpd/db/rdm.taf
2       /cf/var/db/idpd/sec-download/platforms.xml
2       /cf/var/db/idpd/sec-download/sub-download/SignatureUpdate.xml
2       /cf/var/db/kmd_rpd.db
2       /cf/var/db/leases/01c42c03116d78.jdl
2       /cf/var/db/nat_rpd.db
2       /cf/var/db/ntp.drift
2       /cf/var/db/snmp_engine.db
2       /cf/var/home/admin/.ssh/known_hosts
2       /cf/var/jail/etc/auth.conf
2       /cf/var/jail/etc/group
2       /cf/var/jail/etc/httpd.conf
2       /cf/var/jail/etc/localtime
2       /cf/var/jail/etc/master.passwd
2       /cf/var/jail/etc/pam.conf
2       /cf/var/jail/etc/passwd
2       /cf/var/jail/etc/resolv.conf
2       /cf/var/log/__jsrpd_commit_check__
2       /cf/var/log/authd_sdb.log
2       /cf/var/log/dfwd
2       /cf/var/log/eccd
2       /cf/var/log/hostname-cached
2       /cf/var/log/httpd.log.old
2       /cf/var/log/install
2       /cf/var/log/interactive-commands
2       /cf/var/log/inventory
2       /cf/var/log/mastership
2       /cf/var/log/messages
2       /cf/var/log/nstraced_chk_only
2       /cf/var/log/op-script.log
2       /cf/var/log/pf
2       /cf/var/log/pgmd
2       /cf/var/log/snapshot
2       /cf/var/sw/pkg/rollback
4       /cf/var/db/feature.db
4       /cf/var/db/idpd/_compilemmap
4       /cf/var/db/idpd/_mmap
4       /cf/var/db/idpd/db/secdb.d08
4       /cf/var/db/idpd/db/secdb.d09
4       /cf/var/db/idpd/db/secdb.d10
4       /cf/var/db/idpd/db/secdb.d11
4       /cf/var/db/idpd/db/secdb.d12
4       /cf/var/db/idpd/db/secdb.d13
4       /cf/var/db/idpd/db/secdb.dbd
4       /cf/var/db/scripts/op/int.xslt
4       /cf/var/jail/etc/login.conf
4       /cf/var/log/cosd
4       /cf/var/log/gres-tp
6       /cf/var/db/certs/FeatureLicense-v2.pem
6       /cf/var/db/dcd.snmp_ix
6       /cf/var/db/idpd/sec-repository/application.list
6       /cf/var/db/scripts/commit/DNS_Service
8       /cf/var/db/idpd/db/secdb.d07
8       /cf/var/db/idpd/db/secdb.d14
8       /cf/var/db/idpd/db/secdb.d15
8       /cf/var/db/idpd/db/secdb.k16
8       /cf/var/db/idpd/db/secdb.k17
8       /cf/var/db/idpd/db/secdb.k18
8       /cf/var/db/idpd/db/secdb.k19
8       /cf/var/db/idpd/db/secdb.k22
8       /cf/var/db/scripts/commit/Getting_Started
8       /cf/var/db/scripts/commit/Web_Server
10      /cf/var/db/scripts/commit/DMZ_Services
10      /cf/var/db/scripts/commit/File_Server
10      /cf/var/db/scripts/commit/Recommended
12      /cf/var/db/idpd/db/dfa_group.k02
12      /cf/var/db/idpd/db/pcre.k03
12      /cf/var/db/scripts/commit/IDP_Default
12      /cf/var/log/dcd
14      /cf/var/db/idpd/sets/DNS_Service.set
14      /cf/var/log/rtlogd
16      /cf/var/db/ext_id_map.db
20      /cf/var/log/cscript.log
22      /cf/var/log/httpd.log
28      /cf/var/db/idpd/db/secdb.d05
30      /cf/var/db/idpd/bins/Recommended.jpme.input
32      /cf/var/log/kmd
36      /cf/var/log/jsrpd
36      /cf/var/log/nsd_chk_only
40      /cf/var/jail/etc/pwd.db
40      /cf/var/jail/etc/spwd.db
44      /cf/var/db/idpd/db/secdb.k15
48      /cf/var/log/chassisd
56      /cf/var/db/idpd/sec-download/sub-download/templates.xml
56      /cf/var/db/scripts/commit/templates.xsl
60      /cf/var/db/idpd/bins/Recommended.jpme.output
60      /cf/var/db/idpd/bins/last-good-policy.jpme.output
72      /cf/var/db/idpd/db/pcre.d03
134     /cf/var/db/idpd/sec-repository/attack-group.list
136     /cf/var/db/idpd/db/secdb.k07
136     /cf/var/db/idpd/db/secdb.k09
140     /cf/var/db/idpd/db/secdb.k04
140     /cf/var/db/idpd/db/secdb.k05
140     /cf/var/db/idpd/db/secdb.k06
140     /cf/var/db/idpd/db/secdb.k08
140     /cf/var/db/idpd/db/secdb.k10
140     /cf/var/db/idpd/db/secdb.k11
140     /cf/var/db/idpd/db/secdb.k14
154     /cf/var/db/idpd/sec-repository/attack.list
164     /cf/var/db/idpd/db/secdb.k20
164     /cf/var/db/idpd/sets/Recommended.set
176     /cf/var/db/idpd/db/dfa.k01
192     /cf/var/db/idpd/bins/Recommended.bin.gz.v
192     /cf/var/db/idpd/bins/last-good-policy.bin.gz.v
224     /cf/var/db/idpd/sets/File_Server.set
240     /cf/var/db/idpd/db/secdb.k02
368     /cf/var/db/idpd/db/secdb.k12
464     /cf/var/db/idpd/db/secdb.d06
528     /cf/var/db/idpd/sets/Web_Server.set
624     /cf/var/db/idpd/db/dfa_group.d02
672     /cf/var/db/idpd/sec-download/detector-capabilities.xml
672     /cf/var/db/idpd/sets/DMZ_Services.set
720     /cf/var/db/idpd/sec-download/applications.xml
752     /cf/var/db/idpd/db/secdb.d03
800     /cf/var/db/idpd/sets/Getting_Started.set
848     /cf/var/db/idpd/db/secdb.k03
1152    /cf/var/db/idpd/db/dfa.d01
1216    /cf/var/db/idpd/sets/IDP_Default.set
1264    /cf/var/db/idpd/db/secdb.k13
1472    /cf/var/db/idpd/db/secdb.k21
1504    /cf/var/db/idpd/bins/compiled_ai.bin
1552    /cf/var/db/idpd/bins/libidp-detector.so.tgz.v
1552    /cf/var/db/idpd/sec-download/libidp-detector.so.tgz.v
1552    /cf/var/db/idpd/sec-repository/installed-detector/libidp-detector.so.tgz.v
1552    /cf/var/db/idpd/sec-repository/libidp-detector.so.tgz.v
2304    /cf/var/db/idpd/bins/compressed_ai.bin
2496    /cf/var/db/idpd/db/secdb.k01
3888    /cf/var/db/idpd/db/secdb.d01
4848    /cf/var/db/idpd/sec-download/groups.xml
8144    /cf/var/db/idpd/db/secdb.d04
26864   /cf/var/db/idpd/sec-download/SignatureUpdate.xml
28256   /cf/var/db/idpd/db/secdb.d02
43696   /cf/var/db/idpd/db/secdb_child.log
root@SRX-210% exit
exit

root@SRX-210> show system storage 
Filesystem              Size       Used      Avail  Capacity   Mounted on
/dev/da0s1a             293M       203M        67M       75%  /
devfs                   1.0K       1.0K         0B      100%  /dev
/dev/md0                567M       567M         0B      100%  /junos
/cf                     293M       203M        67M       75%  /junos/cf
devfs                   1.0K       1.0K         0B      100%  /junos/dev/
procfs                  4.0K       4.0K         0B      100%  /proc
/dev/bo0s3e              24M        50K        22M        0%  /config
/dev/bo0s3f             342M       141M       174M       45%  /cf/var
/dev/md1                168M        15M       139M       10%  /mfs
/cf/var/jail            342M       141M       174M       45%  /jail/var
/cf/var/log             342M       141M       174M       45%  /jail/var/log
devfs                   1.0K       1.0K         0B      100%  /jail/dev
/dev/md2                 39M       4.0K        36M        0%  /mfs/var/run/utm
/dev/md3                1.8M       4.0K       1.7M        0%  /jail/mfs

 

so as you can see, IDP is consuming a significant chunk of space...and i'm hesitant to even try deleting anything Smiley Tongue  I tried to view the last file since the filename looks to be a log file, but I get greeted by something like this:

 

 

43696   /cf/var/db/idpd/db/secdb_child.log
root@RX-210% less /cf/var/db/idpd/db/secdb_child.log 
^@%^P^@/var/db/idpd/db/secdb.d01^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^P^@/var/db/idpd/db/secdb.d02^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^P^@/var/db/idpd/db/secdb.d03^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^P^@/var/db/idpd/db/secdb.d04^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@

 

 

and it continues that for a good long while.  So i'm not sure if it is a log file with just a bunch of crap in it, or if its actually some kind of binary or who knows what.  But i've let it be for now Smiley Tongue

 

about to finally try the upgrade direct from USB -- we'll see how that goes!

 

 

Will

 

Recognized Expert
Posts: 286
Registered: ‎04-03-2009
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

well I upgraded to 10.3R1...wasn't the smoothest of upgrades Smiley Tongue

 

install from USB was fine, but when I rebooted, it wasn't coming back after a while (even allowing for the SRX boot time...), so I broke out the console cable.

 

Not sure what happened -- guess I should have been consoled in from the start! -- but it came up in a Default state, but with my config in an uncommitted state.

 

I saved off the config, and for kicks I booted without committing anything.  It booted and came up correctly this go-round with the proper config.  Not sure what was up, but just glad it wasn't a remote device...

 

 

Moral of the story -- test upgrades on lab devices first! Smiley Tongue

 

Will

New User
Posts: 1
Registered: ‎12-05-2010
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

As long as you don't have any logs that you need off of the box you can do a:
"request system storage cleanup"

 

That should do the trick for freeing up space.  Just make sure to have a copy of the config if the upgrade goes sideways ;-)

Trusted Contributor
Posts: 330
Registered: ‎01-08-2010
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

My manual upgrade procedure is as follows (note I don't care about local logs since I use a logging server):

 

1. "request system storage cleanup" and select yes to delete all.

2. check the root of /var/tmp for any old firmware files not deleted by the cleanup and delete them

3. SFTP (WinSCP is a handy client) the firmware file to /var/tmp

4. "request system software add /var/tmp/[JUNOS_FILENAME] no-copy no-validate reboot"

 

Wait for firmware to install and reboot.

Contributor
Posts: 46
Registered: ‎06-05-2009
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

Having just spent a considerable amount of time on with JTAC on this issue (and getting nowhere other than trying the same things I already did + getting sent KB articles) I pursued this a bit further.

 

IDP is the issue - takes up significant space.

 

Long story short, remove IDP from your configuration on a temporary basis and reboot.  Then you should have enough space to perform the upgrade - after which re-enable IDP.

 

We have MANY of the SRX boxes and work on them remotely (only method of upgrading them for us) - this method seems to be the only reliable way of doing it.  HTTP/FTP etc all copy to the local filesystem and then perform the upgrade - there is no way (other than USB) to "upgrade on the wire".

 

Paul

JNCIA-JUNOS/JNCIS-ENT/JNCIS-SEC
Juniper Partner Ingenious Champion
Regular Visitor
Posts: 8
Registered: ‎01-08-2011
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

I had some luck with this by deleting the incoming-package.<some number> file in /var/tmp and then using no-copy no-validate

Contributor
Posts: 47
Registered: ‎09-27-2009
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!


tomheron1 wrote:

I had some luck with this by deleting the incoming-package.<some number> file in /var/tmp and then using no-copy no-validate


In addition the unlink option will free up space by removing the install package at the earliest possible opportunity.

 

Aidan

Juniper Employee
Posts: 6
Registered: ‎11-23-2009
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

I experienced this similar issue on my recently purchased SRX100H where I was not able to upgrade from 10.4R4 to 11.2R2 due to not having enough space no other message.  Ran the usual commands to clear up space but that didn't help either.

 

request system storage cleanup

request system software delete-backup

 

Eventually, what I ended up doing was logging in as "root", verifying my bootloader version and then running the command in the shell to update it.

 

show chassis routing-engine bios

 

start shell
bootupgrade –u /boot/uboot –l /boot/loader

 

exit

request system reboot

 

Once the SRX100H rebooted, I then logged back in as "root" and update the software via USB (I'm sure tftp or ftp would work just as well) running the following cli.

 

request system software no-validate reboot add /var/tmp/usb0/1-Branch_SRX/1-junos-srxsme-11.2R2.4-domestic.tgz

 

I'm not sure if this combination was the key in upgrading the SRX100H to Junos 11.2R2.  Not sure also if you have to upgrade using "root" as I might have been trying to upgrade Junos using a superuser account called "r00t".  Perhaps when space is an issue, "root" is able to purge or access space where other accounts cannot?  Either way, hopefully this helps others.

- PM
Trusted Contributor
Posts: 1,048
Registered: ‎09-26-2011
0 Kudos

Re: Upgrading to 10.3R1 . . . but I have no space!

Hi all,

I'm still having problem upgrading to the latest firmware on SRX 210, using the ftp method?

Is there a way to do it?

Pls help.
Thanks!

Michael
JNCIA-JUNOS, JNCIS-ENT/SEC, JNCIP-ENT
(CCNA, ACMP, ACFE, CISE)
"http://www.thechampioncommunity.com/"
CONNECT EVERYTHING. EMPOWER EVERYONE.
Share & Learn. Knowledge is Power.

"If there's a will, there's a way!"