Closed Bug 1301206 Opened 9 years ago Closed 9 years ago

failed cache module on mozdefes8.private.scl3.mozilla.com

Categories

(Infrastructure & Operations :: DCOps, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: van, Assigned: van)

Details

(Whiteboard: 5311745087 , 5311713791)

Controller Status OK Serial Number PDNLH0BRH8R0A8 Model HP Smart Array P440ar Controller Firmware Version 2.14 Controller Type HP Smart Array Cache Module Status Failed <~~~~~~~FAILED! Cache Module Serial Number PDNLH0BRH8R0A8 Cache Module Memory 2097152 KB Encryption Status Not Enabled Encryption ASIC Status OK Encryption Critical Security Parameter NVRAM Status OK
Assignee: server-ops-dcops → vle
colo-trip: --- → scl3
QA Contact: cshields
:michal` the cache module is embedded on the controller so we'll need to swap out the controller. do you want to hold off on rebuilding this host until the controller swap just in case there is a serious issue with the current controller? they weren't able to tell me the reason why your RAID 1 got wiped when 1 drive failed and the cache module died.
Whiteboard: 5311713791
I'm holding on and waiting for the cache module to be replaced.
replaced cache module but im still seeing an error. looks like there might be a faulty battery or cabling since we've never touched either. error message: 856 The cache for SmartArray P440ar in Embedded Slot is disabled due to a cable error from the Smart Storage Battery. will contact HP for a solution.
new case is 5311745087. they were going to send another cache controller but ive asked them to send a replacement battery instead since we've just replaced the controller. will update once i receive the RMA. the host should be good to build now since we're only replacing the battery.
Whiteboard: 5311713791 → 5311745087 , 5311713791
battery came in and has been replaced. everything looks good via iLO and the controller BIOS/status. please let me know if any issues persist.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.