Solved REALLY, REALLY Slow start up. What to do???

Solved issue
I closed Firefox and tried again. Any bookmark I clicked on opened in another tab that I couldn't switch to.
Do you maybe have a ctrl key that's stuck? That would open a clicked bookmark in a new tab (in firefox) and prevent switching to the new tab.
 


Do you maybe have a ctrl key that's stuck? That would open a clicked bookmark in a new tab (in firefox) and prevent switching to the new tab.
Hmm. Let me check. I did see a few crumb looking things between the keys a couple of days ago when I was cleaning up the tower....

Hold on
 
turn off nvidia.....not needed

in the figures below the first 4 take up a minute

I need to mull about this

-----------------------------------------------
22.741s networkd-dispatcher.service
19.041s udisks2.service
16.022s systemd-journal-flush.service
14.056s ubuntu-system-adjustments.service
13.569s ModemManager.service
13.177s systemd-udev-settle.service
13.158s NetworkManager-wait-online.service
10.109s accounts-daemon.service
9.412s dev-sdb3.device
8.290s polkit.service
7.401s avahi-daemon.service
7.399s bluetooth.service
7.074s switcheroo-control.service
7.071s thermald.service
7.069s wpa_supplicant.service
7.069s systemd-logind.service
7.065s NetworkManager.service
5.224s cups.service
4.998s gpu-manager.service
4.834s systemd-udevd.service
4.374s rsyslog.service
3.805s networking.service
3.653s e2scrub_reap.service
3.259s ufw.service
2.944s lm-sensors.service
2.889s apparmor.service
2.739s lightdm.service
2.736s plymouth-quit-wait.service
2.514s zfs-load-module.service
2.322s grub-common.service
2.248s secureboot-db.service
1.706s systemd-fsck@dev-disk-by\x2duuid-BD0E\x2d843D.service
1.509s systemd-modules-load.service
1.379s systemd-tmpfiles-setup-dev.service
1.178s systemd-resolved.service
1.093s systemd-tmpfiles-setup.service
1.049s plymouth-start.service
1.000s colord.service
958ms systemd-sysusers.service
943ms systemd-sysctl.service
870ms systemd-udev-trigger.service
793ms systemd-random-seed.service
749ms keyboard-setup.service
733ms grub-initrd-fallback.service
604ms swapfile.swap
547ms upower.service
462ms systemd-binfmt.service
400ms boot-efi.mount
372ms systemd-rfkill.service
287ms lvm2-monitor.service
281ms systemd-journald.service
270ms setvtrgb.service
269ms systemd-update-utmp.service
268ms zfs-volume-wait.service
250ms ifupdown-pre.service
222ms systemd-timesyncd.service
191ms dns-clean.service
186ms packagekit.service
185ms kerneloops.service
145ms systemd-remount-fs.service
137ms console-setup.service
130ms zfs-mount.service
123ms dev-hugepages.mount
123ms dev-mqueue.mount
122ms sys-kernel-debug.mount
122ms sys-kernel-tracing.mount
119ms kmod-static-nodes.service
118ms [email protected]
118ms [email protected]
116ms [email protected]
114ms systemd-tmpfiles-clean.service
110ms plymouth-read-write.service
101ms proc-sys-fs-binfmt_misc.mount
100ms [email protected]
97ms finalrd.service
95ms blueman-mechanism.service
85ms rtkit-daemon.service
41ms systemd-user-sessions.service
9ms alsa-restore.service
8ms zfs-share.service
5ms [email protected]
5ms systemd-update-utmp-runlevel.service
2ms openvpn.service
2ms modprobe@efi_pstore.service
1ms sys-fs-fuse-connections.mount
1ms sys-kernel-config.mount
667us nordvpnd.socket
24us blk-availability.service
 
Chris's advice is good..follow that...carefully

in the meantime.......which Linux is on your pc ?...version
 
On cleanup tools, take a look here at the first one mentioned, it is Stacer - it gets a lot of good feedback, but I have not had to use it myself ... as always, Timeshift first, you know that without saying (so I said it)

https://www.tecmint.com/free-disk-space-ubuntu-linux-mint/

I'm going to wait on this while he thinks on that

turn off nvidia.....not needed

in the figures below the first 4 take up a minute

I need to mull about this
 
Bong, bong x 12 midnight, Ohio. Lol.
 
When you initially started using that pc, just in the last x number of days.....was it really really slow from the start ?

and which Linux are you using ?
 
22.1
 
When you initially started using that pc, just in the last x number of days.....was it really really slow from the start ?

I don't know if it was slow. That seems strange...

It took several hours to finish getting all the updates
and which Linux are you using ?
1743566783753.png
 
The first ten on my pc are :

6.048s NetworkManager-wait-online.service
1.986s zfs-load-module.service
1.351s systemd-udev-settle.service
984ms mnt-wwn\x2d0x50014ee2bd7c71cf\x2dpart3.mount
812ms NetworkManager.service
682ms smartmontools.service
359ms dev-nvme0n1p2.device
351ms udisks2.service
305ms blueman-mechanism.service
214ms ufw.service

The first ten on your pc are :

22.741s networkd-dispatcher.service
19.041s udisks2.service
16.022s systemd-journal-flush.service
14.056s ubuntu-system-adjustments.service
13.569s ModemManager.service
13.177s systemd-udev-settle.service
13.158s NetworkManager-wait-online.service
10.109s accounts-daemon.service
9.412s dev-sdb3.device
8.290s polkit.service
 
Last edited:
Give Stacer a go.

It will be worth seeing the result

Do you have data on the pc that needs saving ?
 
Also, a hard drive check could be a good idea

In software manager: Gsmartcontrol

Install that on the usb stick that you have for Mint 21.3
So, boot the usb stcik you have with Mint 21.3 on it.....go to menu/Software Manager...type in the above gsmart etc...install it

Type its name into the menu.....click on it to open it....the initial window will look similar to the below;

1743568452321.png


ignore the name on there....they are on my pc.

Choose the name of the drive that is in your pc....the one that mint 21.3 is on...

Double click it...it will open to look like the below

1743568574040.png


SELF TESTS....in the middle...click on that

You can opt for SHort Self test...takes around 60 seconds....or the extended Slef test...takes around 2 minutes
I usually run both.....Just for comparisons sake

On my spare ssd here, the result below on the short test
2025-04-02_15-29.png
 
21.3

That makes a difference

How do yu feel about this :


Just a note, that will update Sherri's "Virginia" to "Wilma" but she will have to then perform another upgrade if she wishes to get to "Xia" 22.1. The "Wilma" update Manager will provide an option to do so.

Only point release upgrades can skip versions. For example if one installs LM22, then can wait until LM22.3 is released and upgrade straight from LM22 to LM22.3 without having to upgrade through LM22.1 and LM22.2.

Wiz (bye, night Sherri, I'm off to wreak havoc on another project)
 


Follow Linux.org

Members online


Top