Closed
Bug 1153369
(foopy67)
Opened 10 years ago
Closed 10 years ago
Please run diagnostics on foopy67
Categories
(Infrastructure & Operations :: DCOps, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Callek, Unassigned)
References
Details
(Whiteboard: #VDJ-123-42740)
Its hitting what seems like a dying disk...
corresponds to:
panda-0434
panda-0435
panda-0436
panda-0437
panda-0438
panda-0439
panda-0440
panda-0441
panda-0442
panda-0443
panda-0445
Can take it out of service at will
Comment 1•10 years ago
|
||
Not that it's fool proof, but the nagios SMART test doesn't show the drive failing. Callek: what makes you think it's the foopy? Did you look in the log for read/write errors?
Reporter | ||
Comment 2•10 years ago
|
||
Io errors with temp in my email from cron
Updated•10 years ago
|
colo-trip: --- → scl3
Reporter | ||
Updated•10 years ago
|
Blocks: panda-0445
Comment 4•10 years ago
|
||
Drive replaced, host reimaged.
vhua$ ssh foopy67.p5.releng.scl3.mozilla.com
The authenticity of host 'foopy67.p5.releng.scl3.mozilla.com (10.26.132.17)' can't be established.
RSA key fingerprint is 35:24:1f:30:7c:78:80:21:64:a8:fc:ba:e3:cd:3e:b2.
Are you sure you want to continue connecting (yes/no)?
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•