Submission + - Handling Remote/Headless Boot Failures 1
abroadwin writes: A coworker of mine has two machines in another state, and these machines require periodic maintenance (which sometimes necessitates a reboot). Of course, it's possible that something will go wrong when the machine is coming back up (such as a disk check failure), leaving the machine waiting at boot and network inaccessible. Both machines are running Linux, and the working assumption is that at least one machine on the same network is remotely accessible at the time of the other machine's failure. Does anyone here have any experience in administering remote/headless/inaccessible computers in a similar situation? If so, how do you handle it?