Created attachment 774438 [details] systemd-analyse plot Description of problem: Startup time is 1.31min very consistent. Disableling service does not change boot time. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Boot system 2. 3. Actual results: Expected results: Additional info:
Not sure why this was moved against system since these are the slowdown components.. NetworkManager.service restorecond.service accounts-daemon.service rtkit-daemons.service plymouth-quit-wait.service gdm.service NetworkManager-wait-online.service And disabling what services? ( might be related to #985038 )
LVM, Firewalld, Avahi, chrony. They are all in the 20 seconds on systemd-analyse blame. Remove one. Reboot run blame again. The next one moves up in the 20 second range. (firewall is back on :) ) Included boot.log
Created attachment 774506 [details] boot.log file plymouth-wait-quit failure
Created attachment 774509 [details] boot with plymouth.enable=0
Boottime does not change. Startup finished in 1.201s (kernel) + 959ms (initrd) + 1min 31.927s (userspace) = 1min 34.088s
Please boot with "systemd.log_level=debug" on the kernel command line and then attach the output of the command "journalctl -b".
Created attachment 774861 [details] Boot with systemd.log_level=debug, output from journalctl -b
That output does not contain debug output since you added "systemd.log_level=debugh" debugh instead of debug so you need to do it again and can you attach your /etc/fstab as well since there is most likely something wrong with it systemd[1]: Mounted /mnt/26CEDA80CEDA47A7. jul 17 18:55:00 localhost.localdomain systemd[1]: Job dev-disk-by\x2duuid-48A00C08A00BFAE8.device/start timed out. jul 17 18:55:00 localhost.localdomain systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-48A00C08A00BFAE8.device. jul 17 18:55:00 localhost.localdomain systemd[1]: Dependency failed for /mnt/48A00C08A00BFAE8. What are you mounting here /mnt/26CEDA80CEDA47A7? and here /mnt/48A00C08A00BFAE8 < which is failing?
Created attachment 774991 [details] with debug not debugh Sorry, microsoft natural F10 is h when not in f-lock whish is special spell funcion.
Still missing your /etc/fstab
Created attachment 775108 [details] /etc/fstab
What happens if you comment out those mnt entries there and or change them to use UUID= instead ( you can just run the blkid command to find the UUID entries )
Created attachment 775468 [details] boot plot comment out Looks a lot better now. 37s is ok.
37s is probably what people get out from our crappy defaults on rotating media. By disabling the stuff you dont actually need ( unless you need everything there ) you should be able to get down to 12s on rotating media and about <4s on SSD What kind of hardware are you running on?
CPU: Intel(R) Core(TM)2 Duo E8400 @ 3.00GHz Memory: 2GB Motherboard: ASUS P5Q (intel P45) Videocard: [AMD/ATI] RV620 LE [Radeon HD 3450] Harddrive: Seagate Barracuda 7200.12 500GB ( ST3500418AS ). Already tried to turn off as much as possible. 12s would be nice :). Still have this boot error message. [FAILED] Failed to start Wait for Plymouth Boot Screen to Quit. See 'systemctl status plymouth-quit-wait.service' for details. Looks like most time is spent on this in the boot plot.
Created attachment 775500 [details] systemctl mask plymouth-start.service Startup from 37s to 25s without plymouth. Seems like a bit much. Just benchmarking for fun here
Created attachment 775642 [details] systemctl mask accounts-daemon.service
Created attachment 775643 [details] both accounts daemon and firewall mask
Created attachment 775644 [details] all slow services masked
Looks like it was the same as bug 983688 *** This bug has been marked as a duplicate of bug 983688 ***