Anyone Else Seeing Memory Card Issues With Dahua IPC-HFW2831T-ZS's ?

I had all sorts of issues with microSD cards in the 59225 and 1A225 which settled down with the latest firmware - maybe Dahua need to port the fixed code across more cameras?
@reverend - Did you load the 1A225U firmware from Dahua's International site, that is dated 181205? And if so, the PTZ firmware is dated 170829, is that also what you installed. I am having the issues with SD cards that you and others have reported and would like to get it resolved. Thanks!
 
I report this to dahua for the SD card issues, they are testing on it, hope can fix up this release the new firmware soon.
 
  • Like
Reactions: reverend
@reverend - Did you load the 1A225U firmware from Dahua's International site, that is dated 181205? And if so, the PTZ firmware is dated 170829, is that also what you installed. I am having the issues with SD cards that you and others have reported and would like to get it resolved. Thanks!
I already had the right PTZ firmware on there so just loaded the newer camera firmware from Dahua - details as follows:

Device TypePTZ1A225U-IRA-N
System VersionV2.623.0000000.13.R.E4.2512.9A.NR, Build Date: 2018-12-05
PTZ VersionV2.300.0000000.8.RHNAB_170829_23879

Since the upgrade the http interface hasn't crashed on it at all. My 59225 is playing up but that's looking to be a cable fault somewhere but the new firmware is definitely an improvement with the microSD cards I was using (Samsung Evo+ and a Toshiba Exceria both 128GB).

Hopefully the new firmware will fix the 2831 too (assuming it's the same fault).
 
  • Like
Reactions: weigle2
Can confirm that for me the issue still exists on both cams. Some of the testing completed so far:
  1. Cams connected via different pre-made cables, I also re-made the hand made cables I had in place (Monoprice).
  2. No packet loss or other anomalies seen across the network or directly to these cams.
  3. SD cards used in the 2 cams mentioned here (2831’s) used in other Dahua cams I have without any issue.
  4. Also tried with Samsung Evo Plus & Endurance SD cards, no difference.
  5. Ruled out POE switch (have a number of different brands I can test against all known good, issue with SD card still exists)
  6. Have now tried FW from 2018-07-31, 2018-11-02 & 2019-01-09 all exhibit the issue. A few notes are that the 7-31 seems to last the longest and 11-02 and 01-09 FW seem to exhibit the issue quicker.
  7. For continued reference, issue still persists with specific log entries made by the ‘system’ showing Hot Swap - Remove Device & swiftly followed (within 3 to 5 seconds) by Hot Swap - Insert Device. The problem is that although there is the 3 sec (small) window and shows insert, the cam never see’s the card again unless you reboot then you start the cycle again.
  8. Time taken to see the issue has ranged from around 25 minutes to a couple of hours (no longer than 4 and that was the max).
  9. I’ve looked at the SD card connect on both cams and looks solid
  10. Factory reset both cams after each FW update
  11. Formatted SD cards both in cam and out of cam (PC)

As stated by @fenderman, it would be very unlikely that 2 cams have the exact same HW issues (if HW related) unless something has changed in the physical HW build in these more recently purchased units. Therefore at this point it would appear similar to the other Dahua cam ‘SD cards going missing’ issues that have been discussed on the board before and tied to certain configurations causing problems in firmware. I know Andy @EMPIRETECANDY is aware of the issues seen in the past with the 5231 and is kindly working with Dahua on getting this looked at in FW with the logs I am providing as well. Hopefully can be a cross port of the solution that was found for the 5231 in code (if determined the same issue) and therefore a quicker fix but we’ll see.

Certainly a strange one this. Thanks Andy @EMPIRETECANDY for agreeing to push this with Dahua for us in hopes to get updated FW or another solution once the issue is run to ground at Dahua.

Will keep testing and reporting back if I see any difference.
 
I have not had any luck with Sandisk Ultras or Samsung EVO. I have went to Samsung Pro Endurance SD cards now. Had the same missing SD card issues and I see a Camera Offline randomly with Ultra and EVO. I still have 2 with Sandisk Ultras which are now malfunction and I get no SD card present. I plan to put Pro Endurance SD in them and will report back


M
 
Further update and spoiler alert........still seeing the same issues. I continue to roll through the firmware testing different scenarios across all and still see the same issues. I ordered 6 brand new cards as well (2 Evo Select, 2 Evo Plus, 2 Evo Endurance) and all suffer the same issues. Now again for continued reference, all of the old and new cards work in my other Dahua cams (non 2831's) without any issue at all.

The Hot Swap - Remove Device & Hot Swap - Insert Device is the constant in this issue and occurs every time this happens. You can see it in the logs but the cam never recovers / never re-see's the card until reboot. In some cases the cam (depending on the FW being run at the time) may also report a 'Disk Error' but again this doesn't seem to be SD card related (as in HW SD card) as not only have I tested so many at this point but also they work without these issues in the other cams.

Therefore my conclusion (based solely on my testing) at this time is that this is either a) sporadic FW related issues as seen with the 5231 SD card problems OR b) HW related issues on the cam for a certain set of build dates / batch. @EMPIRETECANDY is kindly working with Dahua on the FW side to see if we can get expert eyes on that. I've captured all logs relating to this and will continue to test and report back.

