Closed Bug 1112259 Opened 11 years ago Closed 11 years ago

HP Log on metrics-logger1.private.scl3.mozilla.com is CRITICAL: CRITICAL 0004: POST Error: 1786-Drive Array Recovery Needed

Categories

(Infrastructure & Operations :: MOC: Problems, task)

Other
Other
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nagiosapi, Unassigned)

References

()

Details

(Whiteboard: [id=nagios1.private.scl3.mozilla.com:492152])

Automated alert report from nagios1.private.scl3.mozilla.com: Hostname: metrics-logger1.private.scl3.mozilla.com Service: HP Log State: CRITICAL Output: CRITICAL 0004: POST Error: 1786-Drive Array Recovery Needed Runbook: http://m.allizom.org/HP+Log
Automated alert acknowledgement: (ashlee)is being rebuilt currently at 12%
Status: NEW → ASSIGNED
Automated alert acknowledgement: (ashlee)is being rebuilt currently at 16
Automated alert acknowledgement: (ashlee)logicaldrive 1 (8.2 TB, RAID 5, Recovering, 77% complete) array A (SAS, Unused Space: 0 MB)
Drive rebuild completed. Smart Array P410i in Slot 3 (sn: 500143801646C8F8) logicaldrive 1 (8.2 TB, RAID 5, OK) array A (SAS, Unused Space: 0 MB) physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS, 900.1 GB, OK) physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SAS, 900.1 GB, OK) physicaldrive 1I:1:3 (port 1I:box 1:bay 3, SAS, 900.1 GB, OK) physicaldrive 1I:1:4 (port 1I:box 1:bay 4, SAS, 900.1 GB, OK) physicaldrive 1I:1:5 (port 1I:box 1:bay 5, SAS, 900.1 GB, OK) physicaldrive 1I:1:6 (port 1I:box 1:bay 6, SAS, 900.1 GB, OK) physicaldrive 1I:1:7 (port 1I:box 1:bay 7, SAS, 900.1 GB, OK) physicaldrive 1I:1:8 (port 1I:box 1:bay 8, SAS, 900.1 GB, OK) physicaldrive 1I:1:9 (port 1I:box 1:bay 9, SAS, 900.1 GB, OK) physicaldrive 1I:1:10 (port 1I:box 1:bay 10, SAS, 900.1 GB, OK) physicaldrive 1I:1:11 (port 1I:box 1:bay 11, SAS, 900.1 GB, OK) physicaldrive 1I:1:12 (port 1I:box 1:bay 12, SAS, 900.1 GB, OK, spare)
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Component: MOC: Incidents → MOC: Problems
You need to log in before you can comment on or make changes to this bug.