Urgent.News

What's breaking now, across hundreds of outlets.

Tech

How One Remote Reboot Cost Me Three Days of Work

A short story about a remote reboot test that locked me out of a machine for three days, and the rule I wrote afterward.

How One Remote Reboot Cost Me Three Days of Work

As a software developer, I recently found myself setting up a Windows machine at a location accessible only by network connection. This setup required remote access, and I was in the midst of completing the task on a Saturday morning when I decided to reboot the machine as part of a routine check. The intention was to ensure the app could run autonomously post-restart.

However, upon initiating the reboot, the machine failed to return to its normal state. The issue became apparent: the Windows operating system on the machine did not boot from its internal disk but instead from an external drive that I had previously attached. I had neglected to consider the implications of a reboot on the boot sequence, assuming it would automatically revert to the external drive.

My partner's reaction was swift and firm – avoid rebooting, as the situation was precarious given the distance between us. The cost of this single reboot proved to be three days of inaccessibility to the machine. Every subsequent remote action I planned had to wait, as the machine was unresponsive. Looking back, I realize that treating a reboot as a benign action was a misjudgment.

On my local machine, I could intervene easily if something went awry. However, a remote machine lacks this immediate control, making the lack of an undo option a significant oversight. The simple question, "What is the way back if this goes wrong?" took more time to answer than I anticipated. Had I asked this question upfront, I could have avoided the costly three-day setback.

Moving forward, I've identified three key rules I will adopt. Firstly, I will refrain from initiating any reboot, shutdown, or power action remotely unless I have a physical presence at the machine. Secondly, for every step that cannot be undone remotely, I will document the recovery method in a concise line. Failure to do so means the action is postponed until someone physically present or an alternative access method, such as a network power switch or remote management port, is employed.

Lastly, I will verify the boot order on-site before proceeding with any installations. These rules may seem obvious, but they only become crucial when they prevent days of unnecessary work. For those managing remote hardware, I pose a question: what is the least expensive alternative to having a second way to access the machine?

A remote power switch is beneficial, but only if it can power the machine on automatically after a restart, which remains uncertain in my case.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at hackernoon.com →

More in Tech

More from Sunday 8 November →