- Instructions for upgrading from build 3801 (or earlier)
- Disk space
- Performing the upgrade
- Notes for advanced users
- If you use /etc/conf.d/upgrade.local
- EABI background
On any Guralp Systems module running Platinum, you can check the system type (to ensure it is an EAM) and the release currently installed by following the Version and serial numbers link in the Summary menu in the left-hand menu pane of the web interface. If your system does not have this menu item, the information is displayed in the Linux system tab of the status page.
In order to upgrade from release 3801 (or earlier) of Platinum to the most recent stable release, there is an extra step required on EAM units. This is because of a change to the Linux system architecture (ABI), which necessitates replacing each file on the unit. A script has been added to the release to do this but the process must be started manually.
Please note this change only applies to EAM units. DCM units and NAM or NAM64 units are not affected and will upgrade to the most recent Platinum release without intervention.EAM manual (section First steps) for instructions on connecting this way. The rest of this document assumes you are connected either over a serial port or over SSH. If you are connected to a remote system using SSH, then it is advisable to use GNU screen to protect your connection. Simply run the command:
screenand press Enter to clear its banner screen. If your connection is interrupted, whatever is running inside screen will continue to run in your absence, and you can reconnect to it by reconnecting to the system again and running:
screen -rEnsure the EAM can reach the rsync server for performing the upgrade, and that it is at build 3801, by running the command:
upgradeVerify at the end of the output that you see the message:
Upgrade complete. Now at platinum-stable build 3801.
df -h(the Unix command "disk free", with "human-readable" units). This will print a summary of how much space is free on the flash filesystems. On some example systems, this command produced the following outputs:
Filesystem Size Used Available Use% Mounted on /dev/root 512.0M 184.3M 327.7M 36% / /dev/mtdblock3 2.0G 862.3M 1.2G 42% /media/flash_module Filesystem Size Used Available Use% Mounted on /dev/root 512.0M 141.4M 370.6M 28% /The line mentioning
/dev/rootis the important one. It should have at least 64MByte in the
Availablecolumn. If it does not, some space must be freed; the simplest way to do this is to reconfigure one of the services that stores backfill (gdi2gcf, gdi2miniseed, data-mux-cd11 or gdi-link-tx). Please contact support if you require assistance discovering where space has been used and how to free it.
EAM-upgrade-to-eabi.shThis will copy the files from the rsync server onto the EAM, displaying its progress as it goes. This process will take only 2 or 3 minutes if you have a fast connection but depends primarily on connection speed. Once this is done, the files are moved into place, and you will see some messages:
(you can safely ignore Segmentation fault messages above) :::: Rebooting to complete upgrade.At this point the system will reboot itself automatically and complete the upgrade process (part of which is automatically migrating all the existing configuration to the new system).
/etc/conf.d/upgrade.local. There are several points to check:
- Make sure
RSYNC_ADDITIONAL_OPTSis not set in
/etc/conf.d/upgrade.local. This variable is used by the EABI upgrade script and must not be overridden.
- Check that the rsync module being referred to contains (at least) the
- Check that the firmware version in the
CMG-DCM-mk4directory is up to date: i.e. cat (read) the file
CMG-DCM-mk4/etc/build.versionto verify that the build number is 3801.