Labs, can you kick build140-m2?

Fail chromeos waterfall again. Anything updates?

the other slave build202-m2 is offline too. Right now, all the build slaves of storm-paladin are offline.https://uberchromegw.corp.google.com/i/chromeos/builders/storm-paladin

You caught build202-m2 between reboots.  It's up.

Dropping to a P1 accordingly.

chrome-bot@build202-m2:(Linux 12.04):~$ who -b
         system boot  2016-07-13 16:15

build202-m2 seems offline again
https://uberchromegw.corp.google.com/i/chromeos/builders/storm-paladin

online again, is there any maintenance going on? 

No maintenance.   These systems are set to reboot after the completion of each build.
These are Dell PowerEdge 720's and it takes a few minutes for them to do that.

Thanks! Can this builder become back tonight? 

come*

Can someone verify if this bot ever came back?

build140-m2 lost enough disks to destroy the RAID, so it's going to be out of service until the disks are replaced and the machine is reinstalled (disk swaps should happen today).

Looks like friedman started the process to have the disks swapped, so assigning to him.

+dnj in the event he sees it fit to swap this host with another if he's still

Troopers can do this:
https://chrome-internal.googlesource.com/infra/infra_internal/+/master/doc/cros.md#Repairing-Replacing-Slaves

I will this time, I guess.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/build/+/cacf1fcb4412da9354de97eb760af0c617deadb4

commit cacf1fcb4412da9354de97eb760af0c617deadb4
Author: dnj <dnj@google.com>
Date: Thu Jul 14 16:11:31 2016

The replacement is in place and active, back to you, friedman@!

the new builder 117-m2 is still offline.

Slave is online now.

great, thanks!

build117-m2 is offline again.

Oops, online now...

Machine is back online.

Please file a new request going forward surrounding build117-m2, as this original request was for build140-m2 and the history is now confusing to read.