RS4D Station Offline and No Longer Visible on Station View

Technical Support
1

Dear Raspberry Shake Support Team,

I am contacting you regarding an issue with our Raspberry Shake station.

Station information
Model: Raspberry Shake 4D (RS4D)
Station ID: R9AF3

The station had been operating normally and transmitting data to the Raspberry Shake platform. The data were publicly available through the Raspberry Shake network.

However, several months ago, we noticed that:

  • Waveforms were no longer visible on the Raspberry Shake web platform.
  • The station disappeared from Station View.
  • No new data appears to be reaching the Raspberry Shake servers.

To investigate the problem, I accessed the instrument via SSH and checked its status.

Current Status

The device is still accessible through rs.local , and the status page reports:

  • Internet: Online
  • Services: Down
  • Server Connection: Inactive

In addition, when attempting to change settings or reboot the device from the rs.local interface, a password is requested. However, after entering the password, the requested action does not proceed.

Diagnostic Results

Network Connectivity

The instrument appears to have internet access and can successfully reach Raspberry Shake infrastructure:

PING hzcaps1.raspberryshake.org (188.40.209.188)
Reply received successfully.

Raspberry Shake Service

The Raspberry Shake service is failing during startup:

â—Ź raspberryshake.service - Raspberry Shake Boot Script
Loaded: loaded (/lib/systemd/system/raspberryshake.service; enabled)
Active: failed (Result: exit-code)

ExecStart=/usr/local/bin/postboot.rshake
(code=exited, status=1/FAILURE)

The service log shows that the boot script begins execution and proceeds through several initialization steps before terminating with exit status 1:

Jun 18 05:22:53 Starting Raspberry Shake Boot Script...
Jun 18 05:24:19 raspberryshake.service: Main process exited, code=exited, status=1/FAILURE
Jun 18 05:24:19 Failed to start Raspberry Shake Boot Script.

Storage Status

The root filesystem is completely full:

Filesystem      Size  Used Avail Use% Mounted on
/dev/root       7.4G  7.3G     0 100% /

Inode usage is normal:

IUse% = 39%

Most of the used storage appears to be archived waveform data:

4.2G  /opt/data/archive
1.9G  /opt/data/archive/2025/AM/R9AF3
2.4G  /opt/data/archive/2026/AM/R9AF3

Questions

Based on these observations, we suspect that storage exhaustion may be related to the service failure, but we would appreciate your advice.

Could you please advise:

  1. Whether the full root filesystem is likely to be causing the Raspberry Shake service failure.
  2. Which files or directories can be safely removed or archived to recover disk space.
  3. Whether there is a recommended recovery procedure for this situation.
  4. How we can restore communication with the Raspberry Shake servers and make the station visible again in Station View.

I will be happy to provide any additional logs, screenshots, or diagnostic information if needed.

Thank you very much for your assistance.

Best regards,

2

Hello BuRi, and welcome back to the community!

Thank you very much for the extensive and detailed troubleshooting you’ve already done.

The first thing to do next (if you haven’t already) is to save all the data you have stored on the Shake. Since you can access it via SSH, you can use a program such as FileZilla or a similar one to download everything the Shake recorded until it stopped. A comprehensive list can be found here.

Onto your questions:

  1. It is possible, yes. If there isn’t anything else at play (like a corrupted microSD card), the lack of space can be the cause behind what you’re seeing
  2. Only after you have saved all data (because after this, what you delete will become unrecoverable), you can then try to, always via SSH:
    • delete the 2025 directory with sudo rm -r /opt/data/archive/2025
    • manually reboot the Shake via SSH with the command sudo reboot
  3. The data download/backup procedure illustrated above is what can usually be recommended
  4. After the reboot, the Shake should resume standard operations

If it doesn’t, there are other avenues we can explore. And yes, if you could send the full log file set (the entire content of the opt/log/ directory, if you are acquiring it via SSH), it would be very useful.

1 Like
3

Thank you very much for your kind guidance.

Following your instructions, I deleted the archive directories and rebooted the RS4D. The station has now resumed normal operation, and I can see it again on the Raspberry Shake map.

I appreciate your prompt and helpful support.

1 Like
4

You’re more than welcome, happy to read that everything is back online!

For future reference, you can calculate the maximum amount of data you can store on your microSD using this template and its variations.