Closed
Bug 1098707
Opened 10 years ago
Closed 10 years ago
please run hardware diagnostics on t-w732-ix-161 and reimage
Categories
(Infrastructure & Operations :: DCOps, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: philor, Unassigned)
References
Details
It was burning jobs with I/O errors, got diagnostics that didn't find anything in bug 1091661, and continues burning jobs with the exact same I/O errors.
Updated•10 years ago
|
colo-trip: --- → scl3
Comment 2•10 years ago
|
||
do you have the log of IO errors? it'll help if we open a case with iX for either a drive or controller replacement.
Reporter | ||
Comment 3•10 years ago
|
||
There are links to and copy-pastes from the test logs in bug 1091658, but iX isn't likely to think of 08:34:01 FATAL - Unable to remove C:\slave\test\build! 08:34:01 FATAL - Caught exception: (1117, 'FindNextFile', 'The request could not be performed because of an I/O device error.') as very helpful logs. For OS-level logs, I think I'd have to ask Van ;)
Comment 4•10 years ago
|
||
passed memtest, running hard disk diagnostics. If host passes both diags and keeps burning jobs after the reimage we can open a case with iX
Whiteboard: running diagnostics → Running hard disk diagnostics
Comment 5•10 years ago
|
||
host passed diagnostics, reimaging
Whiteboard: Running hard disk diagnostics → reimaging
Comment 6•10 years ago
|
||
host is up, let us know if it keeps burning jobs. sals-MacBook-Pro-3:~ sal$ sudo fping 10.26.19.160 10.26.19.160 is alive sals-MacBook-Pro-3:~ sal$ sudo fping 10.26.40.135 10.26.40.135 is alive sals-MacBook-Pro-3:~ sal$ ssh !$ ssh 10.26.40.135 The authenticity of host '10.26.40.135 (10.26.40.135)' can't be established. RSA key fingerprint is e1:6a:3c:92:52:3b:97:bc:bf:01:87:e1:f0:58:e6:6a. Are you sure you want to continue connecting (yes/no)?
Whiteboard: reimaging
Updated•10 years ago
|
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
•