The longest I've been able to get this to work is about 1.5 days max now. I'm going to experiment with bitrate settings as well in efforts to see if its write related and maybe it will kick out the issue quicker with higher bitrates (I know this seems like a stretch but at beginning I was running 15k bitrate and the cam would lose the card after about 25 mins). All of the recent testing has been at the default of 8192.

Thanks all, @EMPIRETECANDY hopefully we get gain further insight and a fix / port for this issue relatively quickly from Dahua. Appreciate your help and others feedback here as well.
 
@fenderman thanks for the update. Couple of quick questions if I may:

1) Are you using the same SD cards as mentioned above ?
2) Anything show in your logs RE: Hot Swap or Disk Error at all ?
3) Are you running a customized bitrate (I know this one's a stretch but trying to isolate what makes the camera lose these quicker and this was an area I wanted to dive deeper on based on something I noticed while testing).
4) When you saw the issue before (prior to the 2019 FW) did it manifest itself the same way (logs showing Hot Swap and card disappearing) ?

If everything else is equal and the issue is still present then maybe it is down to a particular batch and is hardware related or depending on settings etc is some anomaly in FW. As mentioned above I personally found the 2019 FW had the issue quicker than the older FW which is quite the opposite of your experience as you mentioned.

Hoping that together with @EMPIRETECANDY and Dahua we can get some quick resolution to this because I'm running out of ideas to try and variables to test :)

Thanks again

Mine has been running fine for 11 days after the update.
 
@fenderman thanks for the update. Couple of quick questions if I may:

1) Are you using the same SD cards as mentioned above ?
2) Anything show in your logs RE: Hot Swap or Disk Error at all ?
3) Are you running a customized bitrate (I know this one's a stretch but trying to isolate what makes the camera lose these quicker and this was an area I wanted to dive deeper on based on something I noticed while testing).
4) When you saw the issue before (prior to the 2019 FW) did it manifest itself the same way (logs showing Hot Swap and card disappearing) ?

If everything else is equal and the issue is still present then maybe it is down to a particular batch and is hardware related or depending on settings etc is some anomaly in FW. As mentioned above I personally found the 2019 FW had the issue quicker than the older FW which is quite the opposite of your experience as you mentioned.

Hoping that together with @EMPIRETECANDY and Dahua we can get some quick resolution to this because I'm running out of ideas to try and variables to test :)

Thanks again
1- I am using one of these two dont know which they were purchased around the same time.
https://www.amazon.com/gp/product/B07B9KTLJZ/ref=oh_aui_search_asin_title?ie=UTF8&psc=1
https://www.amazon.com/gp/product/B00V5Q1N1I/ref=oh_aui_search_asin_title?ie=UTF8&psc=1
2- no
3- no custom bitrate
4- I dont recall the exact error I saw if any, I know that the card was not visible on the storage settings and no recordings were visible. After the reboot, I saw the card and it had 3 days of video from months ago so I know it was inactive all that time.

I would test with the camera reset to defaults.
 
As an Amazon Associate IPCamTalk earns from qualifying purchases.
I've just added some info over in the 59225 thread as I swapped the card I was running which it had been happy with recently (a Toshiba Exceria M302 128GB) with a Transcend v30 128GB card and after the new card filled the camera started spitting out disk errors. On checking the 1A225 it has also dropped the Samsung Evo Plus 128GB card.

Here are the errors from the 59225 with the Transcend card:
Screenshot 2019-04-09 at 17.35.26.png


Ironically the Integral card is supposed to be quicker than the Toshiba card so it's interesting it started to :puke: when the card filled up which suggests it is slower at deleting and creating new files when full which is what I'm guessing caused the 59225 to :puke: only whne the microSD filled up.

All bets are off now for that latest 59225 and 1a225 firmware - they're stable but seems the microSD side has more work.

The 5231 has been happy with the Toshiba card on the 2.622.0000000.31.R, Build Date: 2018-08-13 firmware for months now and I think I'm over the 2 year mark now for that card in there - I honestly expected that to have died by now.
 
Last edited:
@fenderman thanks for the info. Yes I have been factory defaulting every time I switch FW and then also re-format the card after the reset to ensure its been formatted by the new FW version after the upgrade/downgrade. I was surprised though that with Factory Reset that it does not reset zoom or focus, every other setting gets reverted but not that, just assumed it would reset everything including back to full wide.

I'm going to do another test running each level of FW on each cam, factory reset again, SD formatted fresh in cam again and leaving one at 8192 and the other at 15000 & 10240) then going to see how long it takes the cams on each FW to lose the card at each setting just in efforts to run to ground any specific setting / scenario that may be causing this as well.

Really is a frustrating issue for sure

