friendica.eskimo.com
Thank you all so much for your help, here is my output of systemd:
It must be something weird with my initial boot. I am dual booting, but on separate hard drives. My PC does have 6 hard drives in it however. Or, maybe something is messed up in my install?
<br />43.616s fstrim.service
11.630s plocate-updatedb.service
10.593s systemd-suspend.service
4.389s plymouth-quit-wait.service
4.277s ufw.service
4.028s systemd-resolved.service
3.964s systemd-timesyncd.service
3.330s NetworkManager-wait-online.service
2.759s apt-daily.service
2.293s fwupd.service
1.563s logrotate.service
1.316s NetworkManager.service
835ms apt-daily-upgrade.service
693ms motd-news.service
653ms blueman-mechanism.service
458ms user@1000.service
450ms dev-sda2.device
432ms dpkg-db-backup.service
404ms udisks2.service
349ms accounts-daemon.service
335ms gnome-remote-desktop.service
309ms ubuntu-system-adjustments.service
307ms apparmor.servicefstrim.service is disk tool (that's supposed to only be run once a week, not every time you boot) that automatically cleans up old deleted SSD data. opensource.com/article/20/2/tr…
It looks like it's running too often, or on the wrong devices, every time you boot your computer. You can actually safely disable it; askubuntu.com/questions/116512… but it's worth looking into why it's taking so long and being run so often.
Running this should show you the log results of fstrim doing it's thing without actually doing anything;sudo fstrim --fstab --verbose --dry-run
These two will show the status of fstrim and it's autorun service;
systemctl status fstrim systemctl status fstrim.timer
I got most of this from a quick google search; duckduckgo.com/?q=fstrim.servi… You can do the same for the other major time-takers on your boot list. For comparison, here's the top results of my semi-fresh install of linux mint;
dageek247@mintPC:~$ systemd-analyze blame
2.237s NetworkManager-wait-online.service
2.077s systemd-binfmt.service
2.003s systemd-resolved.service
1.976s systemd-timesyncd.service
1.916s fwupd-refresh.service
1.365s logrotate.service
1.326s NetworkManager.service
933ms fwupd.service
401ms blueman-mechanism.service
334ms udisks2.service
263ms apt-daily-upgrade.service
254ms dpkg-db-backup.service
229ms dev-nvme0n1p3.device
215ms accounts-daemon.service
201ms power-profiles-daemon.service
199ms polkit.service
197ms smartmontools.service
183ms rsyslog.service
173ms ubuntu-system-adjustments.service
169ms systemd-udev-trigger.service
156ms user@1000.service
155ms proc-sys-fs-binfmt_misc.mount
146ms ModemManager.service
132ms apparmor.service
123ms avahi-daemon.service
121ms bluetooth.service
114ms grub-common.service
111ms lm-sensors.service
106ms switcheroo-control.service
105ms secureboot-db.service
I use Ubuntu 18.04 LTS, dual-booted with Win10. Whenever I boot the system, it takes ~3 minutes. Also before the login screen, this thing comes up of which I am attaching a screenshot. What does...Ask Ubuntu
On my last computer I found that the boot process was looking for things that weren't there but that the motherboard had rudimentary functionality for like a floppy drive. It didn't even have a connector for one.
For whatever reason, that caused a 10-30 second delay while the kernel tried to determine if there was a floppy drive connected. Pretty sure I had everything disabled via the BIOS but apparently it wasn't disabled enough and the kernel could still see it.
That required throwing something into the system config, probably somewhere in /etc/modprobe.d, to blacklist that particular kernel module.
There was another problematic module as well; I can't remember what that was, but I'm pretty sure it was the same fix. Got the boot time to login screen down to less than 10 seconds.
But all that said, even on this computer where the boot time is pretty quick, I usually put the computer into suspend mode to keep times down.
Mint uses systemd, so just use it;
systemd-analyze/systemd-analyze blame.You can also visualize it;