Given that I have a PC dated a few years with a mechanical hard disk, I would like to know if there is a way to understand if the boot times are "normal" or if there is some bottleneck on the software side that slows down the execution of the same . Once the OS is loaded, the use of the PC is responsive and fast. I specify that from ignition to the ready system it takes almost 5 min
Thank you
OS: Linux Mint 20 x86_64
Host: T4000 \ C4000
Kernel: 5.4.0-89-generic
DE: Cinnamon
WM: Mutter (Muffin)
WM Theme: Ubuntu-touch (Mint-X)
CPU: Intel Pentium G620 (2) @ 2.600GHz
PU: Intel 2nd Generation Core Processor Famil
Memory: 1572MiB / 3880MiB
long times for booting
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
LUCAFATICHENTI
- Level 1
- Posts: 49
- Joined: Thu Oct 08, 2020 11:50 am
long times for booting
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
-
LUCAFATICHENTI
- Level 1
- Posts: 49
- Joined: Thu Oct 08, 2020 11:50 am
Re: long times for booting
Code: Select all
luca@luca-T4000-C4000:~$ systemd-analyze
Startup finished in 4.823s (kernel) + 56.199s (userspace) = 1min 1.023s
graphical.target reached after 56.179s in userspace
luca@luca-T4000-C4000:~$ systemd-analyze blame
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
lines 1-23...skipping...
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
4.196s dev-loop11.device >
lines 1-24...skipping...
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
4.196s dev-loop11.device >
4.123s lightdm.service >
lines 1-25...skipping...
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
4.196s dev-loop11.device >
4.123s lightdm.service >
4.111s plymouth-quit-wait.service >
lines 1-26...skipping...
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
4.196s dev-loop11.device >
4.123s lightdm.service >
4.111s plymouth-quit-wait.service >
4.037s dev-loop12.device >
lines 1-27...skipping...
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
4.196s dev-loop11.device >
4.123s lightdm.service >
4.111s plymouth-quit-wait.service >
4.037s dev-loop12.device >
3.391s rsyslog.service >
lines 1-28...skipping...
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
4.196s dev-loop11.device >
4.123s lightdm.service >
4.111s plymouth-quit-wait.service >
4.037s dev-loop12.device >
3.391s rsyslog.service >
3.380s colord.service >
lines 1-29...skipping...
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
4.196s dev-loop11.device >
4.123s lightdm.service >
4.111s plymouth-quit-wait.service >
4.037s dev-loop12.device >
3.391s rsyslog.service >
3.380s colord.service >
3.279s teamviewerd.service >
lines 1-30...skipping...
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
4.196s dev-loop11.device >
4.123s lightdm.service >
4.111s plymouth-quit-wait.service >
4.037s dev-loop12.device >
3.391s rsyslog.service >
3.380s colord.service >
3.279s teamviewerd.service >
3.277s apparmor.service >
lines 1-31...skipping...
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
4.196s dev-loop11.device >
4.123s lightdm.service >
4.111s plymouth-quit-wait.service >
4.037s dev-loop12.device >
3.391s rsyslog.service >
3.380s colord.service >
3.279s teamviewerd.service >
3.277s apparmor.service >
3.263s systemd-sysctl.service >
lines 1-32...skipping...
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
4.196s dev-loop11.device >
4.123s lightdm.service >
4.111s plymouth-quit-wait.service >
4.037s dev-loop12.device >
3.391s rsyslog.service >
3.380s colord.service >
3.279s teamviewerd.service >
3.277s apparmor.service >
3.263s systemd-sysctl.service >
3.022s dev-loop4.device >
lines 1-33...skipping...
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
4.196s dev-loop11.device >
4.123s lightdm.service >
4.111s plymouth-quit-wait.service >
4.037s dev-loop12.device >
3.391s rsyslog.service >
3.380s colord.service >
3.279s teamviewerd.service >
3.277s apparmor.service >
3.263s systemd-sysctl.service >
3.022s dev-loop4.device >
3.022s dev-loop3.device >
lines 1-34...skipping...
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
4.196s dev-loop11.device >
4.123s lightdm.service >
4.111s plymouth-quit-wait.service >
4.037s dev-loop12.device >
3.391s rsyslog.service >
3.380s colord.service >
3.279s teamviewerd.service >
3.277s apparmor.service >
3.263s systemd-sysctl.service >
3.022s dev-loop4.device >
3.022s dev-loop3.device >
3.021s dev-loop7.device >
lines 1-35...skipping...
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
4.196s dev-loop11.device >
4.123s lightdm.service >
4.111s plymouth-quit-wait.service >
4.037s dev-loop12.device >
3.391s rsyslog.service >
3.380s colord.service >
3.279s teamviewerd.service >
3.277s apparmor.service >
3.263s systemd-sysctl.service >
3.022s dev-loop4.device >
3.022s dev-loop3.device >
3.021s dev-loop7.device >
2.783s e2scrub_reap.service >
lines 1-36...skipping...
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
4.196s dev-loop11.device >
4.123s lightdm.service >
4.111s plymouth-quit-wait.service >
4.037s dev-loop12.device >
3.391s rsyslog.service >
3.380s colord.service >
3.279s teamviewerd.service >
3.277s apparmor.service >
3.263s systemd-sysctl.service >
3.022s dev-loop4.device >
3.022s dev-loop3.device >
3.021s dev-loop7.device >
2.783s e2scrub_reap.service >
2.746s grub-common.service >
lines 1-37...skipping...
26.662s snapd.service >
19.875s accounts-daemon.service >
18.652s udisks2.service >
17.434s NetworkManager-wait-online.service >
17.149s networkd-dispatcher.service >
14.476s dev-sdb2.device >
10.447s NetworkManager.service >
10.378s ModemManager.service >
10.340s avahi-daemon.service >
10.284s polkit.service >
9.911s thermald.service >
9.769s systemd-logind.service >
9.764s wpa_supplicant.service >
7.149s ubuntu-system-adjustments.service >
5.428s gpu-manager.service >
4.904s systemd-journal-flush.service >
4.798s dev-loop8.device >
4.721s dev-loop9.device >
4.244s dev-loop5.device >
4.243s dev-loop0.device >
4.243s dev-loop2.device >
4.242s dev-loop10.device >
4.242s dev-loop6.device >
4.196s dev-loop11.device >
4.123s lightdm.service >
4.111s plymouth-quit-wait.service >
4.037s dev-loop12.device >
3.391s rsyslog.service >
3.380s colord.service >
3.279s teamviewerd.service >
3.277s apparmor.service >
3.263s systemd-sysctl.service >
3.022s dev-loop4.device >
3.022s dev-loop3.device >
3.021s dev-loop7.device >
2.783s e2scrub_reap.service >
2.746s grub-common.service >
2.110s snap-bare-5.mount >
1.987s snap-chromium-1801.mount >
1.928s networking.service >
1.913s dev-loop1.device >
1.899s snap-chromium-1810.mount >
1.837s systemd-resolved.service >
1.675s snap-core18-2128.mount >
1.633s snap-core18-2246.mount >
1.623s snapd.seeded.service >
1.580s systemd-modules-load.service >
1.563s snap-gnome\x2d3\x2d28\x2d1804-145.mount >
1.524s snap-gnome\x2d3\x2d28\x2d1804-161.mount >
1.504s ctxlogd.service >
1.226s snap-gtk\x2dcommon\x2dthemes-1515.mount >
1.203s snap-gtk\x2dcommon\x2dthemes-1519.mount >
1.174s systemd-tmpfiles-setup-dev.service >
994ms systemd-sysusers.service >
993ms systemd-udevd.service >
979ms systemd-tmpfiles-setup.service >
975ms systemd-random-seed.service >
973ms upower.service >
961ms systemd-user-sessions.service >
955ms keyboard-setup.service >
904ms grub-initrd-fallback.service >
887ms snapd.apparmor.service >
855ms dns-clean.service >
839ms systemd-udev-trigger.service >
752ms alsa-restore.service >
731ms swapfile.swap >
651ms lm-sensors.service >
563ms ua-timer.service >
391ms systemd-timesyncd.service >
380ms ifupdown-pre.service >
337ms systemd-journald.service >
324ms setvtrgb.service >
309ms snap-losslesscut-72.mount >
286ms dev-hugepages.mount >
286ms dev-mqueue.mount >
284ms sys-kernel-debug.mount >
283ms sys-kernel-tracing.mount >
282ms blk-availability.service >
278ms systemd-hostnamed.service >
276ms kmod-static-nodes.service >
273ms lvm2-monitor.service >
272ms ufw.service >
266ms kerneloops.service >
243ms systemd-rfkill.service >
224ms snap-losslesscut-77.mount >
215ms snap-snapd-13831.mount >
208ms user@1000.service >
192ms hddtemp.service >
166ms pppd-dns.service >
165ms systemd-fsck@dev-disk-by\x2duuid-228A\x2dC91C.>
161ms snap-snapd-13640.mount >
161ms systemd-remount-fs.service >
146ms console-setup.service >
104ms systemd-update-utmp.service >
72ms rtkit-daemon.service >
40ms systemd-tmpfiles-clean.service >
35ms boot-efi.mount >
22ms user-runtime-dir@1000.service >
17ms systemd-update-utmp-runlevel.service >
16ms plymouth-start.service >
14ms plymouth-read-write.service >
9ms finalrd.service >
7ms sys-kernel-config.mount >
7ms openvpn.service >
4ms sys-fs-fuse-connections.mount >
922us snapd.socket >
lines 69-106/106 (END)-
LUCAFATICHENTI
- Level 1
- Posts: 49
- Joined: Thu Oct 08, 2020 11:50 am
Re: long times for booting
Code: Select all
luca@luca-T4000-C4000:~$ systemd-analyze critical-chain
The time when unit became active or started is printed>
The time the unit took to start is printed after the ">
graphical.target @56.179s
└─multi-user.target @56.178s
└─teamviewerd.service @52.898s +3.279s
└─network-online.target @52.734s
└─NetworkManager-wait-online.service @35.299s +1>
└─NetworkManager.service @24.850s +10.447s
└─dbus.service @24.843s
└─basic.target @24.662s
└─sockets.target @24.662s
└─snapd.socket @24.661s +922us
└─sysinit.target @24.441s
└─snapd.apparmor.service @23.553s >
└─apparmor.service @20.273s +3.2>
└─local-fs.target @20.272s
└─boot-efi.mount @20.236s +3>
└─systemd-fsck@dev-disk-by>
└─dev-disk-by\x2duuid-22>
lines 1-20/20 (END)-
LUCAFATICHENTI
- Level 1
- Posts: 49
- Joined: Thu Oct 08, 2020 11:50 am
Re: long times for booting
Code: Select all
Startup finished in 4.823s (kernel) + 56.199s (userspace) = 1min 1.023s
graphical.target reached after 56.179s in userspace-
Larry78723
- Level 14
- Posts: 5476
- Joined: Wed Jan 09, 2019 7:01 pm
- Location: Jasper County, SC, USA
Re: long times for booting
Please post an
Here is how to generate the report and post it:
Boot from your installation media (USB/DVD)
Open a terminal window (Ctrl-Alt-t). Make it fullscreen to avoid unneeded linebreaks or chopped lines. Copy the following code and paste into the terminal (Ctrl-Shft-V) then hit Enter/Return:
exactly as it has been typed here.
Go to Edit, Select All, and then Copy, come back here, click on reply then code tags, </>, and then paste.
The results will help us to help you.
inxi -Fxpmzr report. This will give us a concise overview of your hardware and how Mint sees it per How to get help . Here is how to generate the report and post it:
Boot from your installation media (USB/DVD)
Open a terminal window (Ctrl-Alt-t). Make it fullscreen to avoid unneeded linebreaks or chopped lines. Copy the following code and paste into the terminal (Ctrl-Shft-V) then hit Enter/Return:
Code: Select all
inxi -Fxpmrz Go to Edit, Select All, and then Copy, come back here, click on reply then code tags, </>, and then paste.
The results will help us to help you.
If you have found the solution to your initial post, please open your original post, click on the pencil, and add (Solved) to the Subject, it helps other users looking for help, and keeps the forum clean.
-
SimonPeter
- Level 5
- Posts: 579
- Joined: Tue Jul 13, 2021 5:13 am
Re: long times for booting
Please run the command
cat /etc/fstab and post its output (with personal information redacted).-
LUCAFATICHENTI
- Level 1
- Posts: 49
- Joined: Thu Oct 08, 2020 11:50 am
Re: long times for booting
Code: Select all
/etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdb2 during installation
UUID=1e773a72-fe3d-48ef-9a7e-60842284b272 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sdb1 during installation
UUID=228A-C91C /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
-
LUCAFATICHENTI
- Level 1
- Posts: 49
- Joined: Thu Oct 08, 2020 11:50 am
Re: long times for booting
Code: Select all
Kernel: 5.4.0-90-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 4.6.7 Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal
Machine: Type: N/A System: Olidata S.p.A. product: T4000 \ C4000 v: N/A serial: <filter>
Mobo: Foxconn model: H67MP-S/-V/H67MP serial: <filter> UEFI: American Megatrends
v: A4BO2S01 date: 01/04/2012
Memory: RAM: total: 3.79 GiB used: 1.22 GiB (32.2%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU: Topology: Dual Core model: Intel Pentium G620 bits: 64 type: MCP
arch: Sandy Bridge rev: 7 L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 10376
Speed: 1596 MHz min/max: 1600/2600 MHz Core speeds (MHz): 1: 1643 2: 1686
Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
vendor: Foxconn driver: i915 v: kernel bus ID: 00:02.0
Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 2000 (SNB GT1) v: 3.3 Mesa 21.0.3
direct render: Yes
Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Foxconn
driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Sound Server: ALSA v: k5.4.0-90-generic
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Foxconn
driver: r8169 v: kernel port: e000 bus ID: 02:00.0
IF: enp2s0 state: down mac: <filter>
Device-2: Realtek type: USB driver: rtl88x2bu bus ID: 1-1.4:3
IF: wlx4401bb91f363 state: up mac: <filter>
Drives: Local Storage: total: 465.77 GiB used: 56.90 GiB (12.2%)
ID-1: /dev/sda vendor: Western Digital model: WD2500AAKX-001CA0 size: 232.89 GiB
ID-2: /dev/sdb vendor: Western Digital model: WD2500AAKX-001CA0 size: 232.89 GiB
RAID: Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 bus ID: 00:1f.2
Partition: ID-1: / size: 228.14 GiB used: 56.90 GiB (24.9%) fs: ext4 dev: /dev/sdb2
ID-2: /boot/efi size: 92.5 MiB used: 5.2 MiB (5.6%) fs: vfat dev: /dev/sdb1
Sensors: System Temperatures: cpu: 38.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list
1: deb https://dl.winehq.org/wine-builds/ubuntu/ focal main
No active apt repos in: /etc/apt/sources.list.d/atareao-telegram-focal.list
Active apt repos in: /etc/apt/sources.list.d/dawidd0811-neofetch-focal.list
1: deb http://ppa.launchpad.net/dawidd0811/neofetch/ubuntu focal main
Active apt repos in: /etc/apt/sources.list.d/gezakovacs-ppa-focal.list
1: deb http://ppa.launchpad.net/gezakovacs/ppa/ubuntu focal main
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
No active apt repos in: /etc/apt/sources.list.d/home:gottcode.list
No active apt repos in: /etc/apt/sources.list.d/home:llamaret.list
Active apt repos in: /etc/apt/sources.list.d/jstaf-onedriver-focal.list
1: deb http://ppa.launchpad.net/jstaf/onedriver/ubuntu focal main
Active apt repos in: /etc/apt/sources.list.d/mkusb-ppa-focal.list
1: deb http://ppa.launchpad.net/mkusb/ppa/ubuntu focal main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb https://mirror.init7.net/linuxmint ulyana main upstream import backport
2: deb http://ubuntu.anexia.at/ubuntu focal main restricted universe multiverse
3: deb http://ubuntu.anexia.at/ubuntu focal-updates main restricted universe multiverse
4: deb http://ubuntu.anexia.at/ubuntu focal-backports main restricted universe multiverse
5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
6: deb http://archive.canonical.com/ubuntu/ focal partner
Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list
1: deb [arch=amd64] https://updates.signal.org/desktop/apt xenial main
Active apt repos in: /etc/apt/sources.list.d/stebbins-handbrake-releases-focal.list
1: deb http://ppa.launchpad.net/stebbins/handbrake-releases/ubuntu focal main
Active apt repos in: /etc/apt/sources.list.d/teams.list
1: deb [arch=amd64] https://packages.microsoft.com/repos/ms-teams stable main
Active apt repos in: /etc/apt/sources.list.d/teamviewer.list
1: deb https://linux.teamviewer.com/deb stable main
No active apt repos in: /etc/apt/sources.list.d/trendtechcn.list
Info: Processes: 211 Uptime: 7m Init: systemd runlevel: 5 Compilers: gcc: 9.3.0
Shell: bash v: 5.0.17 inxi: 3.0.38-
LUCAFATICHENTI
- Level 1
- Posts: 49
- Joined: Thu Oct 08, 2020 11:50 am
Re: long times for booting
Trying to get Larry to come back here.Please post an inxi -Fxpmzr report.
Sorry we are not getting back to you in a timely manner.
4+ minute boot time is totally unreasonable. I would expect about 1 min with a spinning disk.
I don't see anything obviously wrong with your inxi report, although there are some interesting things in there.
Sure your system is a bit old and weak, but LM should work good on that machine IMO.
I say we start turning off applications in "Startup Applications", which is in the menu. Start by turning off MS Teams if you have that on.
Here is my "Startup Applications":
-
SimonPeter
- Level 5
- Posts: 579
- Joined: Tue Jul 13, 2021 5:13 am
Re: long times for booting
You may also turn these off:
1) mintwelcome (you can access it from the menu when you need it).
2) System Reports (you can access it from the menu when you need it).
3) Update Manager (remember to frequently check for updates manually, say once in a week).
4) Flatpak updates -- if you don't use Flatpak.
5) Everything related to NVIDIA (NVIDIA Prime, NVIDIA X Server Settings etc.,) -- if you don't use NVIDIA hardware.
BTW I don't know why #1 & #2 aren't disabled in the autostart menu (by default), even after their first run.
1) mintwelcome (you can access it from the menu when you need it).
2) System Reports (you can access it from the menu when you need it).
3) Update Manager (remember to frequently check for updates manually, say once in a week).
4) Flatpak updates -- if you don't use Flatpak.
5) Everything related to NVIDIA (NVIDIA Prime, NVIDIA X Server Settings etc.,) -- if you don't use NVIDIA hardware.
BTW I don't know why #1 & #2 aren't disabled in the autostart menu (by default), even after their first run.
Re: long times for booting
They've never auto-disabled on first run for me ( or specifically even after the first reboot) I've always had to disable them when I wanted them disabled. *shrugs*..no big deal to me though.BTW I don't know why #1 & #2 aren't disabled in the autostart menu (by default), even after their first run
Mint 21.2 Cinnamon 5.8.4
asrock x570 taichi ...bios p5.00
ryzen 5900x
128GB Kingston Fury @ 3600mhz
Corsair mp600 pro xt NVME ssd 4TB
three 4TB ssds
dual 1TB ssds
Two 16TB Toshiba hdd's
24GB amd 7900xtx vid card
Viewsonic Elite UHD 32" 144hz monitor
asrock x570 taichi ...bios p5.00
ryzen 5900x
128GB Kingston Fury @ 3600mhz
Corsair mp600 pro xt NVME ssd 4TB
three 4TB ssds
dual 1TB ssds
Two 16TB Toshiba hdd's
24GB amd 7900xtx vid card
Viewsonic Elite UHD 32" 144hz monitor