[TMG1961]

When i boot up the laptop i get a black screen for 15 seconds just after the feather screen untill my desktop is visible. This is something new, used to be much much less then that. Ayone any idea what might be the problem?

[valtam]

Press the Home key when you reboot for verbose messages, see where it is sticking.

What is the output of:

Code:

systemd-analyze blame

and check the last reboot messages from /var/log/syslog.

[TMG1961]

Hi Jerry,


When i check syslog it doesnt shows anything from Aug 18 13:44:09 to Aug 31 09:43:54 after that no entries.


When i press the Home key during reboot the only thing i can read before its gone is scanning for btrfs


Outcome of systemd-analyze-blame is:

Code:

theo@Lenovo-B50-30:~$ systemd-analyze blame           9.116s NetworkManager-wait-online.service           8.309s ntp.service           7.580s rc-local.service           2.923s dev-sda1.device           1.897s dev-zram0.device           1.875s dev-zram1.device           1.034s networking.service           873ms accounts-daemon.service           846ms console-setup.service           819ms ModemManager.service           574ms systemd-logind.service           559ms lightdm.service           558ms ufw.service           537ms virtualbox.service           517ms NetworkManager.service           493ms grub-common.service           482ms virtualbox-guest-utils.service           476ms apparmor.service           471ms upower.service           460ms avahi-daemon.service           392ms preload.service           390ms lvm2-monitor.service           375ms systemd-udev-trigger.service           369ms irqbalance.service           354ms ondemand.service           340ms console-kit-log-system-start.service           330ms gpu-manager.service           262ms systemd-user-sessions.service           257ms thermald.service           233ms keyboard-setup.service           226ms rsyslog.service           218ms zram-config.service           197ms binfmt-support.service           180ms lm-sensors.service           174ms minidlna.service           173ms pppd-dns.service           144ms ubiquity.service           140ms polkitd.service           113ms NetworkManager-dispatcher.service           101ms systemd-modules-load.service             96ms systemd-udevd.service             93ms kmod-static-nodes.service             93ms systemd-journald.service             92ms dev-mqueue.mount             86ms udisks2.service             82ms hddtemp.service             76ms dev-hugepages.mount             75ms systemd-update-utmp.service             73ms [email protected]             59ms systemd-tmpfiles-setup.service             58ms dns-clean.service             48ms plymouth-read-write.service             48ms proc-sys-fs-binfmt_misc.mount             46ms sys-kernel-debug.mount             45ms resolvconf.service             35ms systemd-journal-flush.service             32ms systemd-tmpfiles-setup-dev.service             26ms postfix.service             22ms plymouth-start.service             21ms systemd-update-utmp-runlevel.service             17ms systemd-backlight@backlight:intel_backlight.service             14ms systemd-remount-fs.service             13ms ureadahead-stop.service             12ms systemd-sysctl.service             11ms rtkit-daemon.service             11ms sys-fs-fuse-connections.mount             9ms systemd-random-seed.service             6ms openvpn.service             6ms plymouth-quit-wait.service             4ms setvtrgb.service

[valtam]

If you don't use the BTFRS file system, you're probably using etx4, you can remove it:

Code:

sudo apt purge btrfs-tools

Set a Restore Point first.

[TMG1961]

Thank you, will do that. Now first have to catch up on making restore point, havent done that in a very longtime. I know, should do it more often but i keep forgetting.

[TMG1961]

The 15 sec black screen is still here after the feather screen. No btrfs scan anymore. Not sure why it takes so long.

[valtam]

Look through Menu, System, System Log for any hints of the delay.

[TheDead]

Hi,

Your sda (harddrive) takes a few seconds there.
Could it be a problem with the harddrive itself hitting a bad sector / calibration problem?
(weird clicking hard drive sounds is an almost 100% indication)
You could check the files sytem with fchk, and the hdd with smartmontools / smartctl
Better be safe than sorry

Another idead, albeit usually from Windows experience ... Could be an antivirus scan running, if you have one isntalled.

Cheers!

[TMG1961]

There are no clicking sounds, its an SSD
I have to look into smartctl, never used it before.

[TheDead]

With an SSD you can almost forget my post. Lucky you!
Maybe try to boot Linux Lite from USB just to confirm its your install.
Otherwise, maybe checking if theres a driver update.

Just throwing ideas... good luck! :-S