This post is also written in English. You may access it here: Disk space issues when upgrading to Junos 9.6 in M7i.

He tenido que actualizar recientemente un router de Juniper M7i, que tenía una versión de Junos 8.5, y 256 MB de memoria RAM. En primer lugar, es requisito para la versión 9.6 del sistema operativo que el router disponga de 512 MB de memoria en la controladora, y se recomiendan 768 MB. Por tanto, después de aumentarle la memoria a 768 MB, se podía actualizar el sistema. O quizá no.

Comando para actualizar por defecto:

request system software add jinstall-9.6R1.13-domestic-signed.tgz

Primer problema: la imagen no pasa la validación. Este es muy fácil de resolver:

request system software add jinstall-9.6R1.13-domestic-signed.tgz no-validate

Segundo problema: no hay espacio en disco. Mensaje que muestra:

tid@m7i> …ce jinstall-9.6R1.13-domestic-signed.tgz

Installing package ‘/mfs/var/home/tid/jinstall-9.6R1.13-domestic-signed.tgz’ …

tar: jinstall-9.6R1.13-domestic.tgz: Wrote only 0 of 10240 bytes

tar: certs.pem: Wrote only 0 of 10240 bytes

tar: Error exit delayed from previous errors

WARNING: Not enough space in /var/tmp to unpack jinstall-9.6R1.13-domestic-signed.tgz

WARNING: Use ‘request system storage cleanup’ and

WARNING: the ‘unlink’ option to improve the chances of success

Viendo el aspecto de las particiones podemos hacernos una idea de por dónde van los tiros:

Filesystem Size Used Avail Capacity Mounted on

/dev/ad1s1a 217M 98M 102M 49% /

devfs 1.0K 1.0K 0B 100% /dev

devfs 1.0K 1.0K 0B 100% /dev/

/dev/md0 23M 23M 0B 100% /packages/mnt/jbase

/dev/md1 80M 80M 0B 100% /packages/mnt/jkernel-8.5R4.3

/dev/md2 8.8M 8.8M 0B 100% /packages/mnt/jpfe-M7i-8.5R4.3

/dev/md3 3.5M 3.5M 0B 100% /packages/mnt/jdocs-8.5R4.3

/dev/md4 28M 28M 0B 100% /packages/mnt/jroute-8.5R4.3

/dev/md5 8.8M 8.8M 0B 100% /packages/mnt/jcrypto-8.5R4.3

/dev/md6 37M 37M 0B 100% /packages/mnt/jpfe-common-8.5R4.3

/dev/md7 504M 232M 231M 50% /tmp

/dev/md8 504M 277M 186M 60% /mfs

/dev/ad1s1e 24M 28K 22M 0% /config

procfs 4.0K 4.0K 0B 100% /proc

Sin embargo, en los mensajes del arranque se ve que el disco duro es bastante más grande que eso:

ad1: 28615MB <FUJITSU MHT2030AR 959C> at ata0-slave UDMA33

Algo falla ¿no? Efectivamente, el contenido de /etc/fstab revela particiones no montadas, en particular:

/dev/ad1s1f /var ufs rw,noauto 2 0

Montándola aparece una partición de 27 GB:

/dev/ad1s1f 27G 595M 24G 2% /mfs/var

Una vez montada la partición, la instalación se hace sin problemas, y después de reiniciar ya está disponible la versión de Junos 9.6.

Este texto está disponible en español: Problemas de disco al actualizar a Junos 9.6 en M7i.

I recently had to upgrade the operating system in a Juniper M7i router which was running Junos 8.5 and had 256 MB of RAM. First, a requisite to run Junos 9.6 is 512 MB of RAM in the routing controller, and 768 MB is recommended. I upgraded to 768 MB and I thought that was going to be it.

To perform a system upgrade, you have to issue this command:

request system software add jinstall-9.6R1.13-domestic-signed.tgz

The first problem that appears is that the
package does not validate. However, this is piece of cake:

request system software add jinstall-9.6R1.13-domestic-signed.tgz no-validate

Second problem: no disk space available. The message is shown below:

tid@m7i> …ce jinstall-9.6R1.13-domestic-signed.tgz

Installing package ‘/mfs/var/home/tid/jinstall-9.6R1.13-domestic-signed.tgz’ …

tar: jinstall-9.6R1.13-domestic.tgz: Wrote only 0 of 10240 bytes

tar: certs.pem: Wrote only 0 of 10240 bytes

tar: Error exit delayed from previous errors

WARNING: Not enough space in /var/tmp to unpack jinstall-9.6R1.13-domestic-signed.tgz

WARNING: Use ‘request system storage cleanup’ and

WARNING: the ‘unlink’ option to improve the chances of success

After entering the command shell and running «df», we may have an idea of where the problem is:

Filesystem Size Used Avail Capacity Mounted on

/dev/ad1s1a 217M 98M 102M 49% /

devfs 1.0K 1.0K 0B 100% /dev

devfs 1.0K 1.0K 0B 100% /dev/

/dev/md0 23M 23M 0B 100% /packages/mnt/jbase

/dev/md1 80M 80M 0B 100% /packages/mnt/jkernel-8.5R4.3

/dev/md2 8.8M 8.8M 0B 100% /packages/mnt/jpfe-M7i-8.5R4.3

/dev/md3 3.5M 3.5M 0B 100% /packages/mnt/jdocs-8.5R4.3

/dev/md4 28M 28M 0B 100% /packages/mnt/jroute-8.5R4.3

/dev/md5 8.8M 8.8M 0B 100% /packages/mnt/jcrypto-8.5R4.3

/dev/md6 37M 37M 0B 100% /packages/mnt/jpfe-common-8.5R4.3

/dev/md7 504M 232M 231M 50% /tmp

/dev/md8 504M 277M 186M 60% /mfs

/dev/ad1s1e 24M 28K 22M 0% /config

procfs 4.0K 4.0K 0B 100% /proc

That is weird, isn’t it? The boot messages show that the hard disk is quite bigger than that:

ad1: 28615MB <FUJITSU MHT2030AR 959C> at ata0-slave UDMA33

So there is something wrong, right? Right. «cat /etc/fstab» reveals umounted partitions, for instance:

/dev/ad1s1f /var ufs rw,noauto 2 0

After mounting /dev/ad1s1f, a 27 GB partition appears:

/dev/ad1s1f 27G 595M 24G 2% /mfs/var

There it is, we have plenty of space to perform the upgrade. This was a big headache, after all. I hope that anyone having the same problems may find this helpful.