Slow boot time/restart

[embrance]

I have installed manjaro many times and it was very fast booting and restarting etc. But now its like 40% slower.

Heres are some info:

systemd-analyze blame | head -n 20

27.666s udisks2.service
9.758s pkgfile-update.service
6.859s systemd-modules-load.service
6.302s NetworkManager-wait-online.service
759ms systemd-random-seed.service
435ms dev-sda2.device
191ms user@1000.service
144ms systemd-udev-trigger.service
117ms lvm2-monitor.service
107ms ModemManager.service
88ms systemd-journal-flush.service
78ms boot-efi.mount
62ms logrotate.service
56ms systemd-journald.service
51ms cups.service
44ms systemd-logind.service
43ms upower.service
40ms systemd-udevd.service
40ms NetworkManager.service
37ms polkit.service

and

inxi -Fza

System:
Kernel: 5.15.81-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.15-x86_64
root=UUID=1b9ad4f0-2926-4b4e-ac1f-7fe2604701eb rw quiet
resume=UUID=a086efd7-88b3-468e-bf05-d12530cd4b49 udev.log_priority=3
Desktop: KDE Plasma v: 5.26.4 tk: Qt v: 5.15.7 info: latte-dock
wm: kwin_x11 vt: 1 dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME B450-PLUS v: Rev X.0x
serial: UEFI: American Megatrends v: 3211
date: 08/10/2021
CPU:
Info: model: AMD Ryzen 5 2600 bits: 64 type: MT MCP arch: Zen+ gen: 2
level: v3 note: check built: 2018-21 process: GF 12nm family: 0x17 (23)
model-id: 8 stepping: 2 microcode: 0x800820D
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 576 KiB desc: d-6x32 KiB; i-6x64 KiB L2: 3 MiB desc: 6x512 KiB
L3: 16 MiB desc: 2x8 MiB
Speed (MHz): avg: 1692 high: 3215 min/max: 1550/3400 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1380 2: 1335
3: 2414 4: 1376 5: 1376 6: 1376 7: 2373 8: 1333 9: 3215 10: 1375
11: 1376 12: 1377 bogomips: 81630
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed mitigation: untrained return thunk; SMT vulnerable
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: Retpolines, IBPB: conditional, STIBP:
disabled, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA TU106 [GeForce RTX 2060 SUPER] vendor: ASUSTeK
driver: nvidia v: 525.60.11 alternate: nouveau,nvidia_drm
non-free: 520.xx+ status: current (as of 2022-10) arch: Turing
code: TUxxx process: TSMC 12nm built: 2018-22 pcie: gen: 1
speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s
bus-ID: 08:00.0 chip-ID: 10de:1f06 class-ID: 0300
Display: x11 server: X.Org v: 21.1.4 compositor: kwin_x11 driver: N/A
display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1080 s-dpi: 81
s-size: 803x343mm (31.61x13.50") s-diag: 873mm (34.38")
Monitor-1: HDMI-1 res: 2560x1080 hz: 60 dpi: 81
size: 798x334mm (31.42x13.15") diag: 865mm (34.06") modes: N/A
API: OpenGL v: 4.6.0 NVIDIA 525.60.11 renderer: NVIDIA GeForce RTX
2060 SUPER/PCIe/SSE2 direct render: Yes
Audio:
Device-1: NVIDIA TU106 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 08:00.1 chip-ID: 10de:10f9 class-ID: 0403
Device-2: AMD Family 17h HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 0a:00.3 chip-ID: 1022:1457 class-ID: 0403
Sound API: ALSA v: k5.15.81-1-MANJARO running: yes
Sound Server-1: JACK v: 1.9.21 running: no
Sound Server-2: PulseAudio v: 16.1 running: yes
Sound Server-3: PipeWire v: 0.3.61 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 03:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp3s0 state: down mac:
Device-2: Intel Wireless-AC 9260 driver: iwlwifi v: kernel pcie:
gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 07:00.0 chip-ID: 8086:2526
class-ID: 0280
IF: wlp7s0 state: up mac:
Bluetooth:
Device-1: Intel Wireless-AC 9260 Bluetooth Adapter type: USB
driver: btusb v: 0.8 bus-ID: 1-6:3 chip-ID: 8087:0025 class-ID: e001
Report: rfkill ID: hci0 rfk-id: 0 state: down
bt-service: enabled,running rfk-block: hardware: no software: yes
address: see --recommends
Drives:
Local Storage: total: 13.21 TiB used: 70.09 GiB (0.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Crucial model: CT525MX300SSD1
size: 489.05 GiB block-size: physical: 512 B logical: 512 B
speed: 6.0 Gb/s type: SSD serial: rev: R040 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 EVO 1TB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B
speed: 6.0 Gb/s type: SSD serial: rev: 2B6Q scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Toshiba model: HDWD110
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B
speed: 6.0 Gb/s type: HDD rpm: 7200 serial: rev: A8R0
scheme: GPT
ID-4: /dev/sdd maj-min: 8:48 type: USB vendor: Toshiba
model: External USB 3.0 size: 3.64 TiB block-size: physical: 4096 B
logical: 512 B type: N/A serial: rev: 5438 scheme: GPT
ID-5: /dev/sdf maj-min: 8:80 type: USB vendor: Western Digital
model: WD80EZAZ-11TDBA0 size: 7.28 TiB block-size: physical: 4096 B
logical: 512 B type: HDD rpm: 5400 serial: rev: 4007
scheme: GPT
Partition:
ID-1: / raw-size: 454.38 GiB size: 446.16 GiB (98.19%)
used: 70.09 GiB (15.7%) fs: ext4 dev: /dev/sda2 maj-min: 8:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 312 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 34.38 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda3 maj-min: 8:3
Sensors:
System Temperatures: cpu: 30.2 C mobo: N/A gpu: nvidia temp: 43 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
Processes: 304 Uptime: 13m wakeups: 0 Memory: 31.25 GiB
used: 2.84 GiB (9.1%) Init: systemd v: 251 default: graphical
tool: systemctl Compilers: gcc: 12.2.0 clang: 14.0.6 Packages: 1276
pm: pacman pkgs: 1216 libs: 317 tools: pamac pm: flatpak pkgs: 60
Shell: Zsh v: 5.9 default: Bash v: 5.1.16 running-in: konsole
inxi: 3.3.23

last
journalctl --boot --priority=3

Dec 12 09:44:56 kiushin-manj kernel: sd 10:0:0:0: [sde] No Caching mode page found
Dec 12 09:44:56 kiushin-manj kernel: sd 10:0:0:0: [sde] Assuming drive cache: write through
Dec 12 09:44:56 kiushin-manj kernel: sd 11:0:0:0: [sdf] No Caching mode page found
Dec 12 09:44:56 kiushin-manj kernel: sd 11:0:0:0: [sdf] Assuming drive cache: write through
Dec 12 09:44:56 kiushin-manj kernel: kvm: disabled by bios
Dec 12 09:44:56 kiushin-manj kernel: kvm: disabled by bios
Dec 12 09:44:56 kiushin-manj kernel: kvm: disabled by bios
Dec 12 09:44:56 kiushin-manj kernel:
Dec 12 09:44:56 kiushin-manj kernel: kvm: disabled by bios
Dec 12 09:44:57 kiushin-manj kernel: xhci_hcd 0000:04:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x>
Dec 12 09:44:57 kiushin-manj kernel: kvm: disabled by bios
Dec 12 09:44:57 kiushin-manj kernel: kvm: disabled by bios
Dec 12 09:44:57 kiushin-manj kernel: kvm: disabled by bios
Dec 12 09:45:01 kiushin-manj kernel: kvm: disabled by bios
Dec 12 09:45:01 kiushin-manj kernel: scsi 11:0:0:1: Wrong diagnostic page; asked for 1 got 8
Dec 12 09:45:01 kiushin-manj kernel: scsi 11:0:0:1: Failed to get diagnostic page 0x1
Dec 12 09:45:01 kiushin-manj kernel: scsi 11:0:0:1: Failed to bind enclosure -19
Dec 12 09:45:01 kiushin-manj kernel: kvm: disabled by bios
Dec 12 09:45:01 kiushin-manj kernel: kvm: disabled by bios
Dec 12 09:45:01 kiushin-manj kernel: kvm: disabled by bios
Dec 12 09:45:01 kiushin-manj kernel: kvm: disabled by bios
Dec 12 09:45:02 kiushin-manj bluetoothd[576]: src/plugin.c:plugin_init() Failed to init vcp plugin
Dec 12 09:45:02 kiushin-manj bluetoothd[576]: src/plugin.c:plugin_init() Failed to init mcp plugin
Dec 12 09:45:02 kiushin-manj bluetoothd[576]: src/plugin.c:plugin_init() Failed to init bap plugin
Dec 12 09:45:02 kiushin-manj bluetoothd[576]: Failed to set mode: Blocked through rfkill (0x12)
Dec 12 09:45:02 kiushin-manj kernel: nvidia-gpu 0000:08:00.3: i2c timeout error e0000000
Dec 12 09:45:02 kiushin-manj kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
Dec 12 09:45:02 kiushin-manj kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
Dec 12 09:45:08 kiushin-manj bluetoothd[576]: Failed to set mode: Blocked through rfkill (0x12)
Dec 12 09:45:11 kiushin-manj systemd[664]: Failed to start Powerdevil.
Dec 12 09:45:16 kiushin-manj systemd[664]: Failed to start Powerdevil.
Dec 12 09:45:22 kiushin-manj systemd[664]: Failed to start Powerdevil.
Dec 12 09:45:27 kiushin-manj systemd[664]: Failed to start Powerdevil.
Dec 12 09:45:32 kiushin-manj kernel: xhci_hcd 0000:04:00.0: xHCI host controller not responding, assume d>
Dec 12 09:45:32 kiushin-manj kernel: xhci_hcd 0000:04:00.0: HC died; cleaning up
Dec 12 09:45:32 kiushin-manj kernel: blk_u

[Mirdarthos]

Hi @embrance,

---

Tip:

When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:

```
pasted text
```

This will just cause it to be rendered like this:

Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.

Instead of like this:

Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.

Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.

Thereby increasing legibility thus making it easier for those trying to provide assistance.

For more information, please see:

@Fabby

On this forum here you need to have Trust Level 1 (=TL1) to be able to post screenshots and links in-line.

That’s dumb! Why is that?

Well, that’s because on our old forum we got tons of screenshots of text, links to SPAM, PR0N and other things you don’t want on a forum, so all the new users are prohibited from posting links and pics because of a few bad actors.

---

Also, if your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:

LC_ALL=C bluetoothctl

This will just cause the terminal output to be in English, making it easier to understand and debug.

Please edit your post accordingly.

---

While you’re at it, please provide the output for:

systemd-analyze critical-chain

…and…

systemd-analyze critical-chain udisks2.service

…formatted as described above.

Edit:

For this person it was because of dropbox. Which doesn’t make all that much sense, while at the same time it does. So make sure there are no network mounts that takes up the time. I suggest Systemd automounts, I have a few network automounts that work perfectly, so I know they work.

See

[root tip] [How To] Use systemd to mount ANY device

Difficulty: ★☆☆☆☆ Disk device recognition Manjaro uses udev (see Arch Wiki) to load devices at boot time. The loading of devices is arbitrary and therefore you cannot predict which device will be available at a given path. But static device names do exist and you can assign specific locations to your device and thus ensure e.g. scripts will work as expected. What to learn Overview of system mount units Structure and Content of a mount unit Mount at boot (immediate mount) Mount on demand (m…

and

[root tip] [How To] systemd mount unit samples

Difficulty: ★★☆☆☆ Example mount units for systemd The examples here are a supplement to the guide on systemd mount units Remember to remove the comments placed in the units - they are not writing for copy-paste but as examples. (comments is text beginning with a #) [root tip] [How To] Use systemd to mount ANY device Only use an automount unit if the device is not readily available at boot like removable devices and network locations. Important rule …

[embrance]

Regarding the mount points…i dont understand. What they are and why NOW i have the problem while in the past i didnt. Here are the outputs.

…

systemd-analyze critical-chain udisks2.service                                             ✔ 
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

udisks2.service +1min 15.690s
└─basic.target @7.015s
  └─sockets.target @7.015s
    └─dbus.socket @7.015s
      └─sysinit.target @7.012s
        └─systemd-sysctl.service @7.004s +8ms
          └─systemd-modules-load.service @247ms +6.756s
            └─systemd-journald.socket @240ms
              └─-.mount @230ms
                └─-.slice @230ms

…

…

systemd-analyze critical-chain                                                    1 ✘  5s  
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @7.128s
└─multi-user.target @7.128s
  └─cups.service @7.088s +40ms
    └─network.target @7.087s
      └─NetworkManager.service @7.053s +34ms
        └─dbus.service @7.018s +32ms
          └─basic.target @7.015s
            └─sockets.target @7.015s
              └─dbus.socket @7.015s
                └─sysinit.target @7.012s
                  └─systemd-sysctl.service @7.004s +8ms
                    └─systemd-modules-load.service @247ms +6.756s
                      └─systemd-journald.socket @240ms
                        └─-.mount @230ms
                          └─-.slice @230ms

…

[Mirdarthos]

From what I read earlier, it would seem it might be because of some external drive. If you have any connected, even if it’s stationery and only used on your computer, if it connects externally, try disconnecting it and try again.

If that doesn’t work, please provide the output of:

mount

…and:

lsblk

…and, finally:

cat /etc/fstab

[embrance]

@Mirdarthos

systemd-analyze critical-chain udisks2.service

I rtemoved all useb hdds and tried them one by one. Apparently one of the,when connected on the lowe row of usb ports of the mobo slowed down the whole system. dont know why but now boots fast again. thanks