Black Hole
May contain traces of nut
I'm getting this on a frequent basis, on a HDR-FOX and a HD-FOX, but the HD-FOX is the current case in point. I'm posting in the CF section only because CF will be involved in the process of diagnosis.
Left to its own devices over the weekend (not in standby), the unit in question recorded on Saturday evening but nothing after that. This morning, it didn't do what it had been scheduled to do, and when I checked the schedule was empty (as I have come to expect). WebIF still works, and there is nothing reported in the crash log (not recently, anyway).
I have no doubt that when I reboot the schedule will restore itself, as I have previously experienced. Previous experience suggests it is not auto-schedule-restore doing this, as there is not a multi-boot, however I will disable ASR before I reboot just to confirm.
Is there any useful information I can report before rebooting?
Weirdly, the last entry in activity.log is 2019! Why might that be? auto.log stopped in May 2023, also weird.
Left to its own devices over the weekend (not in standby), the unit in question recorded on Saturday evening but nothing after that. This morning, it didn't do what it had been scheduled to do, and when I checked the schedule was empty (as I have come to expect). WebIF still works, and there is nothing reported in the crash log (not recently, anyway).
I have no doubt that when I reboot the schedule will restore itself, as I have previously experienced. Previous experience suggests it is not auto-schedule-restore doing this, as there is not a multi-boot, however I will disable ASR before I reboot just to confirm.
Is there any useful information I can report before rebooting?
Weirdly, the last entry in activity.log is 2019! Why might that be? auto.log stopped in May 2023, also weird.