1200250 - t-w864-ix-024 is unreachable

Status: RESOLVED FIXED

(Infrastructure & Operations :: DCOps, task)

Comment 1

[Van Le [:van]]

bad drive, opened up #FGK-444-18369 for RMA

Comment 2

[Van Le [:van]]

drive i picked up was DOA. will need to grab another one from iX.

Comment 3

[Van Le [:van]]

i haven't been able to swing by iX the last 2 weeks. ive asked them go to ahead and ship the bad drive to scl3.

Comment 4

[Van Le [:van]]

i have reimaged this host twice and it boots up to o/s but not reachable. any ideas? are we still having imaging issues?

Comment 5

[Amy Rich [:arr] [:arich]]

There shouldn't be issues with imaging, especially wrt to it being pingble. Can you ping OUT of the machine? Are you sure it reimaged at all (maybe the ethernet interface is broken)?

Comment 6

[Amy Rich [:arr] [:arich]]

I noticed that all of the w8 machines I reimaged earlier this week were not pingable but had the screensaver running. I'm trying to reimage them now to see if Q's modifications to MDT and GPO in the past few days have changed things. If not, though, looks like w8 is broken.

Q: I'm doing 181 - 194 now.

Comment 7

[Van Le [:van]]

hmm looks like q fixed the imaging issue or it just took a while for it to finish installing all the drivers. let me know if it still needs to be reimaged again if there was a fix of any sort but the host is back online.

vans-MacBook-Pro:~ vle$ fping !$
fping t-w864-ix-024.wintest.releng.scl3.mozilla.com
t-w864-ix-024.wintest.releng.scl3.mozilla.com is alive
vans-MacBook-Pro:~ vle$ ssh !$
ssh t-w864-ix-024.wintest.releng.scl3.mozilla.com
The authenticity of host 't-w864-ix-024.wintest.releng.scl3.mozilla.com (10.26.40.54)' can't be established.
RSA key fingerprint is 86:8a:e9:78:35:49:79:7a:d6:3e:aa:86:e8:9e:b8:0c.
Are you sure you want to continue connecting (yes/no)?

Comment 8

[Phil Ringnalda (:philor)]

Reenabled, ran a job at 1024x768 and failed tests as a result, redisabled.

Comment 9

[Q]

A second reboot of the machine fixed the resolution

Comment 10

[Q]

A good point of note if a machine is rebooted with a monitor attached or if fakemon  interrupted the resolution will be incorrect. This can be cleared manually or the machine can be rebooted.

Comment 11

[Q]

I did verify that after fakemon runs correctly once the resolution sticks for subsequent reboots

Comment 12

[Phil Ringnalda (:philor)]

So, should I wait 8 hours after an unreachable is closed as reimaged, then reboot twice while the slave is disabled, then enable it? Not sure what else I can do to avoid this situation.