"Alarm Event: No disk" on IPC-EBW81200

[fa355115]

Hi there,
I have recently installed an IPC-EBW81200 with a 64 Gb SD card into int I am usig for recording (on internal SD card) based on motion detection.

Quite often, I have a notification about "Alarm Event: No disk" then few seconds after a "Alarm Event: No diskStop", like if the SD card was removed or not detected anymore.

here is the lof the camera is providing ... do you have the same issue or not and do you know where thic can come from ??
Most of the time it then continues to record, but sometimes the card gots into "Failed" status and I need to format it through the interface then it goes again for some time ... very annoying ...

... see lines 346 and 347

332    System    2016-11-23 06:24:28    Event End    {"Channel NO.":1,"Event Type":"Motion Detect","Region Name":["Region1"]}
333    System    2016-11-23 06:24:19    Event Begin    {"Channel NO.":1,"Event Type":"Motion Detect","Region Name":["Region1"]}
334    System    2016-11-23 06:09:45    Event End    {"Channel NO.":1,"Event Type":"Motion Detect","Region Name":["Region1"]}
335    System    2016-11-23 06:09:31    Event Begin    {"Channel NO.":1,"Event Type":"Motion Detect","Region Name":["Region1"]}
336    System    2016-11-23 06:01:59    Hot swap    {"Action":"Insert Device","Device Name":"Disk1"}
337    System    2016-11-23 06:01:56    Save Configuration    {"Name":"Network Config"}
338    System    2016-11-23 06:01:49    Save Configuration    {"Name":"Encode"}
339    System    2016-11-23 06:01:49    Save Configuration    {"Name":"Encode"}
340    System    2016-11-23 06:01:48    Start up    {"Reboot Mark":"Abort"}
341    System    2016-11-23 06:01:48    Abort    {"Time":"2016-11-23 06:01:20"}
342    System    2016-11-23 05:57:30    Start up    {"Reboot Mark":"Abort"}
343    System    2016-11-23 05:57:30    Abort    {"Time":"2016-11-23 05:57:01"}
344    System    2016-11-23 05:53:58    Start up    {"Reboot Mark":"Abort"}
345    System    2016-11-23 05:53:58    Abort    {"Time":"2016-11-23 05:53:30"}
346    System    2016-11-23 05:45:20    Hot swap    {"Action":"Insert Device","Device Name":"Disk1"}
347    System    2016-11-23 05:45:15    Hot swap    {"Action":"Remove Device","Device Name":"Disk1"}
348    System    2016-11-23 05:33:48    Event End    {"Channel NO.":1,"Event Type":"Motion Detect","Region Name":["Region1"]}
349    System    2016-11-23 05:33:38    Event Begin    {"Channel NO.":1,"Event Type":"Motion Detect","Region Name":["Region1"]}
350    System    2016-11-23 05:08:09    Event End    {"Channel NO.":1,"Event Type":"Motion Detect","Region Name":["Region1"]}
351    System    2016-11-23 05:08:00    Event Begin    {"Channel NO.":1,"Event Type":"Motion Detect","Region Name":["Region1"]}

Many Thanks !

 

[nayr]

Put SD card in a computer and run H2testw on it

 

[fa355115]

Is it possible to "mount" the camera or map it like a mapped drive in Windows to access the SD card ?
Caera is wall mounted now with silicon and so on so will be a lot of work to dis-mount it to get the SD card out ...

 

[nayr]

no; you should be running that tool on all flash media before putting it into production.. tons of fakes out there and they behave quite the same as your experiencing.

 

[fa355115]

ok .... the SD card is brand new out of the box .... I was not expecting it to be broken ...
But Strange thing is that it desn't happen all the time, sometimes the card gets full and begins archive rotation for several days before the peoblem occurs ... sometimes happens after few hours ...

 

[nayr]

