Ok, I fixed it, It was a problem with my file-system. Here is what I did:
First I saw that stat
returned an input/output error. That seemed strange to me, so I checked the whole directory:
# stat /usr/bin/* | grep "Input/output error"
And got a whole list of errors. Thus I knew that it was not a problem with dumpsolv, but rather something with a bit more impact. This lead me to search the web and I found out that it could in fact be an error in the file-system. To repair the root file-system in OpenSuse they offer some really great advice: http://www.novell.com/documentation/suse91/suselinux-adminguide/html/ch12s05.html
Thus I booted up the installation-DVD, canceled the installation to get my command-prompt as root and used e2fsck
on my root partition, which is /dev/sdb1
like so:
# e2fsck /dev/sdb1
After this I got a really long list of different inode errors, which I read carefully and fixed whatever could be fixed (which was everything, I guess). After this I rebooted my system from harddrive and the problem was solved. I can install my updates and everything is running fine now.
But if you try this: be extremely careful! You are messing with your root partition here and you should read everything it tells you and verify it. Best have a second computer running to check in case you are not sure about something. If you get a bad superblock (which I did not have) you can use dumpe2fs <partition>
in order to see which block it is and then use e2fsck -b <block> <partition>
to restore the file-system from backup.
Everything is explained well in the link I posted above plus there are a lot of websites on the internet containing information about the use of e2fsck
and dumpe2fs
, you should consult these first if you have any doubts.
I do hope that this can help someone else.