How to reinstall an operating system remotely, using TrueNAS as the example
Remote desktop cannot reinstall an operating system, because the installer runs when the operating system does not. An IP KVM sits underneath it, so it can.
We often run into a crashed system at a customer site. In the past there were usually a few ways to deal with it:
- Find someone local to go and look at it, and reinstall the system if it comes to that. This only works if that friend knows the system well and can install it themselves
- Send a colleague out to the site to do the debugging, the repair, the reinstall. This costs a great deal and takes a long time, and the next time it happens you have to do it all over again
- Send the hardware back to us. That takes a long time too, and the business at the site is interrupted while it is away
All of them are awkward, and all for the same reason: distance. But this is the age of networks, so let me offer another option to consider — solving it remotely with a Beacon IP KVM. You don't travel, and nobody has to be on site. All you need is a BeaconKVM sitting next to the machine at the far end.
In this article I'll use BeaconKVM as the example and go through reinstalling TrueNAS remotely. For any other operating system, it works the same way.
The steps, in short
Here is a quick summary of what we are going to do:
- Get BeaconKVM running
- Connect to the TrueNAS machine remotely through the BeaconKVM console, restart it remotely, go into the BIOS, and set it to boot from the USB stick
- Install TrueNAS remotely, exactly as you would install it locally
Step one, get BeaconKVM running
There are two ways to do this. One is to buy the ready-made hardware from the BeaconKVM website,

the other is to install it from the package we provide. That package only supports the Raspberry Pi 4B at the moment, and there is both a video and a written guide for it; anyone who has played with a Raspberry Pi before will have no trouble.
If you are starting from zero, I would suggest buying the hardware — it is simple to set up, there is a video to follow, and you can contact us for help. If you don't mind tinkering, go with the Raspberry Pi 4B route; you don't have to wait for hardware to arrive before you can use it.
Step two, connect to the TrueNAS machine remotely
Once step one is done, the KVM device shows up in the BeaconKVM console. Click the Remote KVM button to open a remote KVM session, click connect, and the TrueNAS screen appears.



Once we can see the screen, reinstalling TrueNAS means restarting the machine, going into the BIOS, and setting it to boot from the USB stick.

All of this happens in a browser, and this is the biggest difference from remote desktop. I have never heard of remote desktop software that can get into BIOS setup, because at that point the operating system is not running — and if the operating system is not running, the remote desktop software certainly isn't either.
Last step, install TrueNAS
This step is no different from installing TrueNAS any other time. Follow the steps one by one, reboot when it's finished, and we have a brand new TrueNAS.

In summary
An IP KVM may not feel as good to use as remote desktop, because remote desktop runs directly on the operating system and can use screen-capture techniques to get a better picture. But there is one thing remote desktop cannot do: exist independently of the operating system.
That is exactly where the value of an IP KVM lies. Picture it — a fault at a site needs an engineer sent out to fix it, and in the end all it took was reinstalling the system, but it cost you over $1,000 in travel and at least a day of time. A BeaconKVM is $249. It only has to earn its keep once.