Hello!
In /var/log/messages on two identical servers the failed logging messages logged:
Jun 12 23:00:59 uni057 sfcb[10227]: INTERNAL StorelibManager::getEnclosureConfig - StorelibManager::getEnclosureConfig:ProcessLibCommandCallfailed;rval=0x12
Jun 12 23:00:59 uni057 sfcb[10227]: INTERNAL StorelibManager::fireStorelibCommand - caller StorelibManager::getBBUStatus, ProcessLibCommandCall failed, rval = 0x22
Jun 12 23:00:59 uni057 sfcb[10227]: INTERNAL StorelibManager::fireStorelibCommand - caller StorelibManager::getBBUCapacityInfo, ProcessLibCommandCall failed, rval = 0x22
Jun 12 23:00:59 uni057 sfcb[10227]: INTERNAL StorelibManager::fireStorelibCommand - caller StorelibManager::getBBUDesignInfo, ProcessLibCommandCall failed, rval = 0x22
Jun 12 23:00:59 uni057 sfcb[10227]: INTERNAL StorelibManager::fireStorelibCommand - caller StorelibManager::getBBUProperties, ProcessLibCommandCall failed, rval = 0x22
Jun 27 23:27:59 uni067 sfcb[2095]: INTERNAL StorelibManager::getEnclosureConfig - StorelibManager::getEnclosureConfig:ProcessLibCommandCallfailed;rval=0x12
Jun 27 23:27:59 uni067 sfcb[2095]: INTERNAL StorelibManager::fireStorelibCommand - caller StorelibManager::getBBUStatus, ProcessLibCommandCall failed, rval = 0x22
Jun 27 23:27:59 uni067 sfcb[2095]: INTERNAL StorelibManager::fireStorelibCommand - caller StorelibManager::getBBUCapacityInfo, ProcessLibCommandCall failed, rval = 0x22
Jun 27 23:27:59 uni067 sfcb[2095]: INTERNAL StorelibManager::fireStorelibCommand - caller StorelibManager::getBBUDesignInfo, ProcessLibCommandCall failed, rval = 0x22
Jun 27 23:27:59 uni067 sfcb[2095]: INTERNAL StorelibManager::fireStorelibCommand - caller StorelibManager::getBBUProperties, ProcessLibCommandCall failed, rval = 0x22
Servers HW is:
PRIMERGY RX300 S4 (ABN:K1151-V101-7435)
Chassis Type RX300S4R1
BIOS Version 4.06 Rev. 1.06.2519
MainBoard D2519 (S26361-D2519-A11)
Controller LSI MegaRAID SAS 1078 - configured with RAID1 (2 x 500Gb ) and RAID10 ( 4 x 500Gb)
One of the servers was updated to Update 2.
The second yesturday was freshly installed with ESX 4.0 Update 2 (DVD
ISO)
Please, anyone know what is the sources, reason these errors and how to eliminate
them.
Thank You
" Jun 12 23:00:59 uni057 sfcb10227: INTERNAL StorelibManager::getEnclosureConfig - StorelibManager::getEnclosureConfig:ProcessLibCommandCallfailed;rval=0x12 "
Ans : The above piece of error message happens to be a bug in the LSI provider being shipped with ESX. Even though you cannot eliminate this from the logs, this message is harmless and you can safely ignore them.
-
Jun 12 23:00:59 uni057 sfcb10227: INTERNAL StorelibManager::fireStorelibCommand - caller StorelibManager::getBBUCapacityInfo, ProcessLibCommandCall failed, rval = 0x22
Jun 12 23:00:59 uni057 sfcb10227: INTERNAL StorelibManager::fireStorelibCommand - caller StorelibManager::getBBUDesignInfo, ProcessLibCommandCall failed, rval = 0x22
Jun 12 23:00:59 uni057 sfcb10227: INTERNAL StorelibManager::fireStorelibCommand - caller StorelibManager::getBBUProperties, ProcessLibCommandCall failed, rval = 0x22
Ans : Here the error code 0x22 indicates that your controller does not have a battery or its not working as normal. Please check the existence of the batteries/ whether its working as intended. These messages can also be ignored if the controller does not have a battery.
Award points if useful
Message was edited by: venkyVM
Yep,
You are completely right, there is no battery on controller. Now it is clear to me!
Thank You very much!
I would consider adding the battery. You can't safely enable disk caching without one. Disk caching greatly contributes to disk performance especially in a virtual environment.
Hi,
I'm getting a similar error:
LSIESG: LSIESG:INTERNAL :: StorelibManager::fireStorelibCommand - caller StorelibManager::getBBUCapacityInfo, ProcessLibCommandCall failed, rval = 0x37
sfcbd: INTERNAL StorelibManager::fireStorelibCommand - caller StorelibManager::getBBUCapacityInfo, ProcessLibCommandCall failed, rval = 0x37
Can you please tell me where to look up the error codes, or what 0x37 refers to?
Many thanks
Hi mblake4u,
Not sure about this code 0x37. A call from the provider to get the battery capacity is definitely getting failed. Please check the existence of the battery / its normal functioning.
Hi,
Thanks for your replying. Everything seems to be OK now.
Cheers,
Michael