Replacing /etc/init.d/autostart on EAMs

Contents

• Scope
• Introduction
• Preparation
• Booting
• Replacing the missing file

Scope

This procedure applies to EAMs and products containing EAMs. Compatible products are those without red crosses in the following table. If your product is not listed, please contact for advice.

DM24S3EAM DM24S6EAM	or
3TDE
3ESPCDE
40TDE
5TCDE
EAM
Affinity		The Affinity requires a different procedure. Please contact for details.
DCM		The DCM requires a different procedure. Please contact for details.

Introduction

This procedure is a response to two reports of a missing /etc/init.d/autostart file, which makes console access impossible.

Preparation

Physical access to the unit will be required.

Equipment required:

• Console cable (either a 12-way military-specification bayonet connector to DE9 for digital sensors or metal cylindrical units, or a standard 9-pin serial cable for Peli-case variants).
• Laptop or PC with serial port or USB to RS232 adapter.
• Terminal emulator (e.g. PuTTY under Windows or minicom under Linux).

A suitable rsync/upgrade server is required. You therefore need either:

• Internet access (to rsync.guralp.com TCP port 873/rsync); or
• a local rsync server with a copy of the firmware on (refer to the local mirror instructions for details about setting up a local mirror)

Booting

1. Connect the console cable to the EAM and to the laptop/PC (the "recovery machine").

2. Open the terminal emulator on the recovery machine and set it to 38400 baud, 8N1.

3. Apply power to the EAM.

4. Almost immediately, there should be some output. Approximately two screens (2×25 lines) of output will be displayed.

5. There will be a series of yes or no questions. Answer no (by pressing the n key) to each question. Very old bootloaders have some minor differences, but the questions should be as below. If any question is accidentally answered yes, it is safe to simply remove and re-apply power, starting the process again.

   Boot-up procedure questions:

   Attempt rsync update ? (y/N) n Boot main via kexec ? (Y/n) n Boot main via switch_root ? (y/N) n Mount successful but no boot options available Attempt scripted NAND device reinstall ? (y/N) n

   At this point, you are now at a shell prompt:

   / #

   and can continue the process as below.

Replacing the missing file

This procedure is involved, and you may prefer to return the unit to Guralp support, but instructions are presented below for users willing to attempt the procedure.

Set up networking

The required configuration for the network depends on whether you use DHCP on your local network or not.

• If you use DHCP to configure your network, run:

  ifconfig lo 127.0.0.1 route add -net 127.0.0.0 netmask 255.0.0.0 lo udhcpc --script /etc/udhcpc.sh --now --interface eth0

• If you are not using DHCP and need to assign your networking parameters statically, find the correct values and then run:

  ifconfig lo 127.0.0.1 route add -net 127.0.0.0 netmask 255.0.0.0 lo ifconfig eth0 192.0.2.2 netmask 255.255.255.0 route add default gw 192.0.2.1 echo "nameserver 1.1.1.1"> /etc/resolv.conf

  replacing…

  • 192.0.2.2 with the desired IP address;
  • 255.255.255.0 with the desired netmask;
  • 192.0.2.1 with the IP address of your default router; and
  • 1.1.1.1 with the IP address of a suitable DNS server. Most people can use 1.1.1.1 (operated by Cloudflare) for this purpose but, if it is blocked in your jurisdiction, search the Internet for free public DNS servers for a list of other suitable addresses.

Set system date

The date must be set to something sensible because, otherwise, files will have incorrect modification times, which will cause various malfunctions. In the command below, replace:

• mm with the Month (01 to 12);
• dd with the Day (01 to 31);
• HH with the Hour (00 to 23);
• MM with the Minute (00 to 59); and
• YYYY with the Year (2011 upwards)

The command should be entered as

The data and time should be entered in UTC, regardless of your current time zone.

Copy the file on

In the example below it may be necessary to replace rsync.guralp.com with its IP address (currently 46.43.14.141) or with the name of your local rsync server. This step will download about 50Mb of image data.

If this step fails at start-up (with error messages like temporary failure in name resolution, no route to host, etc.) then something is wrong with the networking configuration. If, instead, it fails part way through, or at the end, something is likely wrong with the unit and it will need to be returned to the factory.

Finalise

Now it is safe to power cycle the unit. You can also boot the new system without power cycling by running:

You can watch its boot progress on the console port. You should eventually have a login: prompt, at which point you can log in as root using your normal password.

This completes the procedure.