Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[smonsees]

We received these message from our 3200 this morning:

module BM function battery_charger_daemon:  Battery transition from charged to charging (this was repeated  once a minute for 10 minutes)

then we had this:

module BM: The battery charger daemon failed

followed by:

Battery State Change: Previous State: Charged, New State: Failed
Source: RCP
General Purpose Flags: 0x00000b44


What do I need to do to resolve this? 
Thanks,
Scott

[Lycan]

What firmware are you using?
\

[KenS]

We also had this happen to us last week.  We were running 2.6.3.1, but I updated the firmware to 2.7.3.1 on Friday, and after a power cycle, the problem cleared itself.  Then the daemon failed again early this morning (Monday).

Any help would be appreciated.

Thanks,
Ken

[smonsees]

We are running version 2.6.3.1

[Lycan]

there is a newer firmware. it should address that issue.

[JoelSnyder]

The 2.7.3.1 firmware doesn't resolve this issue. 
I just got these alerts tonight.

Now what do we do?  Is the battery user-replaceable? What's the part number?
If we have to reboot this thing, we don't want it to be down for long...

This is affecting performance, because it has enforced Write-Thru cacheing:

2.185649 seconds for the Controller in Slot #0. ;"
"2010/02/25 03:51:28","43212","Error","System","Startup","General message","Chassis 001-001","0000000063600176","0","0","module BM  function battery_charger_daemon: Battery transition from charged to charging","Text1 = module BM  function battery_charger_daemon: Battery transition from charged to charging ;"
"2010/02/25 03:51:29","43213","EngInfo","System","Startup","General message","Chassis 001-001","0000000063600176","0","0","battery_charger_daemon: check the battery again","Text1 = battery_charger_daemon: check the battery again ;"
"2010/02/25 03:51:29","43214","Error","System","Startup","General message","Chassis 001-001","0000000063600176","0","0","module BM  function battery_charger_daemon: Battery transition from charged to charging","Text1 = module BM  function battery_charger_daemon: Battery transition from charged to charging ;"
"2010/02/25 03:51:30","43215","EngInfo","System","Startup","General message","Chassis 001-001","0000000063600176","0","0","battery_charger_daemon: check the battery again","Text1 = battery_charger_daemon: check the battery again ;"
"2010/02/25 03:51:30","43216","Error","System","Startup","General message","Chassis 001-001","0000000063600176","0","0","module BM  function battery_charger_daemon: Battery transition from charged to charging","Text1 = module BM  function battery_charger_daemon: Battery transition from charged to charging ;"
"2010/02/25 03:51:31","43217","EngInfo","System","Startup","General message","Chassis 001-001","0000000063600176","0","0","battery_charger_daemon: check the battery again","Text1 = battery_charger_daemon: check the battery again ;"
"2010/02/25 03:51:31","43218","Error","System","Startup","General message","Chassis 001-001","0000000063600176","0","0","module BM  function battery_charger_daemon: Battery transition from charged to charging","Text1 = module BM  function battery_charger_daemon: Battery transition from charged to charging ;"
"2010/02/25 03:51:32","43219","EngInfo","System","Startup","General message","Chassis 001-001","0000000063600176","0","0","battery_charger_daemon: check the battery again","Text1 = battery_charger_daemon: check the battery again ;"
"2010/02/25 05:04:51","43220","Error","System","Startup","General message","Chassis 001-001","0000000063600176","0","0","module BM: The timeout happened when trying to fully charge the battery","Text1 = module BM: The timeout happened when trying to fully charge the battery ;"
"2010/02/25 05:04:51","43221","EngInfo","System","Startup","General message","Chassis 001-001","0000000063600176","0","0","     Notify the CMAP/RCP of the Battery state change ( battery is failed )","Text1 = Notify the CMAP/RCP of the Battery state change ( battery is failed ) ;"
"2010/02/25 05:04:51","43222","Error","System","Startup","General message","Chassis 001-001","0000000063600176","0","0","module BM: The battery charger daemon failed","Text1 = module BM: The battery charger daemon failed ;"
"2010/02/25 05:04:51","43223","Info","System","RCP","Received Async Message","Chassis 001-001","0000000063600176","0","0","Battery State Change: Previous State: Charged, New State: Failed","Event = Battery State Change ;RCP_State = Standalone ;General_Purpose_Flags = 0x00001684 ;"
"2010/02/25 05:04:51","43224","Info","System","RCP","Sequence","Chassis 001-001","0000000063600176","0","0","Starting Enable Host IO","Event = Received Response to THIS Message ;RCP_State = Standalone ;General_Purpose_Flags = 0x00008684 ;Time_Msg_Sent = 1267074291 ;Time_Rsp_Rcvd = 1267074291 ;"
"2010/02/25 05:04:51","43225","Info","System","RCP","Sequence","Chassis 001-001","0000000063600176","0","0","Force Write Through","Event = Received Response to THIS Message ;RCP_State = Standalone ;General_Purpose_Flags = 0x00008e84 ;Time_Msg_Sent = 1267074291 ;Time_Rsp_Rcvd = 1267074291 ;"
"2010/02/25 05:04:52","43226","Info","System","RCP","Sequence","Chassis 001-001","0000000063600176","0","0","Operation Completed","Event = Received Response to THIS Message ;RCP_State = Standalone ;General_Purpose_Flags = 0x00008e84 ;Time_Msg_Sent = 1267074291 ;Time_Rsp_Rcvd = 1267074292 ;"

[Fatman]

It is user replaceable.  Call in and we will get your old battery RMA'ed if it has failed.

[JoelSnyder]

It is user replaceable.  Call in and we will get your old battery RMA'ed if it has failed.

Oh, you funny guy!  Have you ever tried calling D-Link technical support with this kind of question?  I have spoken over the past 90 minutes to a wide variety of young ladies in all parts of the globe, but no one is willing to allow me to purchase a new battery, although they all want to know my first and last name.  I am trying to send email to spareparts@dlink.com (one of the recommended options) as a last resort.  Maybe I can pop the cover and just see; it could be a stock battery I can get anywhere...

Thanks!

Joel Snyder

[Fatman]

I am sorry you had such difficulties, which line did you call in under?

[KenS]

I have assumed that this is just a problem with the new firmware as it started after we applied the latest one.  Having had to go through the painful process of calling tech support for this product before, I was not so interested in going through it again.  At one point I was able to reach someone knowledgeable about the xStack, but the sheer number of calls I had to make to get different people before I found one who could route me to the correct group made me decide that calling for this was not really worth it.  Especially if it might get corrected with a firmware update in the not so distant future.

At one point, one of the people  I spoke with last August wanted us to spend an additional $1100.00 US to buy some sort of Enterprise Support Package before they would assist us.  I just kept calling back to get someone else on the phone, and eventually, I got routed to the storage folks and they were able to help us get the problem kind of fixed.  In fact, they were quite nice to work with once I was able to reach them.

[JoelSnyder]

The error went away on ours for a while (before I could figure out how to get D-Link to sell me a battery), so I gave up on them and went to the original manufacturer, iStor.  They have the batteries for about $35, answer their phone, and seem to be perfectly happy to sell parts.   Try support@istor.com.  The iStor part number for the DSN3200 is the "iS325."

[KenS]

The latest firmware (2.7.7.1) seems to have corrected our problem.  We are now and have been for some time in "Write Back" mode.

Ken