I’ve been deploying Sophos Virtual Appliances recently and so I was presented with a bit of a challenge when the install was failing on physical hardware.

Error: install.tar wasn’t found on the installation media.

Error: install.tar wasn’t found on the installation media.

This happens because during part of the installation process. the USB drive is un-mounted and needs to be mounted again.

It also expects to find install.tar at /install/install/install.tar and so we must mount the device to the /install path.

 

You don’t need to be a wizard to re-mount the USB stick. It’s also not difficult to list all the drives and pick out your USB device address from the list. Keep reading to learn how to fix this easily:


Step 1: Reboot the server.

You can’t get past this error and start over without rebooting.

 

Step 2: Boot from the USB.

You’ll need to load all the way up to the installer, but don’t start the install yet.

Step 3: Open the Shell

press ALT + F2 before proceeding with anything else. This will open the shell, where we will run our command to re-mount.

 

Step 3: Re-Mount the USB drive.

The main command you will be running will be something like this

mount /dev/sdb1 /install

/dev/sdb1 was the path to my USB stick’s boot drive.

  • You can find yours by running fdisk -l to list the disks

If you don’t have any other devices attached to your server, it will most likely also be sdb1 for you. You can confirm the mount success by running ls- alF after mounting to get a directory listing, cd over to install dir and check it out.

 

Step 4: Exit the Shell Safely.

Press ALT + F1 to quit the shell

 

Step 5: Install.

Run the installer and enjoy your new Sophos UTM!

 


Notes:

I had to run through this this a couple of times to get it right. I don’t think I was quitting the shell properly, so make sure to quit the shell with ALT + F1 and proceed directly to installation without doing anything in-between.

Some helpful commands are:

  • cd to change directory
  • ls -alF to view directory contents
  • fdisk -l to view disks attached to the system

 


2 Comments

Mugetsu · June 24, 2017 at 7:41 pm

fdsik -l does not work. The easiest way is to go to the dev directory and look for the correct date (today).

Steve · August 10, 2017 at 2:02 pm

Thanks! Saved me some head-scratching. FDISK doesn’t seem to be on the media for 9.502-4 mine was sdb1 so no problems.

Leave a Reply

Related Posts

Amazon AWS

netdata: A remarkable server monitoring utility.

I wanted to write a short introduction to a tool that I’ve been using a lot on my newest servers and development projects. This tool seriously provides the most amazing way of monitoring and comprehending Read more…

Linux Server

How to install NGINX, get a free SSL certificate, and configure a reverse proxy (part two)

This is part two, the final part of configuring NGINX with SSL as a reverse proxy. Now that you have successfully installed NGINX and obtained a free SSL cert, you can proceed.   There is Read more…

Cisco Meraki

How to provide Guest WiFi network access securely with Cisco Meraki Appliances

If you have an office, facility, or residence with a lot of guest traffic and are needing to provide the guests with their own network using your existing Meraki equipment, this is the best way Read more…

%d bloggers like this: