We'd love to hear about it! Click here to go to the product suggestion community
In reply to Scott_Klassen:
@Mast: SSI ISO is for Sophos/Astaro branded hardware appliances.
In reply to Astaphos:
Just ran into this problem, and the /install mounting trick worked perfectly for me as well! I did it directly after the hardware detection.
Hardware: Intel D2500CC (using the 64-bit kernel)
Used the excellent Rufus for iso -> usb-key.
In reply to pclov3r:
pclov3rI thought I'd pitch in to the community to helpAfter many hours of trial and error I found the solution. Mount /dev/sdb1 to /install to install AFTER the hardware detection runs. The hardware detection is what is causing it to be unmounted. So once you get a report of the hardware installed get into the shell by running ALT+F2 than run the mount command and it should work from there.
Thank you so much to pclov3r . After two hours I found your tip and you make my day.
In reply to Tony Rivero:
Well, 6 years after this thread was initially established and it's still going strong! Why Sophos don't give us a 21st century solution to this issue I do not know. Anyway...
I have just purchased an SG135 and I am attempting to install UTM 9.5 on it via a USB flash drive. I have followed all recommendations in this thread, but I am still getting the 'install.tar' error.
Is there a new trick with later versions of UTM 9 which I need to be aware of?
One question I have however is assuming you get the install media booting and arrive at the install screen, does it matter which method you use to get there?
Also, could someone please provide me with an answer on which version of the ISO to use? There seems to be only the Hardware/SSI and Software versions now. Given that I have a fully stock Sophos hardware appliance I am assuming the SSI version is what I should be using? I have not been able to find clear directions regarding this so far.
In reply to SamFickling:
...and to answer my own question:
Yes, it does matter which method you use to boot the ISO. Switching to Rufus resolved my issue. :)
Also, the SSI ISO appears to work fine with my stock SG135 box.
In reply to CharlesErrington:
After some hours trying diffrent methods I found this thread.
To check what sdb number the installation media is just flick to Alt-F4 View Log at the first screen. You can see it there.
I used asg-9.502-4.1.iso on a Dell Optiplex 790 with Intel i350 T2.
Had problems with the file names, as other people, until I switched to Rufus.
Did the mount /dev/sdb1 /install after the hardware check as suggested and it worked fine after that.
In reply to Tomas Bengtsson:
It's work for me in SG115w. Good job! ;-)
In reply to Konrad Biesiadecki:
still an issue, i'm afraid. thanks for the help.
fwiw, another way to get the list of drives from the shell is w/
that will list all your found partitions and you should be able to tell which is which.
a bit suprising this is still an issue 6 years on...
In reply to Erin Jones:
Hey,I had a problem with mounting, but I tried a solution where USB is mounted to the upper port and the keyboard to the bottom. Probably all you do well, only sdb1 that you want to mount is just the port on top.mount /dev/sdb1 /install (when bootable USB stick is mounted to the upper port)Please, try this solution.
I was able to use the work around in the thread to get it working. The primary purpose of my post was to note that you can you 'blkid' to help identify the name of your install partition that needs to be mounted.