flash media quality also varies dramatically, even non fake cheap stuff seems to go faulty at absurd rates.. I wont run any SanDisk crap anymore after feeling the burn of failed flash more than I could count.. I typically buy expensive memory for IP Cameras, not that they need the high performance by any stretch.. but they use higher quality flash and its inherently more reliable as a result.

Surveillance cameras are more abusive than most other things w/flash memory.. Ive written to the cards in my vehicle's mp3 players mebe a dozen times in 4-5 years, on an ip camera its the opposite.. few reads, constant writes.. and flash does wear out on writes.

 

[fa355115]

so you are telling me sunning such a scan tool like H2testw is not necessary or .... ?
If I need to do that I need to dismount the camera to extract the card ...

 

[nayr]

if your SD card is disappearing (no disk); its pretty much guaranteed to be either: Counterfeit Flash, or quite simply Bad Flash Memory.. either way its going to require removing the current SD card and replacing it with another.

before putting ANY flash memory into production; you should test it thoroughly with tools like H2testw and other torture testing tools to see if it'll survive the long haul.. in the majority of the cases adequate testing prior to deployment will reveal any potential problems before you put em to use.

Every SD card I buy anymore spends a day or two in a burn-in test; if any errors happen at all I send it right back while the exchange/return window is still open.. Ive had alot of flash chips die on me prematurely over the years.. they used to offer industrial grade flash for a premium price, but now days industrial grade is basically the top of the line chips as they get the highest grade flash memory.. going cheap when buying SD cards rarely turns out to be a good purchase.

 

[fa355115]

it is really Strange we can ot "mount" de camera via a computer to access its SD "drive".
When I mount the camera via Windows 10 it is asking for a login and password, but the standard login and password is not working .... I am sure there should be a way to see its content and scan but I need to know its path ...

 

[nayr]

scanning it remotely over the network would not reveal anything; all those tools must be ran on local disks.. they have to write directly to the filesystem for the kinds of tests they are performing.

 

[fa355115]

yes ... but a "map network drive" would allow to write directly on the SD card no ??

 

[nayr]

no, it would be writing to a network cifs/nfs system, ontop of a networking subsystem, ontop of a filesystem, ontop of physical blocks on the disk.. these tools require block level access to perform the tests..

writing over a network is as close to directly writing as circumnavigating the globe to the west to eventually end up at your destination a mile or two to your east.. that can reasonably be performed via networking.

 

[fa355115]

ok ... I have just removed the SD card and will test it with H2testw and let you know the resuts.
I will put the micro SD in an adapter and insert it in my PC slot.

 

[fa355115]

... but I need to find the download button first ???

 

[fa355115]

ok ... running, it says 2 hours for my 64Gb card

 

[fa355115]

I am supposed to run the test sveral times on the SD card or once is sufficient if there is any mistake on the card ?
So far Nothing reporting, still running ...

 

[fa355115]

I have already ran the SD card test 2 times and no issues were reported.
I run it a third time now.

But according me, it looks like a wrong SD card management of the camera .... maybe too busy when you set event recording based on motion detection like I do, and the camera is loosing its card ...
Will let you know the 3rd run test results.

 

[fa355115]

ok ... ran the test 3 or 4 times on the SD card and no issues reported :

Test finished without errors.
You can now delete the test files *.h2w or verify them again.
Writing speed: 9.50 MByte/s
Reading speed: 18.8 MByte/s
H2testw v1.4

So according me this is the camera soft itself not supporting the load ...
shit

 

[nayr]

how long is it taking to fail in your camera? your going to need to test it for that log; try running this on burn in mode: Download Check Flash 1.16 (Free) for Windows

unless you put another flash chip of a different make model in and get the exact same error; you have not done enough to remove suspicion from the flash media.

 

[fa355115]

with motion detection set, I get 3 days of recordings before the caera overwrites the old data, and most of the time, the "No Disk" error appears after those 3 days when the card becomes full... sometimes 4 days.
Do you mean I need to run a 4 days continuous testing ??