Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Installation Failed - Installer searching for 'plymouth-plugin-script...' file that does not exist

Hello All! While trying to install UTM on a Dell Optiplex GX520, I get to step 3 of 6 and then it fails. 

According to the log:

bootstrap: system: install /install/install/rpm/ep-up2date-9.35-7-g219fd45.rb1.i686.rpm /dest/opt/inst/rpm/ep-up2date-9.35-7-g219fd45.rb1.i686.rpm

bootstrap: system: returned with exit status 0

bootstrap: system: install /install/install/rpm/plymouth-plugin-script-0.8.8_git201309032142-5.17.1322.g0e019d3.rb1.i686.rpm /dest/opt/inst/rpm/plymouth-plugin-script-0.8.8_git201309032142-5.17.1322.g0e019d3.rb1.i686.rpm

bootstrap: install: can't stat '/install/install/rpm/plymouth-plugin-script-0.8.8_git201309032142-5.17.1322.g0e019d3.rb1.i686.rpm' : No such file or directory

bootstrap: system: returned with exit status 1

bootstrap: END screen 'inst_rpm_copy"

bootstrap: END task 'installation'

bootstrap: START task 'fail'

bootstrap: START screen 'fail'

 

Okay, that's clear enough. So I open up my USB drive (created using LiLi USB creator using iso file asg-9.351-3.1.iso) and navigate to the /rpm folder and can see that indeed that file is missing. Here is what is in the /rpm directory:

plymouth-0.8.8_git201309032142-5.17.1322.g0e019d3.rb1.i686.rpm

plymouth-plugin-script-0.8.8_git201309032142-5.17.1322.g0e019d3

plymouth-scripts-0.8.8_git201309032142-5.17.1322.g0e019d3.rb1.i6

It looks like the installer is calling for a mix between the two files. The "plymouth-plugin-script" file does not include ".rb1.i686.rpm" in the name, which the installer is looking for. 

Can I rename the "plymouth-plugin-script..." file from my install media from "plymouth-plugin-script-0.8.8_git201309032142-5.17.1322.g0e019d3" to the name the installer is looking for? Will this cause other problems? Why is this file named incorrectly or why is the installer looking for an alternative, seemingly mixed-and-matched file name other than what is available?

Thanks!



This thread was automatically locked due to age.
Parents
  • Lots of folks try it, but for software installs, USB thumbdrives are not supported. Some get it to work, but more often it fails with truncated filenames due to the "burning" software used. ISO burned to disk is the only supported method. For Hardware installs, ISO burned to disk or the Sophos proprietary SUSI software and SUSI thumbdrive (yes, it is different than an off the shelf one. Has an extra chip to emulate an optical drive).

Reply
  • Lots of folks try it, but for software installs, USB thumbdrives are not supported. Some get it to work, but more often it fails with truncated filenames due to the "burning" software used. ISO burned to disk is the only supported method. For Hardware installs, ISO burned to disk or the Sophos proprietary SUSI software and SUSI thumbdrive (yes, it is different than an off the shelf one. Has an extra chip to emulate an optical drive).

Children
No Data