It’s been a while since I looked at my 1D as it just does it’s thing so well. However, I was surprised to hear we’d had a small shake the other day and went to look at the Helicorder file on the local web page. Selecting a file brings up 404 error. Can anyone tell me if this is a known issue or something that’s new and exciting to look at! So 1D, on Pi3 and OS 0.20
The Pi has been rebooted and the SD has plenty of space:
Really happy to hear that your RS1D is performing well and providing you with good data!
Is the 404 error happening for every link in the helicorder page? That is, you are not able to see any helicorder image on the Shake?
From the stats everything appears all right, however, could you please download the logs from the Shake (instructions here: Please read before posting!) and attach them to your answer?
Also, if the earthquake you wanted to check was the June 26th Cook Strait M4.6 one, it was perfectly captured by your Shake. Quite a beautiful waveform, I may add.
All the links on the “Recent Helicorder Displays” pages display a 404 error so at least it’s consistent. Sorry I didn’t attach the log tar file… Here’s the latest. RSH.R7B0A.2022-06-30T08_21_27.logs.tar (3.1 MB)
It’s not a big deal as there seem to many other options to look at them but I was a little worried the SD card might be on the way out. I might sort out a new one tomorrow.
Thank you for the logs, these were among the cleanest ones that I had my eyes upon, so there is good confirmation that your Shake is working fine.
The only “unusual” appearances are some Permission denied lines, that may be the cause of why the helicorder images are not being displayed (or created in the first place).
It may be related to some microSD card issues, so, if you want, I will leave the burning instructions here for your convenience:
Please take the microSD card you have and format it before burning the new Shake OS image
Make sure, when you format it, that the shown capacity is the maximum (i.e. if the SD card is 32GB like yours, then the capacity should be near or equal to that value). This is to check that no partitions have been involuntarily and erroneously created. They could be the cause of the error we see now
Take care to format the SD card in a FAT32 File System (or exFAT if the SD card is 64GB or larger)
If you acquire a second microSD card, I would also advise to leave the current working one untouched, so that, if there are issues during the burning process, you will have a ready backup in place.
