Hello All, I hope you can shed some light on this problem. Here are the details…
Station: R907E
Hardware: Raspberry Shake RS4D
Storage: 8 GB microSD card
Operating system: “Raspbian GNU/Linux 8 (jessie)”
Background
My Raspberry Shake (R907E) stopped reporting seismic activity about two years ago. I finally got the unit back inside, connected a monitor and keyboard, and was able to boot the Raspberry Pi successfully. The Linux operating system appears to be functioning, but the station is not reporting data as expected.
During troubleshooting, I discovered that the root filesystem is completely full.
1. Filesystem Status
Running df -h reports:
Filesystem Size Used Avail Use%
/dev/root 7.4G 7.2G 0 100%
Other mounted filesystems show little or no usage.
2. Directory Usage
Running sudo du -xhd1 / identified the following major directories:
/opt 4.0G
/var 2.0G
/usr 831M
/lib 430M
Further investigation of /opt showed:
/opt/data 3.9G
/opt/log 1.9M
/opt/DL 47M
And /opt/data contains:
/opt/data/gifs 3.8G
/opt/data/archive 144M
The GIF directory contains approximately 10,997 GIF files .
The oldest files are dated September 20, 2021, and the newest files are dated October 30, 2026.
Interestingly, some helicorder GIFs are still being generated, suggesting that at least portions of the Raspberry Shake software remain operational.
3. System Log Usage
The /var/log directory occupies approximately 1 GB.
The largest files are:
daemon.log.1 468M
daemon.log 229M
syslog 229M
syslog.1 89M
Both daemon.log and syslog are actively being updated.
I have not yet examined their contents to determine whether recurring errors account for their unusually large sizes.
4. Kernel Messages
One of the last kernel messages I found was:
ttyS ttyS0: 1 input overrun(s)
I understand this indicates a serial-port receive overrun, although I don’t know whether it is related to the reporting failure.
I also checked for undervoltage or throttling messages using:
dmesg | grep -i -E 'voltage|under-voltage|throttl'
No messages were returned.
5. Questions
at this point, I cannot even create a temp file: “No space left on device”
Before deleting files or rebuilding the microSD card, I would appreciate some guidance.
- GIF retention: Is it normal for
/opt/data/gifsto accumulate several years of helicorder images? Should older GIF files be automatically deleted? - Disk recovery: Is there a recommended procedure for safely removing older GIF files and recovering disk space without affecting the Raspberry Shake installation?
- System logs: Are the large
daemon.logandsyslogfiles indicative of a known Raspberry Shake problem? - Data acquisition: Since helicorder GIFs are still being generated, is there a recommended method for determining whether the seismic acquisition hardware is operating correctly?
- Network reporting: After recovering disk space, what is the recommended procedure for verifying or restoring data transmission to the Raspberry Shake network?
- Software recovery: Given the age of this installation, would you recommend repairing the existing system or installing a current Raspberry Shake image on a larger microSD card?
My preference is to recover the existing installation if possible, particularly to preserve its configuration and any diagnostic information that might explain the original failure.
Any recommendations would be appreciated. Thanks!
Jim
AM.R907E