Not enough HDD Speed BugIn Progress
Sinc ethe update to 5.0 nearly all of my Wisenet WAVE servers are throwing huge numbers of HDD Speed not enough errors. Hanwha support was, as usual, less than useless trying to tell me that a 14 camera system i should change my quality to LOW and set framerate to no more than 3fps. You might as well not have a video system at those frame rates. I can skip across a camera without ever being seen at 3fps. so im posting here since i got frustrated dealing with that line of stupidity.
The issue here is that actual system benchmarks dont support the log file's claim. That 14 camera system (1 of 30 or so having this problem) is powered by a Synology RS1221+ with each drive separately attached via network share (I also have systems with drives over sata or over a PCI HBA raid card backplane but well use the NAS for this example, ill get to why in a moment) each drive is a WD Purple PRO (the 256mb cache version) 8TB and if i try copy operations for a 1GB file from drive to drive using the wave server as the host for the copy operation im bench marking about 272mbps for all the transfers when grabbing and copying a handful of smaller files from one drive to the other the same way i was seeing about 180-230mbps. according to network card metrics, WAVE is only sending data to the NAS at a rate of about 40-50mbps leaving huge quantities of write speed overhead for these drives and yet, dozens of errors. By sitting and watching my netdata metrics what I've noticed is that wave consistently sends data over the network at a constant rate (About 45mbps on avg for this system) then suddenly tries to dump 270+mbps for a moment then returns to 40-50 and when that sudden spike occurs that's when the write to log is triggered (and why i used the NAS for an example because I can see the LAN card data rate metric readily.) however there seems to be no footage gaps of any kind even when this occurs. no observed missing frames no gaps in the recording bar at the bottom, nothing.
This seems to me like a bug of some kind. How can i resolve this, if its not a problem it shouldn't be logging as its causing my customers to panic about the hundreds of hard drive errors on their systems and if it is a problem it needs fixed. what can i do to further troubleshoot this.
Hi John Griffin,
I've converted this topic into a support ticket for further investigations.
Post is closed for comments.