![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 2018-02-02 23:04, Ken Schneider - openSUSE wrote:
On 02/01/2018 04:44 PM, Carlos E. R. wrote:
Hi,
This machine crashed while YaST was updating it and installing things. Hard crash, the filesystem became R/O (the disk is removable, it is in a caddy). Bad filesystem corruption, automatic fsck on boot failed, had to fsck from another disk.
So some files are broken, and I find them now and then. Thunar had broken libraries, for instance. Now there is another when I run VLC:
cer@linux-backup:/tmp/mozilla_cer0> vlc 27566544_559085681122620_5011855560279064576_n.mp4 vlc: error while loading shared libraries: /usr/lib64/libvlc.so.5: file too short
So, is there a way to check all rpms in the system?
I tried "rpm -qa V", but it lists all files, not rpms.
In the case of VLC I'm going to force update all installed packman packages. Brute force attack.
Hi Carlos, Had similar issue this past weekend but in my case one of my ram modules decided to go on vacation while while running zypper dup. After reseating all of the ram modules and rebooting I ended up opening YaST-->Software Manager. I selected the repo view and forced an update of "All in this list". I let it run overnight and after a reboot all seems to be well since. I haven't run a mem test yet but I will if I have problems again with the system seizing.
I did that on the packman repo, for testing the procedure. Did not on the XFCE repo, the other one that was selected when the system crashed. But my "verify" found other packages that were not apparently from either one. From instance, SuSEfirewall2 or grub2 were damaged. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" (Minas Tirith))