failed drive tp-b02-master01.phx

RESOLVED FIXED

Status

RESOLVED FIXED
8 years ago
4 years ago

People

(Reporter: phong, Assigned: phong)

Tracking

Details

(Whiteboard: HP: 4622492099)

(Assignee)

Description

8 years ago
[17:11]  <nagios-phx> [197] tp-b02-master01.phx:hplog is CRITICAL: CRITICAL 0001: Internal SAS Enclosure Device Failure (Bay 2, Box 1, Port 1I, Slot 0)
(Assignee)

Comment 1

8 years ago
            physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS, 300 GB, OK)
         Mirror Group 1:
            physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SAS, 300 GB, Failed)
(Assignee)

Comment 2

8 years ago
SPARE: 507127-B21  
SAS Hot Plug SFF (2.5-inch) Enterprise (ENT) Drives         
HP 300GB 6G SAS 10K SFF (2.5-inch) Dual Port

=&amp;gt; controller slot=0 show config

Smart Array P410i in Slot 0 (Embedded)    (sn: 5001438006AAA440)

   array A (SAS, Unused Space: 0 MB)


      logicaldrive 1 (279.4 GB, RAID 1, Interim Recovery Mode)

      physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS, 300 GB, OK)
      physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SAS, 300 GB, Failed)


=&amp;gt; controller slot=0 physicaldrive 1I:1:2 show

Smart Array P410i in Slot 0 (Embedded)

   array A (Failed)

      physicaldrive 1I:1:2
         Port: 1I
         Box: 1
         Bay: 2
         Status: Failed
         Drive Type: Data Drive
         Interface Type: SAS
         Size: 300 GB
         Rotational Speed: 10000
         Firmware Revision: HPD3
         Serial Number: WXC0CA9P1986        
         Model: HP      DG0300BAQPQ     
         PHY Count: 2
         PHY Transfer Rate: 3.0GBPS, Unknown
Whiteboard: HP: 4622492099
(Assignee)

Updated

8 years ago
Flags: colo-trip+
(Assignee)

Updated

8 years ago
Assignee: server-ops → phong
(Assignee)

Comment 3

8 years ago
[10:51]  <nagios-phx> tp-b02-master01.phx:hplog is OK: OK 0001: Internal SAS Enclosure Device Failure (Bay 2, Box 1, Port 1I, Slot 0)
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.