What are your tips for faster boots? My system seems to hang a bit at POST until it boots into Mint. Right after post I’ll get a blinking cursor for about a full minute until it boots in. All ssd, so I know it’s something I must have done wrong. It’s also a 14 year old processor (amd fx be 8 core, rx580), but win### booted faster on it.
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?
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.service
Are you positive you mean during POST? Like when you see your motherboard details and such?
It varies wildly from board to board, but if you don’t already know what you’re flipping around in there, I wouldn’t mess with it. You can try disabling certain tests like memory or components checks if everything seems fine operationally.
If it is the OS, you could try “systemd-analyze” and “systemd-analyze blame” on the terminal to see what is going on, you can post the output of blame here and maybe someone can pinpoint something strange, or you can search online how to speed up or disable certain elements from the list.
I am going to guess its getting the network up and going. You should be able to hit escape on the screen and see where the boot is in its process. Getting the networking going during boot is something a lot of linux installs will do as most enterprise/devs (tbh the biggest part of their audience) have network attached storage. I have never looked into getting it just to move on past it (it will still start the process for getting networking online, it just shouldnt pause) I know that some fedora installs I have had in the past did this.
But boot it again and hit escape and get more info and if it something else post again here maybe we can help better.