Clip: Disk can't keep up

M

MontanaJohn

n3wb
Oct 2, 2016
2
1
1714261532366.jpeg
Having trouble with this error all of sudden. All my disks are cached and not full. Any help would be great.
 
  • Like
Reactions: mat200
Ditto.

I’ve reverted back to version 5.8.9.6 as the log entries started showing up after I installed 5.8.9.7, and continued to do so for every update I’ve tried since.
 
  • Like
Reactions: mat200
Just received this reply from Ken (emphasis is mine)

"Please use 5.9.0.2 where this has been fixed and "relaxed" to not freak out so soon.​
It's a valuable sanity check and I am still refining it for 5.9.0.3"​
​
I informed him that 5.9.0.2 is what I was using when last observing the issue.

I'm going to update to 5.9.0.3 now and give it a try.
 
Last edited:
jaydeel said:
Just received this reply from Ken (emphasis is mine)

"Please use 5.9.0.2 where this has been fixed and "relaxed" to not freak out so soon.​
It's a valuable sanity check and I am still refining it for 5.9.0.3"​
​
I informed him that 5.9.0.2 is what I was using when last observing the issue.

I'm going to update 5.9.0.3 now and give it a try.
Click to expand...

I was also on 5.9.0.2 and having the problem. Glad to hear he is working on the problem...
 
  • Like
Reactions: Flintstone61
I went through this last week on 5.8.9.8 and Ken had me email him back an export of the troubled cam. Since 5.8.9.9 I have not had more of this issue. This appears to be a certain camera issue maybe?? I'm running 5.9.0.3 and have no issues.
 
  • Like
Reactions: Flintstone61
Tinman said:
I went through this last week on 5.8.9.8 and Ken had me email him back an export of the troubled cam. Since 5.8.9.9 I have not had more of this issue. This appears to be a certain camera issue maybe?? I'm running 5.9.0.3 and have no issues.
Click to expand...
Thanks for the data point.

The issue is happening with all of my Dahua cameras (4 models), and 1 of my 3 Amcrest cameras ( 1model).

Did Ken have you make any changes, or did he do something at his end using the export file your provided?
He's not yet asked for exports.

My affected camera models:
DH-IPC-HDW5442T-ZE
DH-IPC-HDW2231R-ZS
DH-SD12203T-GN
DH-IPC-HDW5231R-ZE
Amcrest IP2M-841W-V3 Pan/Tilt
 
jaydeel said:
Thanks for the data point.

The issue is happening with all of my Dahua cameras (4 models), and 1 of my 3 Amcrest cameras ( 1model).

Did Ken have you make any changes, or did he do something at his end using the export file your provided?
He's not yet asked for exports.

My affected camera models:
DH-IPC-HDW5442T-ZE
DH-IPC-HDW2231R-ZS
DH-SD12203T-GN
DH-IPC-HDW5231R-ZE
Amcrest IP2M-841W-V3 Pan/Tilt
Click to expand...
He just said it would be fixed in the next update, and it did indeed fix mine. I did nothing on my end. Mine was an older Dahua cam:

1714345849602.png
 
It looks like I may have other issues to debug. I just received this reply from Ken.

"Those force quits are bad news. That's usually a problem with hardware decoding or networking. ​
The 'can't keep up' messages are valuable... otherwise you would run out of memory. If you get those in .3 they are likely legitimate. "​

If anyone reading this has tips/suggestions on how to efficiently dig into this, I'd be grateful.
 
My setup:
Surveillance Computer System

Dell T3500 W3530 2.80Ghz CPU
24 Gig memory
150 GB C: drive
370 GB E: Drive
1Tb SSD M.2 Page File drive
FebSmart 4 Ports Superspeed 5Gbps USB 3.0 PCI Express

Syba 8 Bay SATA Non Raid External USB 3.0 Enclosure SY-ENC50119
(8) Seagate BarraCuda 1TB HDD ST1000DMZ10/DM010

19 cameras (8 full time recording)
The eight full time record cameras are the ones drawing the "Clip: Disk can't keep up." error
 
My question then is why does it not show up in 5.8.9.6??
I also have it happening on multiple cameras.
Most are hard wired in my Ubiquiti network and a few Amcrest wireless models.
All cameras record continuously in 4 hour blocks, after 24 hours move from New to Storage drive. After staying in Storage for 14 days the move to Aux for another 21 days then delete. They have been this way since 2016 when I first set it up.
 
More emails from Ken

4/29 4:45a
Can't keep up was added in 5..8.9.x.
It's a valuable sanity check to prevent crashes but there may be a problem closing the file in this case and I am now looking into that as a cause for the force quits.

4/28 10:11a
Yes [Can't keep up] was definitely new/buggy/too eager when first introduced.
I was able to recreate an issue where if the disk could not keep up, a force quit was possible. I am fixing this now.
 
  • Like
Reactions: bob2701
jaydeel said:
More emails from Ken

4/29 4:45a
Can't keep up was added in 5..8.9.x.
It's a valuable sanity check to prevent crashes but there may be a problem closing the file in this case and I am now looking into that as a cause for the force quits.

4/28 10:11a
Yes [Can't keep up] was definitely new/buggy/too eager when first introduced.
I was able to recreate an issue where if the disk could not keep up, a force quit was possible. I am fixing this now.
Click to expand...

Thanks for the update...
 
You must log in or register to reply here.
Top Bottom