Hello, 

 Yes you can.  You should have set the disk timeout values according to the OS considerations guide that's located with the EQL firmware downloads.  If you install the HIT/ME or HIT/LE software that will be set automatically. 

 The failover time depends on EQL F/W version, the model, 6210's are fast, and the load on the array at the time., 

 These settings should be set in the event of an unexpected failover, and firmware updates.  So it's a good thing to do regardless.  If they are not set, some OS's like Windows requires a restart to become effective. 

 Regards,

Don 

I have the same issue. I have replaced the battery on slot 0 and performed multiple maintenance resets, allowed over 72 hours and slot 0 still reports an end of life warning. Any suggestions appreciated. Thank you in advance.

Hello, 

 I would go back to your vendor and get another battery.  Once you replace the battery with a good one there's no other action required.  The battery assy keeps track of manufacture data, number of cycles, etc..  it's similar to a SMART failure on a drive.  Replacement is the only option. 

 Regards,

Don 

Hello,

While I do not know what resolution the original poster reached, I would expect you would need a different battery. Like Don mentioned above, once the battery is replaced, there really isn't anything more for you to do. Page 26 of the document below goes into detail on battery replacement.

https://downloads.dell.com/manuals/common/ps6210_om_en.pdf 

Thanks very much for the prompt response!

I followed this guide, except the fact that I turned off the storage entirely before taking the controllers off and replacing the batteries. I found so many information about the charging time of the controller batteries. Do you know how many time we need to wait for it? It is possible that this erros is related with a uncharged battery?

Thanks again!

Hello, I'm facing the same problem. Even after the replacement, the two slots keeps the same error.

Do you found any other solution? Or you needed to ask for another battery?

Thanks!

EDIT: My cache policy is set to write-through, which is impairing the storage performance.

You could give it 24 hours from the of replacement, because the batteries do go through charging and learn cycles. I'm not confident this will resolve your issue by itself, but there's certainly no harm in observing to see if the battery does come up properly. However, if it doesn't come up after that, I'd be considering a different battery.

Thank you both for the patience and quick response.

So I'll wait the 24 hours replacement period and if it do not come back up, we will try to aquire a new battery or a new controller.

Hello, 

 That would not be a very good idea.  A power loss or possibly even a controller failover could result in lost data. Including array side operations to the internal databases. Which could leave that member inaccessible. 

GrpName>member select MEMBERNAME low-battery-safe ?
enable - Enables low-battery-safe mode. Cache operates in write-b
ack mode.
disable - Disables low-battery-safe mode. Cache operates in write-
back mode, regardless of battery charge. Not recommended
due to risk of data loss.

 The time to flush cache is dependent on many factors.  RAID type and IO load foremost among them.  

 Strongly advise you do NOT disable this feature. 

  Regards, 

Don 

Like Don had said, I really don't think it would be a great idea to disable this. I'd really only be repeating what his post, but turning this off would be a disservice to yourself.