I was updating Fedora 19 tonight when my system crashed ( I suspect it's a memory error)....but anyway it now **appears I have a lot of duplicate files on my system, at least that what yum check all reports. The crash happened after the updates had been installed I think during the verify stage.
This is a partial list of what "yum check all" reports:
Loaded plugins: langpacks, refresh-packagekit SDL-1.2.15-8.fc19.i686 is a duplicate with SDL-1.2.15-7.fc19.i686 1:autocorr-en-4.0.3.3-3.fc19.noarch is a duplicate with 1:autocorr-en-4.0.3.3-2.fc19.noarch 1:cups-1.6.2-7.fc19.i686 is a duplicate with 1:cups-1.6.2-4.fc19.i686 1:cups-filesystem-1.6.2-7.fc19.noarch is a duplicate with 1:cups-filesystem-1.6.2-4.fc19.noarch 1:cups-libs-1.6.2-7.fc19.i686 is a duplicate with 1:cups-libs-1.6.2-4.fc19.i686 desktop-backgrounds-compat-19.0.0-2.fc19.noarch is a duplicate with desktop-backgrounds-compat-19.0.0-1.fc19.noarch desktop-backgrounds-gnome-19.0.0-2.fc19.noarch is a duplicate with desktop-backgrounds-gnome-19.0.0-1.fc19.noarch dialog-1.2-2.20130523.fc19.i686 is a duplicate with dialog-1.2-1.20121230.fc19.i686 dmraid-1.0.0.rc16-21.fc19.i686 is a duplicate with dmraid-1.0.0.rc16-20.fc19.i686 dmraid-events-1.0.0.rc16-21.fc19.i686 is a duplicate with dmraid-events-1.0.0.rc16-20.fc19.i686 dracut-027-46.git20130430.fc19.i686 is a duplicate with dracut-027-45.git20130430.fc19.i686 dracut-network-027-46.git20130430.fc19.i686 is a duplicate with dracut-network-027-45.git20130430.fc19.i686 glusterfs-3.4.0-0.5.beta2.fc19.i686 is a duplicate with glusterfs-3.4.0-0.4.beta1.fc19.i686 glusterfs-api-3.4.0-0.5.beta2.fc19.i686 is a duplicate with glusterfs-api-3.4.0-0.4.beta1.fc19.i686 glusterfs-fuse-3.4.0-0.5.beta2.fc19.i686 is a duplicate with glusterfs-fuse-3.4.0-0.4.beta1.fc19.i686 1:grub2-2.00-18.fc19.i686 is a duplicate with 1:grub2-2.00-16.fc19.i686 1:grub2-efi-2.00-18.fc19.i686 is a duplicate with 1:grub2-efi-2.00-16.fc19.i686 1:grub2-tools-2.00-18.fc19.i686 is a duplicate with 1:grub2-tools-2.00-16.fc19.i686
The list goes on and on...
I am a relative newcomer to Fedora (I'm a Debian refugee) so my knowledge of yum at the moment is pretty minimal. Does anyone have any suggestions on how this can be fixed? The system still boots fine
I wrote this message originally on the regular users list but at least one person took exception to it even though it's not an F19 problem specifically.
Thanks
Tell us your "yum history"
On 05/24/2013 11:08 PM, Christopher Meng wrote:
Tell us your "yum history"
Too late Christopher - found "package-cleanup --dupes" in the Fedora forums (and a suggestion from another user on the regular list) - so I tried it - now the 19 partition is unbootable :) So it sort of solved my problem. Package cleanup ran into a bunch of what it said were zero-length files..dunno what it did or didn't do with them..nothing I guess. But it appears some . many or all were essential.
Anyway I can roll back time to a few hours ago :)
On 05/24/2013 11:39 PM, Frank McCormick wrote:
On 05/24/2013 11:08 PM, Christopher Meng wrote:
Tell us your "yum history"
Too late Christopher - found "package-cleanup --dupes" in the
Fedora forums (and a suggestion from another user on the regular list) - so I tried it - now the 19 partition is unbootable :) So it sort of solved my problem. Package cleanup ran into a bunch of what it said were zero-length files..dunno what it did or didn't do with them..nothing I guess. But it appears some . many or all were essential.
Anyway I can roll back time to a few hours ago :)
A second problem Christopher is there is no history for tonight when it happened. I guess Yum/RPM writes the file after/during the update process, which never ended properly. The partition still boots but ends up with the message of no /boot/init so I get a sh-4.2 prompt on a read-only partition. A fine state of affairs :)
--Cheers--
On Fri, May 24, 2013 at 23:39:17 -0400, Frank McCormick beacon@videotron.ca wrote:
On 05/24/2013 11:08 PM, Christopher Meng wrote:
Tell us your "yum history"
Too late Christopher - found "package-cleanup --dupes" in the Fedora forums (and a suggestion from another user on the regular list) - so I tried it - now the 19 partition is unbootable :) So it sort of solved my problem. Package cleanup ran into a bunch of what it said were zero-length files..dunno what it did or didn't do with them..nothing I guess. But it appears some . many or all were essential.
You need to be careful about using cleandupes. After a partially completed transaction you might end up removing extra stuff. Generally you want to start with yum-complete-transaction.
Frank McCormick beacon@videotron.ca wrote:
I was updating Fedora 19 tonight when my system crashed ( I suspect it's a memory error)....but anyway it now **appears I have a lot of duplicate files on my system, at least that what yum check all reports. The crash happened after the updates had been installed I think during the verify stage.
This is a partial list of what "yum check all" reports:
Try
package-cleanup --dupes
On 05/24/2013 11:23 PM, Ed Greshko wrote:
Frank McCormick beacon@videotron.ca wrote:
I was updating Fedora 19 tonight when my system crashed ( I suspect it's a memory error)....but anyway it now **appears I have a lot of duplicate files on my system, at least that what yum check all reports. The crash happened after the updates had been installed I think during the verify stage.
This is a partial list of what "yum check all" reports:
Try
package-cleanup --dupes
Yeah, that's what I found in the Fedora forums. So I tried it. Now the partition won't boot.
package-cleanup --dupes removed the dupes..at least it said it was....but it also ran into a bunch of files it said were zero-length...what it did about them I don't know. Short version: the partition is now unbootable. So I am back in Fedora 18...where I think I'll stay for a while. I don't anticipate re-installing 19...at least not for a while.
Frank McCormick beacon@videotron.ca wrote:
On 05/24/2013 11:23 PM, Ed Greshko wrote:
Frank McCormick beacon@videotron.ca wrote:
I was updating Fedora 19 tonight when my system crashed ( I suspect it's a memory error)....but anyway it now **appears I have a lot of duplicate files on my system, at least that what yum check all reports. The crash happened after the updates had been installed I think
during
the verify stage.
This is a partial list of what "yum check all" reports:
Try
package-cleanup --dupes
Yeah, that's what I found in the Fedora forums. So I tried it. Now the partition won't boot.
package-cleanup --dupes removed the dupes..at least it said it was....but it also ran into a bunch of files it said were zero-length...what it did about them I don't know. Short version: the partition is now unbootable. So I am back in Fedora 18...where I think I'll stay for a while. I don't anticipate re-installing 19...at least not for a while.
The only comforting thing is that this same problem could happen no matter what version you're running. :-)
Since F19 is beta it isn't a big deal IMHO. I've had similar things go wrong, disk problems, and getting it fixed took time and effort....but I was able to recover.
On 05/24/2013 11:35 PM, Ed Greshko wrote:
Frank McCormick beacon@videotron.ca wrote:
On 05/24/2013 11:23 PM, Ed Greshko wrote:
Frank McCormick beacon@videotron.ca wrote:
I was updating Fedora 19 tonight when my system crashed ( I suspect it's a memory error)....but anyway it now **appears I have a lot of duplicate files on my system, at least that what yum check all reports. The crash happened after the updates had been installed I think
during
the verify stage.
This is a partial list of what "yum check all" reports:
Try
package-cleanup --dupes
Yeah, that's what I found in the Fedora forums. So I tried it. Now
the partition won't boot.
package-cleanup --dupes removed the dupes..at least it said it was....but it also ran into a bunch of files it said were zero-length...what it did about them I don't know. Short version: the partition is now unbootable. So I am back in Fedora 18...where I think I'll stay for a while. I don't anticipate re-installing 19...at least not for a while.
The only comforting thing is that this same problem could happen no matter what version you're running. :-)
Since F19 is beta it isn't a big deal IMHO. I've had similar things go wrong, disk problems, and getting it fixed took time and effort....but I was able to recover.
Yeah maybe I'll reinstall when 19 is released, Or maybe not. Thanks anyway for the suggestion - it seems it's about the only thing that could be done under the circumstances
On Fri, May 24, 2013 at 11:43:15PM -0400, Frank McCormick wrote:
On 05/24/2013 11:35 PM, Ed Greshko wrote:
Frank McCormick beacon@videotron.ca wrote:
I was updating Fedora 19 tonight when my system crashed
Try
package-cleanup --dupes
Thanks anyway for the suggestion - it seems it's about the only thing that could be done under the circumstances
Not exactly! First you have to finish messed up upgrade, by whatever means necessary, and make sure that results are sane and bootable. Only then you are running 'package-cleanup --cleandupes'. I did such recovery procedures on quite few occassions and they work fine but you need to be careful about what you are doing.
Yet another possibility is to use '--justdb' rpm option to bring your rpm database to a pre-upgrade state and run an upgrade once again. Seems tad safer than moving with '--justdb' in another direction and makes sure that you are not left with unresolved dependencies.
Michal
On Fri, 2013-05-24 at 23:01 -0400, Frank McCormick wrote:
I am a relative newcomer to Fedora (I'm a Debian refugee) so my knowledge of yum at the moment is pretty minimal. Does anyone have any suggestions on how this can be fixed? The system still boots fine
FWIW, the few times I got stuck in a case like that, I rpm -V'ed the newer dupes, and if that resulted in an OK, you can do this:
rpm -e --justdb --noscripts (older version)
what that basically does is simply remove the entry from the RPM database without running any scriptlets or actually deleting any files from the filesystem.
On 05/25/2013 12:32 AM, Adam Williamson wrote:
On Fri, 2013-05-24 at 23:01 -0400, Frank McCormick wrote:
I am a relative newcomer to Fedora (I'm a Debian refugee) so my knowledge of yum at the moment is pretty minimal. Does anyone have any suggestions on how this can be fixed? The system still boots fine
FWIW, the few times I got stuck in a case like that, I rpm -V'ed the newer dupes, and if that resulted in an OK, you can do this:
rpm -e --justdb --noscripts (older version)
what that basically does is simply remove the entry from the RPM database without running any scriptlets or actually deleting any files from the filesystem.
I wish now had waited rather than running tum complete transaction ( which it never did) as it ended up marking the transaction files as invalid. It was then I ran package cleanup and that's what left my partition unbootable. Thanks for the suggestions anyway :)