build29-m2 was also in this state, I just logged in and rebooted it.

After rebooting build111-m2, and build184-m2 are still offline. This will hurt CQ performance, and break release builds.

Can we pass this to the lab team to get the physical machines repaired?

Passing to the current trooper, since I'm not finding how to pass it to the Golo team where it should be in our docs.

https://uberchromegw.corp.google.com/i/chromeos/buildslaves

build29-m2 and build184-m2 are connected to master.chromeos

Someone else in the team is currently looking at build111-m2.   Elliott, if it's not you pass the ticket back to me.

Thanks Peter.  I reported on build111-m2 yesterday, but don't know who to alert on these.  Is it always dgarrett?  https://bugs.chromium.org/p/chromium/issues/detail?id=671405

build111-m2 just got new disks.  I'm upgrading it's firmware just in case, then it will get a reinstall.

In theory, it's the current deputy, which is currently jrbarnette.

build111-m2 is dead.  Replacing.

Issue 671405 has been merged into this issue.

build111-m2 is back with a brand new server.  Please be kind to it.