budgies takes forever and a day when booting up…any suggestions
systemd-analyze blame so that everyone can see what is being loaded at boot and more importantly which element is taking the time during the boot.
How big is your root partition? Maybe taking a very long time to check it?
Mine boots in under 40 seconds, installed on an 11 GB ssd partition. systemd-analyze blame is
5.161s dev-mmcblk0p4.device 4.467s NetworkManager-wait-online.service 3.164s snapd.service 2.509s plymouth-read-write.service 2.328s dev-loop0.device 2.318s dev-loop1.device 2.311s dev-loop2.device 2.237s dev-loop3.device 2.209s systemd-logind.service 2.107s e2scrub_reap.service 1.857s lightdm.service 1.837s plymouth-quit-wait.service 1.797s upower.service 1.453s udisks2.service 1.439s networkd-dispatcher.service 1.315s ModemManager.service 1.162s accounts-daemon.service 1.153s systemd-resolved.service 1.130s systemd-timesyncd.service 1.113s systemd-journald.service 1.089s systemd-rfkill.service 852ms avahi-daemon.service 809ms bluetooth.service 780ms wpa_supplicant.service 737ms rsyslog.service 667ms NetworkManager.service 570ms keyboard-setup.service 537ms apparmor.service 522ms systemd-udev-trigger.service 512ms systemd-backlight@backlight:intel_backlight.service 502ms lm-sensors.service 500ms apport.service 478ms pppd-dns.service 459ms grub-initrd-fallback.service 451ms secureboot-db.service 399ms gpu-manager.service 384ms grub-common.service 347ms email@example.com 233ms polkit.service 216ms systemd-udevd.service 192ms systemd-journal-flush.service 142ms snapd.seeded.service 127ms snap-ubuntu\x2dbudgie\x2dwelcome-145.mount 124ms kerneloops.service 121ms colord.service 119ms sys-kernel-debug.mount 117ms ufw.service 116ms snap-core-8268.mount 116ms kmod-static-nodes.service 110ms dev-hugepages.mount 106ms snap-core-7917.mount 105ms systemd-fsck@dev-disk-by\x2duuid-9472\x2d61A6.service 98ms systemd-modules-load.service 98ms systemd-remount-fs.service 95ms swapfile.swap 94ms dev-mqueue.mount 91ms systemd-sysctl.service 89ms snap-ubuntu\x2dbudgie\x2dwelcome-156.mount 80ms systemd-update-utmp-runlevel.service 73ms systemd-tmpfiles-setup.service 71ms hddtemp.service 67ms systemd-update-utmp.service 62ms console-setup.service 61ms plymouth-start.service 56ms systemd-sysusers.service 56ms boot-efi.mount 52ms firstname.lastname@example.org 49ms systemd-tmpfiles-setup-dev.service 49ms systemd-random-seed.service 47ms sys-fs-fuse-connections.mount 46ms systemd-user-sessions.service 46ms sys-kernel-config.mount 24ms rtkit-daemon.service 18ms snapd.socket 14ms setvtrgb.service
Do I need snap?
I think I have only one partion…I let the system config it,all I did was click on the /…and let it do its thing…should I reinstall,and if so…how should I have it partition up…its a 80 gb hard drive
Let’s first have a look at what is slowing down your boot. Please run the systemd command I requested.
80GB shouldn’t take very long to check on boot, no need to re-install just yet. Usually a slow boot is down to just one or two problems.
glynn@glynn-System-Product-Name:~$ systemd-analyze blame
29.665s dev-sdd1.device 24.461s snapd.service 14.548s accounts-daemon.service 14.170s ModemManager.service 14.061s udisks2.service 12.739s networkd-dispatcher.service 10.454s systemd-journal-flush.service 10.368s lightdm.service 10.365s plymouth-quit-wait.service 8.996s NetworkManager-wait-online.service 8.715s grub-common.service 8.488s nmbd.service 8.369s e2scrub_reap.service 8.233s lm-sensors.service 8.115s apport.service 8.026s grub-initrd-fallback.service 7.909s dev-loop7.device 7.882s NetworkManager.service 7.651s systemd-logind.service 7.560s rsyslog.service 7.524s wpa_supplicant.service 7.519s thermald.service 7.399s dev-loop5.device 7.339s email@example.com 7.335s dev-loop10.device 7.188s gpu-manager.service 7.065s apt-daily.service 6.886s dev-loop1.device 6.526s dev-loop9.device 6.462s dev-loop8.device 6.294s dev-loop3.device 6.112s dev-loop2.device 6.000s dev-loop6.device 5.876s dev-loop4.device 5.705s dev-loop0.device 5.028s systemd-udevd.service 3.443s smbd.service 2.897s apparmor.service 2.896s colord.service 2.712s systemd-resolved.service 1.667s systemd-sysctl.service 1.611s systemd-tmpfiles-setup.service 1.336s polkit.service 1.271s switcheroo-control.service 1.096s systemd-rfkill.service 1.047s plymouth-read-write.service 1.009s systemd-modules-load.service 894ms snap-core-8268.mount 882ms upower.service 838ms keyboard-setup.service 837ms snap-ubuntu\x2dbudgie\x2dwelcome-145.mount 796ms snap-core-7917.mount 747ms systemd-tmpfiles-setup-dev.service 715ms snap-core18-1650.mount 678ms systemd-timesyncd.service 670ms systemd-sysusers.service 600ms plymouth-start.service 595ms firstname.lastname@example.org 560ms pppd-dns.service 531ms snapd.seeded.service 513ms snap-clementine-659.mount 480ms systemd-journald.service 450ms snap-chromium-1005.mount 446ms systemd-user-sessions.service 436ms swapfile.swap 387ms ufw.service 382ms systemd-udev-trigger.service 358ms snap-gtk\x2dcommon\x2dthemes-1440.mount 356ms openvpn.service 239ms console-setup.service 238ms snapd.socket 235ms systemd-random-seed.service 219ms snap-epiphany-53.mount 183ms setvtrgb.service 171ms kerneloops.service 162ms kmod-static-nodes.service 142ms systemd-remount-fs.service 137ms snap-core18-1668.mount 120ms fwupd.service 110ms snap-gnome\x2d3\x2d28\x2d1804-116.mount 106ms snap-ubuntu\x2dbudgie\x2dwelcome-156.mount 105ms rtkit-daemon.service 95ms dev-mqueue.mount 94ms sys-kernel-debug.mount 82ms bolt.service 78ms hddtemp.service 77ms systemd-update-utmp.service 59ms dev-hugepages.mount 49ms systemd-tmpfiles-clean.service 27ms email@example.com 11ms systemd-update-utmp-runlevel.service 7ms avahi-daemon.service 2ms sys-kernel-config.mount 2ms sys-fs-fuse-connections.mount
Hmm… are you fully up to date?
sudo apt update && sudo apt dist-upgrade
What kernel are you using?
What version of ubuntu budgie are you running?
You have several snaps installed … but overall your boot processes are extraordinarily slow. Weird.
That is probably getting scanned by fsck. If that happens each time you boot it could be dying. Do a check yourself from command line to see if it throws any errors.
This one can be disabled:
sudo systemctl mask NetworkManager-wait-online.service
without any side effects unless you run servers that require your network to be up and running during boot. Generally not the case for a desktop.
is related to
“ModemManager is a DBus-activated daemon which controls mobile broadband (2G/3G/4G) devices and connections. Whether built-in devices, USB dongles, bluetooth-paired telephones, or professional RS232/USB devices with external power supplies, ModemManager is able to prepare and configure the modems and setup connections with them.”
Do you have to have it active? If not mask that one too.
sudo systemctl mask ModemManager.service
Both would save you 25s.
plymouth-quit-wait.service and accounts-daemon.service are not an issue: those times are affected by other services (https://www.freedesktop.org/software/systemd/man/systemd.special.html is releated to this)
is another command to use in combination with systemd-analyze blame.
Burning question : How do you even have a 64-bit machine with an 80GB hard drive? Is it an ssd?
80GB HD was normal in 2005, so how has this particular 80GB hard disk ended up in a 64-bit capable machine being used in 2020?
oh it’s on a test hard drive…I use 2 ssd drives 150 and 550 for my everyday use…and when I see a ps to try I use my old 80 gig data drive for testing…if I can get it to work on that,than I can put it on my ssd 150gig drive
Nice. How about this plan -
Don’t bother installing anything on the old 80GB drive. Keep it as spare space for when you need to make 150GB space on your 550GB drive.
Before testing out an install, take an image of the smaller drive, save to the larger drive. Have a functional o/s installed on the second drive so you can use it as the system for imaging the first drive. If you want to make this faster, you can partition the smaller drive and just image the partition you have the system on. If I were you I’d have less than 50GB for the system, the other 100 for home, the 550 drive just for data and backup imaging the system partition.
If you ever don’t have enough room, use the 80GB drive as extra space.
@8ink I am considering adding an SSD to my Asus VivoBook, to make it faster.
Reading your advice to “image” a drive, is this meant to copy the contents, installs and configurations of the Budgie OS to the SSD drive?
Is it possible to copy the OS to the SSD drive, so that I don’t have to install and configure everything again?
You can copy an os to a drive using rsync and some tinkering, but using either gnome-disk-utility or dd https://en.wikipedia.org/wiki/Dd_(Unix) very carefully is the way to go.
Put it this way, I’m currently using an HP stream which came with windows. I first booted it from LMDE on a usb and used dd to take an image of the whole internal 32GB emmc drive and saved it to a 2 TB external HDD.
Very soon I may do this again, to preserve my current dual-boot setup, and go with something else. If I come to sell this laptop, I’ll use dd to put the original windows 10 image back.
Imaging whole drives is easier than partitions but takes more resources.
If you want to image your 80GB setup over to your ssd you can, and just grow the partition into the extra space or add whatever other partitions you need. Keeping it the same size as the original drive makes it handy for using dd to take a backup.
I see what you saying… but my 2 sad drives are windows10 work drives,cant mess with them…so all I have is my old 80gb hd. I had makula on it before it worked fine,and everything seems to be working fine with budgie…just a slow bootup…but if that’s all that’s wrong…I am good with it…thanks for the hlp
It’s Windows. Either you take control of it or it messes with you!
Back up your data, create windows restore disks if you haven’t done so already then reinstall windows every three months minimum and while you’re at it, shrink each of the large windows basic data partitions using gparted to create a few GB of space, make new partitions, install linux on both of them. Use them to keep your windows work data safe.
@Rinzwind I have masked both processes, now I am unable to access the internet.
In the wifi settings it says Device not Ready…
Oops … the reverse of “mask” needs a bit more work
I think we got lost somewhere…he is exactly what do…when I want to try a new os,I remove all my hard drives,except the 80 gig sata…that way I cannot mess up any of my other drives. .so when I boot bodgie…it has only the data drive connected…no windows at all…
unmask them then e
it was not my intention so sorry!
it is probably:
sudo systemctl unmask ModemManager.service
and not …
sudo systemctl unmask NetworkManager-wait-online.service
cuz the 1st one sets up internet for some specific types of connections