Since updating to 6.20 I keep finding messages that my disk is too slow

I can't find any evidence of problems with the disk. It's a 2 TB SSD connected via external USB3 that runs between 1/2 and 3/4 full.

The messages suggest that recording has stopped but as near as I can tell it picked right up again.


Is this a new problem I need to be worried about, or just something different in 6.2? I really don't need to know if recording paused momentarily for a few seconds while I was asleep (although there's actually no useful indication of when it happened.)

Comments

  • This is not a known/new problem - in fact 6.20 should be significantly more efficient in terms of disk access than 6.19, so this problem should be less likely, not more. This could indicate a problem with your recording disk, but it's not possible to confidently diagnose without further information.

    After this happens, SecuritySpy will back off for a short time and then try recording again, so this recovery mechanism sounds like it's working, but still this is a problem that needs to be fixed in order to avoid interruptions in recordings.

    My advice would be:

    • Revert to the previous 6.19 version to check whether this is in fact a new problem in 6.20. You can do this at Settings > License > Choose Version > 6.19 > Install. If you see the same problem with 6.19, this points to the disk as the culprit.
    • After running the above test, email us and include a debug file (SecuritySpy menu > Debug > Create Debug File On Desktop), and we will investigate. Further troubleshooting of this issue should be done via direct correspondence rather than via this forum.
  • Thanks, Ben. Back to 6.19.

  • No messages in SS 6.19.

  • Ran 6.21 update. Got message. Going back to 6.19 again.


  • To get to the bottom of this we will need to investigate and this is best done directly with you by email rather than this forum. Please email us and include two debug files (SecuritySpy menu > Debug > Create Debug File On Desktop); one created by 6.19 and the other created by 6.21 when this problem is showing. Include "escalate to human" at the top of your email so that it bypasses our helpdesk bot and goes straight to our human team.