[deleted]
Ok, I did add these commands at boot (in grub). I followed the instructions. I do not know much in detail about Systemd. Where does this debug info come out? I did not find anything in /var/log.
However, when I run the command 'system-analyze blame' I get this top list:
30.321s udisk2.service
6.350s NetworkManager-wait-online.service
6.085s home.mount
4.589s systemd-fsck@dev-disk-by\x2duuid-nnnnnnnnnnnn (n equals a disk ID and alot of other numbers)
The rest of the list is is in the 500ms or much lower.
Could this mean a faulty disk?
Could it be that I have a bad drive and the journaling system is forced to hog power all to often and therefor creating an illusion of a slower CPU? My journaling log is only 35MB in size (I have limited the size manually).
If I check the logs in the log program there are ALOT of failed tries to create a PopplerDocument, which is pdf. I do not know why it tries to do this so many times. It is not one and the same but many different files. All PDFs. I have since deleted those faulty PDF-files.
The drive in question is my mechanical (an older drive) which contains my /home. If I check the drive in the disk utility it say it is fine and only 27+% full. The SMART data indicates high age but no other warnings like read errors, sector re-locations and such. No abnormal temperatures or noises from it either. I made a longer self test to verify.
