- 22 Oct 2020 [10:04]
- ... Fixed by John Aldridge "The file system on the memory stick is corrupt. I've reinitialized the file system on the existing memory stick, and I've added 3sec to last_drift to bring the logged data back into line with the data as of a week ago (I hope). Everything *seems* to be running OK. Let's see whether it stays fixed, or whether it breaks again! The symptoms now make sense: clocklogger was unable to read the last_drift (because of the corrupt filing system), was therefore assuming 0"
Download data