1- I am using one of these two dont know which they were purchased around the same time.
https://www.amazon.com/gp/product/B07B9KTLJZ/ref=oh_aui_search_asin_title?ie=UTF8&psc=1
https://www.amazon.com/gp/product/B00V5Q1N1I/ref=oh_aui_search_asin_title?ie=UTF8&psc=1
2- no
3- no custom bitrate
4- I dont recall the exact error I saw if any, I know that the card was not visible on the storage settings and no recordings were visible. After the reboot, I saw the card and it had 3 days of video from months ago so I know it was inactive all that time.

I would test with the camera reset to defaults.
 
As an Amazon Associate IPCamTalk earns from qualifying purchases.
Further update on this issue with more detail

Cam # 1

  • Last reset was on 4/7/19
  • Had the ‘Hot Swap - Remove Device’ event @ 21:29:39 on 4/7 and showed the ‘Hot Swap - Insert Device’ BUT didn’t lose the card
  • Running FW 2018-07-31
  • Bitrate @ 8192
  • 4/10/19 - Cam lost card today - Uptime therefore (before losing card) was approx 2 hours before initial Hot Swap (that it DID recover from above) and about 2.5 days before it saw the same issue again and did not recover

Cam # 2
  • Reset on 4/8/19 and lasted only (in comparison to Cam 1) 9hrs 41 minutes before losing card
  • Recorded an event at @ 21:26:08 on 4/8/19 then lost the card shortly after with ‘Hot Swap - Remove Device’ @ 21:26:22 followed by ‘Hot Swap - Insert Device’ @ 21:26:23, card was never re-seen by cam
  • Running FW 2018-07-31
  • Bitrate @ 15k
  • Reset again this morning (4/10/19) with bitrate @ 8192 and lasted only 2 hours before it lost the card again
Quick question, is there a log maximum entry that anyone here is aware of as it seems that even though the camera never loses connection to POE/Network there are entries missing (at least based on time the cam has been up etc) that I haven’t noticed before. Wondering if a maximum entry count before purging the log is in effect ?

As you can see from above there is clearly a difference being seen between timing of 1 cam losing card to another even when settings are set equally. I’m wondering if there is some issue in time between recordings (motion detected) and read/write operations on camera that is kicking these issues off. Specifically that if there are a large number of detections (therefore writes) for a camera in a short time that the camera / card cannot keep up and throttles itself rather than buffering to the 512MB on board etc. The SD cards that I’m using are the same as others here, and with the amount of them I’ve gone through in the past few weeks (of different Samsung flavors), plus testing in other Dahua cams, I think I can rule those out for now both in terms of their performance and the health of the SD cards.

@EMPIRETECANDY, not sure what Dahua found to be the issue with the 5231’s and why they were losing SD cards, would be useful if you could find out what they fixed there and again if possible to port that solution into firmware for the 2831 ASAP ? Similarly if there is a brand of SD card that Dahua uses in its testing that we (this forum) are not aware of/using, I am happy to test with those as well in hopes to narrow this issue down and get it fixed.

I’m going to repeat the tests again now on the 2018-11-02 firmware (then 2019-01-09), reformatting the cards and factory defaulting the cams again as I continue the testing.

Will continue to update
 
My 2831T-ZS (2019-01-09) log looks like this. Sometimes the card is missing. The card is Samsung 128 EVO Plus.
 

Attachments

  • 2831hotswap.JPG
    2831hotswap.JPG
    92.7 KB · Views: 19
@fenderman was just about to post my latest update when I saw yours. Mine too lost the card today longest run yet on the Endurance Pro, just under 3 weeks. I already upgraded my other 2831. It upgraded this one today so am testing on both as well. Just wish the bitrate option on these latest FW’s went up to 15k again. @EMPIRETECANDY did say via a DM that he kindly would bring that up with Dahua. Thanks Andy
 
@fenderman was just about to post my latest update when I saw yours. Mine too lost the card today longest run yet on the Endurance Pro, just under 3 weeks. I already upgraded my other 2831. It upgraded this one today so am testing on both as well. Just wish the bitrate option on these latest FW’s went up to 15k again. @EMPIRETECANDY did say via a DM that he kindly would bring that up with Dahua. Thanks Andy
Yes, i already talked with them, the next update maybe done.;) thanks!
 
@fenderman was just about to post my latest update when I saw yours. Mine too lost the card today longest run yet on the Endurance Pro, just under 3 weeks. I already upgraded my other 2831. It upgraded this one today so am testing on both as well. Just wish the bitrate option on these latest FW’s went up to 15k again. @EMPIRETECANDY did say via a DM that he kindly would bring that up with Dahua. Thanks Andy
15k bitrate is a waste of storage space. Its not discernable from much lower rates
 
@fenderman I have three 2831T-ZS cameras I upgraded them all to 29.4 for the latest update.
Sd card has been visible on all cameras at all times when I've gone to check.
One had a hot swap every day but only because I had auto Maintain at 1.00 hot swap appeared in the log at 1.01 every day.
 
  • Like
Reactions: fenderman