Closed
Bug 961844
Opened 10 years ago
Closed 10 years ago
Please send t-w732-ix-115 to iX for 48 hours burn-in
Categories
(Infrastructure & Operations :: DCOps, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Unassigned)
References
Details
(Whiteboard: hardware diagnostics)
As discussed in https://bugzilla.mozilla.org/show_bug.cgi?id=959663#c2 Thanks!
Reporter | ||
Updated•10 years ago
|
Blocks: t-w732-ix-115
Updated•10 years ago
|
colo-trip: --- → scl3
Updated•10 years ago
|
Whiteboard: FEW-175-47434 (Waiting for response)
Comment 1•10 years ago
|
||
Dropped off at IX for brun-in.
Whiteboard: FEW-175-47434 (Waiting for response) → FEW-175-47434 (@ IX for brun-in)
Comment 2•10 years ago
|
||
HOst passed the burn-in, currently reimaging here's what ix said; Sal, It sounds like it was originally complaining about the disk and the node is actually continuing to pass our burn-in. Have you tried testing the disks yet, using the manufacturer's utility? Cheers!
Whiteboard: FEW-175-47434 (@ IX for brun-in) → reimaging
Reporter | ||
Comment 3•10 years ago
|
||
Has the disk utility been tried? Thanks for helping out with this!
Comment 4•10 years ago
|
||
We're trying other alternatives (Data Lifeguard Diagnostic for DOS)
Updated•10 years ago
|
Whiteboard: reimaging → hardware diagnostics
Comment 5•10 years ago
|
||
Passed the diags. host is up. sals-MacBook-Pro-3:~ sal$ sudo fping 10.26.41.165 10.26.41.165 is alive sals-MacBook-Pro-3:~ sal$ sudo fping 10.26.16.231 10.26.16.231 is alive
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → Infrastructure & Operations
You need to log in
before you can comment on or make changes to this bug.
Description
•