On 11/28/2016 06:44 AM, Constant Brouerius van Nidek wrote:
My system does not work as expected. Have looked into hardware problems and memory, but did not find anything up to now
What you report below is very informative, certainly not "nothing"
Did a new install and although in the begin it worked quit well I had some system freezes. Started to look into journalctl and found quit a lot failed results.[ ... ]
What is wrong with computer or its software. Why a whole bunch of failures and where to start working on the system.
What it looks like to me is that you have one failure that results in a CASCADE of errors.
Nov 25 12:22:16 linux-c8ur kernel: XFS (sda5): Starting recovery (logdev: internal) Nov 25 12:22:16 linux-c8ur kernel: XFS (sda5): Metadata corruption detected at __write_verify+0xd0/0xe0 [xfs], xfs_dir3_leaf1 block 0xea5a00 Nov 25 12:22:16 linux-c8ur kernel: XFS (sda5): Unmount and run xfs_repair
There is you problem. You have a damaged /corrupt XFS file system. I suspect that you followed the defaults and that you formatted /home as XFS. My first experiments with XFS *under 13.2) ended up similarly PDQ. There are tools to repair this. later ...
Nov 28 06:30:31 linux-c8ur dbus[1026]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Nov 28 06:30:31 linux-c8ur systemd-logind[7079]: Failed to fully start up daemon: Connection timed out Nov 28 06:30:31 linux-c8ur systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE Nov 28 06:30:31 linux-c8ur systemd[1]: Failed to start Login Service. -- Subject: Unit systemd-logind.service has failed
So you are starting in graphical mode, then, and the login daemon wants to make use of /home so that a user can log in. Only /home isn't there. This is what I mean about cascade errors. The solution is to bring your system up in maintenance mode and repair the XFS. What that takes in your specific instance I'm not sure; it may be as simple as starting single user and running the XFS tools. But just to make sure, I'd run a memory check and a disk bad block scan. How to do that? Again it might depend on your specific situation, but long ago I prepared a bootable 'rescue/maintenance' CD and have the image on a bootable USB as well. You may choose to have Knoppix. Earlier version of the openSuse installation DVD also had a rescue mode but that was specific to the OS; maybe the memory checker of those transcends versions :-) The first 1T drive I ever purchased cascaded errors so I ran a badblock/f3write on it and found it was VERY flawed and took it back. The badblock scan of a 1T drive takes a couple of days. The vendor must have thought me a little strange, but anyone strange enough to produce the evidence of a taking three days out to run a badblock scan on a 1T drive had to be taken seriously so there was no argument. I've run badblock/f3write sans on 32G and larger USB and SD chips. The good one take overnight, the bad ones show up PDQ, after a couple of G. Again, wielding evidence. I've always had vendors refund/replace with no argument. My point here is twofold. 1. You errors are a CASCADE starting with a bad XFS. For some people, it seems, XFS is not a good choice. I don't know why my XFS failed in the first place. I upgraded my tools (see archives) and my kernel (also see archives) and haven't had any more problems. However my inclination is to use ext4 unless I'm clearly faced with a problem about inode provisioning. 2. There are plenty of tools to check the reliability/integrity of your hardware. If you haven't already downloaded copies than I suggest you find some way to do so and check your hardware. -- Almost all quality improvement comes via simplification of design,manufacturing, layout, processes, and procedures. -- Tom Peters -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org