Hi, im new to Manjaro and Linux. I recently partitioned 100gb of my 1tb hard drive for Manjaro KDE Plasma. Everything runs fine once booted but the OS takes 2-4 minutes on average to boot. Would getting a new ssd fix this? Sorry if this sounds stupid, I’ve just seen some posts having slow boot times on ssd as well.
Right, not a stupid question.
With SSD I can install an OS from USB in about 6 minutes, and boot in maybe 8 seconds after BIOS.
With HDD it takes forever and a few coffees.
Opening GIMP with brushes etc takes 1.5 seconds from SSD, but much much longer with HDD.
There’s no question that an SSD would be so much better here - the only question is whether you can fix your issue with a fresh install as 2-4 minutes is still a little long and indicates some of your problems might be separate from your slow HDD issue.
Start with a terminal, open it and type systemd-analyze blame
Type three backticks (on the ~ ` key) and paste.
like this:
systemd-analyze blame
13.223s updatedb.service
1.681s man-db.service
1.560s lvm2-monitor.service
1.147s systemd-random-seed.service
956ms systemd-tmpfiles-clean.service
809ms mnt-W2.mount
482ms upower.service
450ms dev-sda2.device
399ms cups.service
398ms var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-145.mount
392ms var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1514.mount
392ms var-lib-snapd-snap-snapd-10707.mount
380ms var-lib-snapd-snap-gnome\x2d3\x2d34\x2d1804-60.mount
368ms var-lib-snapd-snap-core18-1944.mount
367ms var-lib-snapd-snap-gnome\x2d3\x2d34\x2d1804-66.mount
366ms var-lib-snapd-snap-snapd-11036.mount
364ms var-lib-snapd-snap-core18-1988.mount
338ms snapd.service
337ms swapfile.swap
264ms tlp.service
243ms polkit.service
134ms avahi-daemon.service
132ms systemd-modules-load.service
129ms user@1000.service
128ms NetworkManager.service
120ms systemd-journald.service
111ms logrotate.service
110ms ModemManager.service
110ms dev-loop1.device
109ms systemd-logind.service
109ms lm_sensors.service
105ms systemd-udevd.service
103ms udisks2.service
99ms mnt-T3.mount
97ms systemd-udev-trigger.service
91ms accounts-daemon.service
81ms pkgfile-update.service
66ms systemd-timesyncd.service
64ms mnt-T4.mount
61ms modprobe@drm.service
57ms dev-loop0.device
45ms systemd-tmpfiles-setup-dev.service
44ms systemd-binfmt.service
43ms systemd-journal-flush.service
40ms colord.service
37ms mnt-SSD.mount
37ms dev-loop5.device
34ms dev-hugepages.mount
34ms dev-mqueue.mount
33ms sys-kernel-debug.mount
32ms sys-kernel-tracing.mount
32ms kmod-static-nodes.service
30ms modprobe@configfs.service
29ms modprobe@fuse.service
lines 1-54
This is what i got:
21.227s udisks2.service
10.858s tlp.service
6.505s lvm2-monitor.service
5.709s snapd.service
4.992s systemd-modules-load.service
4.839s dev-sdb5.device
3.330s systemd-journal-flush.service
3.105s polkit.service
2.823s cups.service
2.618s ModemManager.service
2.294s systemd-tmpfiles-setup-dev.service
1.856s apparmor.service
1.710s avahi-daemon.service
1.704s NetworkManager.service
1.669s systemd-logind.service
1.224s systemd-udevd.service
808ms user@1000.service
571ms systemd-fsck-root.service
571ms upower.service
461ms systemd-random-seed.service
438ms var-lib-snapd-snap-core-10823.mount
423ms snapd.apparmor.service
420ms accounts-daemon.service
401ms var-lib-snapd-snap-code-55.mount
312ms modprobe@fuse.service
266ms systemd-tmpfiles-setup.service
260ms systemd-sysctl.service
Also my boot time has shortened to around 2 minutes now that I’ve disabled some startup settings
Ok, now for SSD…
compare my 338ms snapd.service to your 5.709s snapd.service
16 times faster.
I’d be wondering why you’ve 21.227s on the udisks2.service next. Maybe you have some funky mounting options going on…
Can you post the hardware info of your computer?
Gpu: GTX 1660ti
Cpu: Ryzen 7 2700
Ram:16gb 2666mhz
Motherboard:Asus Rog Strix B450m
Then you should buy a SSD (SATA or NVME).
1 Like
Yes, please get a SSD as soon as possible… You will be so happy and wonder why you didn’t do it sooner.
You can get a crucial BX500 120GB SSD online for like $30 or a cheaper kingston for $25… Just use the SSD for your /boot & /root then put your /home on HDD…
Hey I’m facing the same problem, but my systemd-analyze blame outputs are different. Any suggestions on what should I do (apart from the obvious “get an SSD”).
28.606s man-db.service
15.295s pkgfile-update.service
13.839s systemd-journal-flush.service
9.166s lvm2-monitor.service
9.109s snapd.service
6.329s polkit.service
5.819s pamac-cleancache.service
5.641s dev-sda5.device
3.850s avahi-daemon.service
3.848s bluetooth.service
3.838s NetworkManager.service
3.802s systemd-machined.service
3.801s systemd-logind.service
3.419s systemd-modules-load.service
2.294s systemd-udevd.service
2.070s systemd-fsck@dev-disk-by\x2duuid-6343ecdf\x2dc07a\x2d4a9d\x2d9e20\x2db6790f4ac652.service
1.858s apparmor.service
1.831s tlp.service
1.516s ModemManager.service
1.239s systemd-tmpfiles-setup-dev.service
1.192s dev-loop4.device
1.166s dev-loop2.device
1.013s snapd.apparmor.service
1.010s var-lib-snapd-snap-snapd-11588.mount
998ms var-lib-snapd-snap-core-10958.mount
989ms dev-loop8.device
972ms dev-loop10.device
938ms dev-loop9.device
919ms dev-loop1.device
884ms var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1514.mount
875ms dev-loop6.device
858ms dev-loop5.device
857ms udisks2.service
731ms var-lib-snapd-snap-simplenote-519.mount
728ms dev-loop7.device
652ms var-lib-snapd-snap-core18-1997.mount
651ms var-lib-snapd-snap-spotify-46.mount
648ms user@1000.service
582ms dev-loop0.device
567ms var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-145.mount
556ms wpa_supplicant.service
524ms var-lib-snapd-snap-snapd-11402.mount
509ms systemd-tmpfiles-setup.service
494ms var-lib-snapd-snap-simplenote-524.mount
477ms var-lib-snapd-snap-core18-1988.mount
445ms var-lib-snapd-snap-spotify-43.mount
436ms upower.service
433ms logrotate.service
386ms var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1515.mount
366ms linux-module-cleanup.service
359ms systemd-rfkill.service
344ms boot-efi.mount
340ms dev-loop11.device
325ms systemd-udev-trigger.service
302ms systemd-random-seed.service
297ms dev-sda4.swap
247ms kmod-static-nodes.service
246ms modprobe@fuse.service
245ms modprobe@drm.service
232ms systemd-sysctl.service
229ms systemd-fsck@dev-disk-by\x2duuid-C6FD\x2d5E16.service
220ms systemd-binfmt.service
176ms systemd-timesyncd.service
165ms rtkit-daemon.service
151ms NetworkManager-wait-online.service
150ms systemd-tmpfiles-clean.service
149ms systemd-journald.service
134ms systemd-backlight@backlight:intel_backlight.service
90ms dev-hugepages.mount
89ms dev-mqueue.mount
88ms sys-kernel-debug.mount
87ms sys-kernel-tracing.mount
83ms modprobe@configfs.service
81ms home.mount
68ms systemd-update-utmp.service
37ms systemd-remount-fs.service
29ms user-runtime-dir@1000.service
28ms systemd-user-sessions.service
6ms sys-fs-fuse-connections.mount
2ms proc-sys-fs-binfmt_misc.mount
2ms snapd.socket
2ms tmp.mount
2ms sys-kernel-config.mount
systemd-analyze critical chain
graphical.target @27.790s
└─multi-user.target @27.789s
└─snapd.service @18.679s +9.109s
└─basic.target @18.633s
└─sockets.target @18.633s
└─snapd.socket @18.630s +2ms
└─sysinit.target @18.609s
└─systemd-timesyncd.service @18.432s +176ms
└─systemd-tmpfiles-setup.service @17.901s +509ms
└─systemd-journal-flush.service @4.060s +13.839s
└─systemd-journald.service @3.910s +149ms
└─haveged.service @3.908s
└─systemd-tmpfiles-setup-dev.service @2.669s +1.239s
└─kmod-static-nodes.service @2.412s +247ms
└─systemd-journald.socket @2.406s
└─-.mount @2.106s
└─-.slice @2.106s
Also, my inxi-Fazy
System:
Kernel: 5.11.16-2-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.11-x86_64
root=UUID=24bd1f49-ac6f-4594-8891-2c90acb44f58 rw quiet apparmor=1
security=apparmor udev.log_priority=3
Desktop: KDE Plasma 5.21.4 tk: Qt 5.15.2 wm: kwin_x11 vt: 2 dm: SDDM
Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Laptop System: HP product: OMEN by HP Laptop 15-dc1xxx v: N/A
serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: HP model: 8575 v: 21.16 serial: <filter> UEFI: AMI v: F.21
date: 11/13/2020
Battery:
ID-1: BAT0 charge: 45.3 Wh (100.0%) condition: 45.3/45.3 Wh (100.0%)
volts: 13.0 min: 11.6 model: HP Primary type: Li-ion serial: N/A
status: Full
CPU:
Info: 6-Core model: Intel Core i7-9750H bits: 64 type: MT MCP
arch: Kaby Lake note: check family: 6 model-id: 9E (158) stepping: A (10)
microcode: DE cache: L2: 12 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 62431
Speed: 800 MHz min/max: 800/4500 MHz Core speeds (MHz): 1: 800 2: 800 3: 800
4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel UHD Graphics 630 vendor: Hewlett-Packard driver: i915
v: kernel bus-ID: 00:02.0 chip-ID: 8086:3e9b class-ID: 0300
Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q]
vendor: Hewlett-Packard driver: nvidia v: 460.73.01
alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:1f91
class-ID: 0300
Device-3: Quanta HP Wide Vision HD Camera type: USB driver: uvcvideo
bus-ID: 1-6:2 chip-ID: 0408:5300 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org 1.20.11 compositor: kwin_x11 driver:
loaded: modesetting,nvidia unloaded: intel,nouveau alternate: fbdev,nv,vesa
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 142 size: 344x193mm (13.5x7.6")
diag: 394mm (15.5")
OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 21.0.3
direct render: Yes
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Hewlett-Packard
driver: snd_hda_intel v: kernel alternate: snd_soc_skl,snd_sof_pci
bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
Sound Server-1: ALSA v: k5.11.16-2-MANJARO running: yes
Sound Server-2: JACK v: 0.125.0 running: no
Sound Server-3: PulseAudio v: 14.2 running: yes
Sound Server-4: PipeWire v: 0.3.26 running: no
Network:
Device-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi v: kernel
port: 5000 bus-ID: 00:14.3 chip-ID: 8086:a370 class-ID: 0280
IF: wlo1 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel port: 3000 bus-ID: 03:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eno1 state: down mac: <filter>
IF-ID-1: virbr0 state: down mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB
driver: btusb v: 0.8 bus-ID: 1-14:3 chip-ID: 8087:0aaa class-ID: e001
Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: see --recommends
RAID:
Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
v: 3.0 port: 5060 bus-ID: 00:17.0 chip-ID: 8086.282a rev: 10 class-ID: 0104
Drives:
Local Storage: total: 1.14 TiB used: 345.04 GiB (29.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: PC SN720 SDAPNTW-256G-1006 size: 238.47 GiB block-size:
physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD
serial: <filter> rev: 10112006 temp: 44.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: HGST (Hitachi) model: HTS721010A9E630
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
rotation: 7200 rpm serial: <filter> rev: A3T0 scheme: GPT
Partition:
ID-1: / raw-size: 70 GiB size: 68.4 GiB (97.72%) used: 29.12 GiB (42.6%)
fs: ext4 dev: /dev/sda5 maj-min: 8:5
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%)
used: 82.3 MiB (32.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 26 GiB size: 25.47 GiB (97.95%)
used: 10.25 GiB (40.3%) fs: ext4 dev: /dev/sda6 maj-min: 8:6
Swap:
Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 4 GiB used: 28.4 MiB (0.7%) priority: -2
dev: /dev/sda4 maj-min: 8:4
Sensors:
System Temperatures: cpu: 63.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 297 Uptime: 8h 00m wakeups: 9 Memory: 7.58 GiB
used: 3.4 GiB (44.8%) Init: systemd v: 247 tool: systemctl Compilers:
gcc: 10.2.0 clang: 11.1.0 Packages: 1440 pacman: 1432 lib: 420 snap: 8
Shell: Bash v: 5.1.0 running-in: konsole inxi: 3.3.04
Getting rid of Snap could be an improvement I guess.
pamac remove --no-save snapd
If you don’t use Snaps of course, and if you do, probably try to switch these applications to Flatpaks first, or better, install them from repos, or the AUR.
Also it seems this took time, but I don’t think this would go on every boot as long. Maybe try to vacuum your journal logs too.
sudo journalctl --vacuum-size=64M
But yeah, getting a SSD is kinda the norm if you want a proper reactive system, it is really cheap nowadays, you can have a 120GB SSD, which is perfectly fine for a system disk, for less than 20€ (example the PNY CS900 SSD on my local Amazon goes for 18€ pretty often, just check prices regularly and buy when it is cheap, don’t buy no name SSD though, always buy a brand name).
PS: pro tip for Amazon price tracking, use browser extension called Keepa, it will add a price history on each product page if your country is eligible, (not all are => Amazon Locales Support [ .com | .co.uk | .de | .co.jp | .fr | .ca | .it | .es | .in | .com.mx | .com.br ]), and you can even program alerts if you want.
1 Like
Many thanks, the bit about snap helped very much
7.931s lvm2-monitor.service
5.761s polkit.service
5.468s dev-sda5.device
4.107s systemd-modules-load.service
2.849s avahi-daemon.service
2.848s bluetooth.service
2.846s NetworkManager.service
2.842s systemd-machined.service
2.841s systemd-logind.service
2.039s apparmor.service
1.975s systemd-udevd.service
1.472s ModemManager.service
1.368s systemd-tmpfiles-setup-dev.service
1.292s udisks2.service
1.184s tlp.service
1.067s systemd-journal-flush.service
775ms systemd-sysctl.service
517ms systemd-tmpfiles-setup.service
485ms systemd-fsck@dev-disk-by\x2duuid-6343ecdf\x2dc07a\x2d4a9d\x2d9e20\x2db6790f4ac652.service
464ms upower.service
458ms wpa_supplicant.service
389ms user@1000.service
361ms systemd-random-seed.service
274ms systemd-backlight@backlight:intel_backlight.service
259ms linux-module-cleanup.service
252ms dev-sda4.swap
235ms systemd-fsck@dev-disk-by\x2duuid-C6FD\x2d5E16.service
217ms systemd-journald.service
201ms dev-hugepages.mount
200ms dev-mqueue.mount
199ms sys-kernel-debug.mount
199ms sys-kernel-tracing.mount
197ms kmod-static-nodes.service
196ms modprobe@configfs.service
195ms modprobe@drm.service
195ms modprobe@fuse.service
194ms systemd-udev-trigger.service
179ms systemd-timesyncd.service
157ms systemd-binfmt.service
113ms rtkit-daemon.service
110ms systemd-rfkill.service
70ms systemd-update-utmp.service
69ms systemd-remount-fs.service
68ms boot-efi.mount
40ms systemd-user-sessions.service
20ms home.mount
8ms proc-sys-fs-binfmt_misc.mount
8ms tmp.mount
7ms sys-fs-fuse-connections.mount
7ms sys-kernel-config.mount
6ms user-runtime-dir@1000.service
Improvement big time!
As for SSD, I do have one, but Windows is installed on it(dual boot).
You can also disable some services, which are not needed.
This decreases the boot time.
Like? I’ve disabled snap alright but apart from that I don’t know what I can safely disable?
Thats depends on your setup:
- If you don´t use LVM, you can disable that service
- If you don´t use crypt, you can disable that service
- If you don´t use a modem, you can disable that service
1 Like