Description

[MX960] [ RE-S-1800X4-16G-BB] Error: not enough space to unpack.

Symptoms

1):There might be a case where an upgrade can fail stating not enough space available on the disk


labroot@MX960>request system software add re1 /var/tmp/junos-install-mx-x86-64-22.2R3-S1.9.tgz no-validate


- Error detected: labroot@MX960> ...4-22.2R3-S1.9.tgz no-validate

contents/jpfe-ulc.tgz: truncated gzip input

tar: Error exit delayed from previous errors.

Error: not enough space to unpack /var/tmp/junos-install-mx-x86-64-22.2R3-S1.9.tgz

ERROR: Either use 'force' or consider deleting snapshots using 'request system snapshot delete <snap>'


2) We have already tried below steps.

2a) Customer has deleted old files from RE0 and RE1.

2b) Rebooted RE1


3) Still upgrade is failing even though we have enough space.


labroot@MX960> show system storage invoke-on all-routing-engines 

re0:

--------------------------------------------------------------------------

Filesystem       Size    Used   Avail Capacity  Mounted on

/dev/gpt/junos     10.0G    3.7G    5.5G    40% /.mount

/dev/gpt/config     446M    604K    410M    0% /.mount/config

/dev/gpt/var       14G    8.6G    4.3G    66% /.mount/var

tmpfs          35G    28K    35G    0% /.mount/tmp

tmpfs          8.0G    2.8M    8.0G    0% /.mount/mfs


re1:

--------------------------------------------------------------------------

Filesystem       Size    Used   Avail Capacity  Mounted on

/dev/gpt/junos     10.0G    1.5G    7.6G    17% /.mount

/dev/gpt/config     446M    768K    410M    0% /.mount/config

/dev/gpt/var       14G    5.6G    7.4G    43% /.mount/var

tmpfs          46G    28K    46G    0% /.mount/tmp

tmpfs          8.0G    2.6M    8.0G    0% /.mount/mfs


labroot@MX960

Solution

Sometimes even we can see there is disk Space available on the device even though upgrade is failing. Checksum Mismatch can cause this issue as well. It is advisable to delete the image and reupload the image on the RE.

Modification History

2024-09-27 : Article Created