So my power went out when i tried to install KVM using yast, now i think the package is corrupted, when i try to install it again, i get the error “Error: Package installation failed”. Anyone know how i would go about removing the corrupted files so that i can finally download it?
Thanks for reading
Also, i forgot to say but can’t edit OP, but it gets stuck on “Verify installed packages”, so it is most definitely a problem with corrupted packages
An update:
I have now re-installed opensuse and… same problem occured.
I then tried to do it using my laptop through a virtual machine, same error.
So it doesn’t seem to be a problem with my device, but a problem on opensuse’s side, can anyone confirm? I will probably make a bugreport tomorrow, please tell me if it works for you if you have the time to try it, so it isn’t just my router blocking it from downloading or something dumb
You don’t provide enough details about each attempt you did, but be aware that if you re-install only by removing your partitions and then create <exactly> the same partitions again, your old files from your previous system including any corrupted files will re-appear. You need to either change your partition (and file system) sizes slightly which means not using default install configurations or purposefully wipe the disk clean before re-installation.
But,
You have an easier way.
Just purge the downloaded package files, if any were corrupted then they will be removed, forcing a re-download. Else, default behavior is for cached rpms already downloaded to be re-used.
To purge your zypper cache, you must “clean” as follows
zypper clean --all
Of course, that only works if your rpm packages were corrupted… If your power went out not during downloading but during installation, then your problem might not be recoverable… And instead of chasing a troubleshooting solution, I would highly recommend wiping clean and re-installing.
Wiping clean generally would mean using a LiveCD like Gparted Live, removing the existing partitions, then creaiting a new partition, then formatting, then removing everything so that your disk has all free space with the data destroyed. Or, a much faster way would be to mount your disk in another system (can be a LiveCD), use dd to zero your partitions, then remove the partitions and re-install.
TSU
To reinstall the first time i just told it to format all disks in the installer, and i couldn’t find any files that i had form before. I tried using your method using Gparted live to remove all partitions, then create one large particion in their place, formated that and then deleted all partitions. Although in both cases i got the same result, it crashed
I tried the zypper clean command, and it un-jammed it a bit by letting me download all the packages again, but it still crashes with the same message, although this time i recorded it and was able to see that the last message it gave me before crashing was “Building repository ‘google-chrome’ cache”. Don’t know what that has to do with it though, i don’t even think i had google chrome installed at that time.
Yeah, i don’t think the RPM packages are corrupted, i left the installation on for like 20 seconds before the power went out, and it only took me about 2 seconds to download the RPM packages.
Post the results of the following so we know what repositories you have installed and enabled.
zypper lr -d
In general,
Whenever you upgrade you should always disable every repository except the 0ss and oss-update repos.
Then, after you’ve successfully upgraded, re-enable any other repos, and after again verifying that they point to the correct versions for your upgraded system, do a “zypper up” (update, not upgrade again).
TSU
So i disabled all repositories except the ones you recommended, did a zypper clean, and no difference except now it crashes after building the official repository. Anyway, here are the results after disabling unecessary repos, usually i have chrome, easy-rpm and megamaced on, the sandisk is my installer USB, I forgot to remove it but it was disabled when i tried to install as you can see.
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
--+-------------------------------------+-----------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------------------------+--------
1 | Google-Chrome | Google-Chrome | No | ---- | ---- | 99 | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64 |
2 | http-download.opensuse.org-5cc04659 | home:megamaced | No | ---- | ---- | 99 | rpm-md | http://download.opensuse.org/repositories/home:/megamaced/openSUSE_Tumbleweed/ |
3 | openSUSE-20170516-0 | openSUSE-20170516-0 | No | ---- | ---- | 99 | yast2 | hd:///?device=/dev/disk/by-id/scsi-1SanDiskCruzer_Edge-part2 |
4 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/tumbleweed/repo/oss/ |
5 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | No | ---- | ---- | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/non-oss/ |
6 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/oss/ |
7 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/tumbleweed/repo/oss/ |
8 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |
9 | spotify-easyrpm | spotify-easyrpm | No | ---- | ---- | 99 | rpm-md | dir:///var/cache/spotify-easyrpm |
Not sure what you mean with upgrade, i am pretty new to opensuse, but since i am using tumbleweed, shouldn’t i never need to upgrade my system? Do you mean upgrade as in install virtualization tools? Anyway, here is the output of the zypper up command, not sure what to make of it
[sudo] password for root:
Loading repository data...
Reading installed packages...
The following 6 package updates will NOT be installed:
elfutils libaccounts-glib0 libasm1 libdw1 libelf1 libsensors4
The following application is going to be REMOVED:
Desktop
No additional space will be used or freed after the operation.
Nothing to do.
Maybe i am already at the latest version? Sorry for the lack of knowledge of opensuse
Pls post your zypper log which is at the following location to a pastebin
/var/log/zypper.log
TSU
Well, its too large to paste in any pastebin i could find, but i found this filesharing site: https://uploadfiles.io/i6au3
Anyway, today i began installing it manually instead, so you can ignore the references made to kvm today, maybe the solution could be of help for people with problems with it in the future
Guys,
I just upgrade my OS to Thumbleweed from Suse 13.1. It was a long way I ended up doing a fresh install. I am having the same issues with the KVM installation here is my zypper logs.
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 --------------------------------------
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - alias : repo-debug
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - name : openSUSE-Tumbleweed-Debug
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - enabled : 0
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - autorefresh : 1
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - url : http://download.opensuse.org/debug/tumbleweed/repo/oss/
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - path : /
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - type : NONE
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - priority : 99
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - gpgcheck : D(Y) repoD(Y) sig? pkgD(Y)
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - keeppackages: 0
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - filePath: /etc/zypp/repos.d/repo-debug.repo
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoManager.cc(repositories_in_file):276 repo file: /etc/zypp/repos.d/repo-source.repo
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] IniParser.cc(parse):84 Start parsing /etc/zypp/repos.d/repo-source.repo[g___]
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] IniParser.cc(parse):138 Done parsing /etc/zypp/repos.d/repo-source.repo[eF]
2017-06-12 15:53:31 <1> Robotechpc(4453) [Progress++] ProgressData.cc(report):88 {#7|/etc/zypp/repos.d/repo-source.repo}END
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 --------------------------------------
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - alias : repo-source
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - name : openSUSE-Tumbleweed-Source
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - enabled : 0
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - autorefresh : 1
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - url : http://download.opensuse.org/source/tumbleweed/repo/oss/
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - path : /
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - type : NONE
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - priority : 99
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - gpgcheck : D(Y) repoD(Y) sig? pkgD(Y)
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - keeppackages: 0
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191 - filePath: /etc/zypp/repos.d/repo-source.repo
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoFileReader.cc(repositories_in_stream):191
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] PathInfo.cc(dirForEach):553 readdir /var/cache/zypp/raw
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] PathInfo.cc(dirForEach):553 readdir /var/cache/zypp/solv
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] PathInfo.cc(dirForEach):553 readdir /var/cache/zypp/packages
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] RepoManager.cc(init_knownRepositories):881 end construct known repos
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypper] Zypper.cc(cleanup):5356 START
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypper] main.cc(~Bye):59 ===== Exiting main() =====
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp] PathInfo.cc(recursive_rmdir):426 recursive_rmdir /var/tmp/zypp.HUdmKk
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/zypp.HUdmKk{d 0700 0/0}
2017-06-12 15:53:31 <1> Robotechpc(4453) [zypper] Zypper.cc(~Zypper):374 Zypper instance destroyed. Bye!
I will try to install from terminal and let you know how it works.
Just reading your log and not comparing it to anything, IMO it’s noteworthy that your TW repos don’t appear to be enabled.
So,
- Be very careful posting to someone else’ Forum thread. Even if things seem similar, unless your situation is identical in all relevant aspects (and in this case it’s open what really happened), your solution won’t be the same.
- As noted to the other person, it looks like you’ll need to describe in detail exactly which upgrade method you’re doing, and perhaps most importantly what guide you’re following… Plus of course your specific details.
- You should post info about your machine using the same commands described, in particular listing your repos
zypper lr -d
So,
Bottom line is that you should start a new Forum thread.
TSU