Help with improving bootup speed

Installed Manjaro a few weeks ago after years with Ubuntu. Having problems I suspect are related to errors I made in disk partitioning.

  • Startup slow, displays BIOS log 3 times;
  • Distinction between / and /home fuzzy, for example in left section of Thunar, [user name] “chas” in “Places” location is /home/chas but should be /. /run/media/chas/Home/chas/mervin but should be simply /Home/chas. Under “Devices,” “Home” location is /run/media/chas.

inxi output:

  Kernel: 6.1.11-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.2.1
    Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm
    v: 4.18.0 vt: 7 dm: LightDM v: 1.32.0 Distro: Manjaro Linux
    base: Arch Linux
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: PRIME Z690-A v: Rev 1.xx serial: <superuser required>
    UEFI: American Megatrends v: 1601 date: 07/07/2022
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510
    serial: <filter> charge: 55% (should be ignored) rechargeable: yes
    status: discharging
  Info: 12-core (8-mt/4-st) model: 12th Gen Intel Core i7-12700 bits: 64
    type: MST AMCP smt: enabled arch: Alder Lake rev: 2 cache: L1: 1024 KiB
    L2: 12 MiB L3: 25 MiB
  Speed (MHz): avg: 2041 high: 2896 min/max: 800/4800:4900:3600 cores:
    1: 2896 2: 2100 3: 2100 4: 2100 5: 937 6: 2100 7: 1304 8: 2100 9: 2100
    10: 2100 11: 2088 12: 2100 13: 2100 14: 2100 15: 2100 16: 2100 17: 2100
    18: 2100 19: 2100 20: 2100 bogomips: 84500
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Device-1: NVIDIA GF119 [GeForce GT 520] vendor: driver: nouveau
    v: kernel arch: Fermi pcie: speed: 2.5 GT/s lanes: 16 ports:
    active: DVI-I-1,DVI-I-2 empty: HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:1040
    class-ID: 0300 temp: 40.0 C
  Display: x11 server: X.Org v: 21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting alternate: fbdev,vesa dri: nouveau gpu: nouveau
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3840x1200 s-dpi: 96 s-size: 1016x317mm (40.00x12.48")
    s-diag: 1064mm (41.9")
  Monitor-1: DVI-I-1 pos: primary,left model: Acer G276HL serial: <filter>
    res: 1920x1080 hz: 60 dpi: 82 size: 598x336mm (23.54x13.23")
    diag: 686mm (27") modes: max: 1920x1080 min: 720x400
  Monitor-2: DVI-I-2 pos: right model: Samsung SyncMaster serial: <filter>
    res: 1920x1200 hz: 60 dpi: 94 size: 518x324mm (20.39x12.76")
    diag: 611mm (24.1") modes: max: 1920x1200 min: 720x400
  API: OpenGL Message: Unable to show GL data. Required tool glxinfo
  Device-1: Intel Alder Lake-S HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus-ID: 00:1f.3 chip-ID: 8086:7ad0 class-ID: 0403
  Device-2: NVIDIA GF119 HDMI Audio vendor: driver: snd_hda_intel
    v: kernel pcie: speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0e08
    class-ID: 0403
  Sound API: ALSA v: k6.1.11-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.65 running: yes
  Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie:
    speed: 5 GT/s lanes: 1 port: N/A bus-ID: 06:00.0 chip-ID: 8086:15f3
    class-ID: 0200
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Hardware-1: Intel Volume Management Device NVMe RAID Controller driver: vmd
    v: 0.6 port: N/A bus-ID: 00:0e.0 chip-ID: 8086:467f rev: class-ID: 0104
  Local Storage: total: 3.64 TiB used: 713.72 GiB (19.2%)
  ID-1: /dev/sda vendor: SanDisk model: SSD PLUS 2000GB size: 1.82 TiB
    speed: 6.0 Gb/s type: SSD serial: <filter> rev: 04RL scheme: GPT
  ID-2: /dev/sdb type: USB vendor: Western Digital model: WD20SDRW-11VUUS0
    size: 1.82 TiB type: HDD rpm: 5400 serial: <filter> rev: 1034 scheme: GPT
  ID-1: / size: 95.56 GiB used: 33.09 GiB (34.6%) fs: ext4 dev: /dev/sda4
  ID-2: /boot/efi size: 329.3 MiB used: 312 KiB (0.1%) fs: vfat
    dev: /dev/sda5
  ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda1
  System Temperatures: cpu: 36.0 C mobo: N/A gpu: nouveau temp: 40.0 C
  Fan Speeds (RPM): N/A
  Processes: 396 Uptime: 1d 11m wakeups: 35 Memory: 62.61 GiB
  used: 6.46 GiB (10.3%) Init: systemd v: 252 default: graphical Compilers:
  gcc: 12.2.1 clang: 15.0.7 Packages: 1246 pm: pacman pkgs: 1240 pm: flatpak
  pkgs: 6 Shell: Bash v: 5.1.16 running-in: xfce4-terminal inxi: 3.3.25

gparted graphic of the SSD:

I will appreciate any suggestion for how to clear this up without re-partitioning the disk.

can you report

sudo lsblk -fs
sudo cat /etc/fstab

what its appears

  1. bios grub , only in bios mode not UEFI
  2. you have also /boot/efi
  3. /home is inside your partition root / ( do not appears in fstab )
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=53e7e78e-5411-48ac-8bef-0154066b90a4 /              ext4    defaults,noatime 0 1
UUID=56E3-1748                            /boot/efi      vfat    umask=0077 0 2
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

for you install ( manjaro & SSD )
have you checked before all options in UEFI ?

  • no secure boot
  • no CSM
  • no legacy
  • all disks on AHCI
  • no optane/rst
  • no fast boot

may be remove with gparted flag bios_grub

what is result for

sudo systemd-analyze blame 
sudo systemd-analyze critical-chain 

Thank you for the tips. I’ll do some research and see what I can do along the lines you suggest.
Whoops, posted too soon - results you ask for:

[chas@chas-pc ~]$ sudo systemd-analyze blame
[sudo] password for chas: 
8.010s pkgfile-update.service
4.133s plymouth-quit.service
4.108s plymouth-quit-wait.service
1.083s dev-sda4.device
 876ms udisks2.service
 860ms man-db.service
 780ms systemd-journal-flush.service
 553ms tlp.service
 412ms snapd.service
 372ms cups.service
 311ms systemd-udev-trigger.service
 293ms systemd-remount-fs.service
 293ms systemd-tmpfiles-setup-dev.service
 280ms lvm2-monitor.service
 267ms user@1000.service
 267ms ModemManager.service
 255ms apparmor.service
 217ms lightdm.service
 212ms avahi-daemon.service
 211ms polkit.service
 210ms systemd-logind.service
 200ms systemd-modules-load.service
 199ms snapd.apparmor.service
 180ms dbus.service
 156ms plymouth-read-write.service
 150ms systemd-udevd.service
 126ms systemd-fsck@dev-disk-by\x2duuid-56E3\x2d1748.service
 125ms systemd-vconsole-setup.service
 123ms upower.service
 113ms boot-efi.mount
 101ms NetworkManager.service
 100ms ufw.service
  98ms systemd-sysctl.service
  91ms modprobe@fuse.service
  86ms plymouth-start.service
  76ms updatedb.service
  71ms logrotate.service
  70ms systemd-random-seed.service
  60ms systemd-tmpfiles-clean.service
  58ms modprobe@drm.service
  56ms NetworkManager-wait-online.service
  53ms systemd-tmpfiles-setup.service
  52ms colord.service
  47ms dev-sda1.swap
  42ms alsa-restore.service
  40ms systemd-journald.service
  39ms systemd-user-sessions.service
  34ms accounts-daemon.service
  33ms kmod-static-nodes.service
  33ms modprobe@configfs.service
  33ms user-runtime-dir@1000.service
  32ms systemd-timesyncd.service
  32ms systemd-update-utmp.service
  17ms sys-fs-fuse-connections.mount
  17ms pamac-daemon.service
  16ms dev-hugepages.mount
  16ms sys-kernel-config.mount
  15ms dev-mqueue.mount
  13ms sys-kernel-debug.mount
  12ms sys-kernel-tracing.mount
   4ms proc-sys-fs-binfmt_misc.mount
   3ms rtkit-daemon.service
   2ms tmp.mount
 461us snapd.socket


[chas@chas-pc ~]$ sudo systemd-analyze critical chain
Unknown command verb critical.
[chas@chas-pc ~]$

Dash - between critical and chain

[chas@chas-pc ~]$ sudo systemd-analyze critical-chain
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. @7.648s
└─lightdm.service @7.430s +217ms
  └─plymouth-quit.service @3.259s +4.133s
    └─systemd-user-sessions.service @3.213s +39ms
      └─ @7.454s
[chas@chas-pc ~]$

if this is the fisrt boot , it can be slow :

  • man-db service fisrt time + ending ext4 format , if you see cpu working
  • SSD with 1 second on boot , is not good

First boot of the day, or first boot ever? There have been many first-boots since installing Manjaro about three weeks ago and it was and remains slow to boot.
Right now I am researching the observations contained in your first message – will probably take me a while. Will definitely take me a while. Thank you.

Hi and welcome to the Forum :+1:

First of all please see:

Especially this link that’s mentioned in there:

Please re-edit all your posts to make command outputs be between the codeblocks as mentioned in above link.

What exactly do you want “cleared up” in what way :thinking:

As far as i could understand from the conversation so far is that your real request is about improving slow booting and not with the partitioning, so i’m changing the topic title to reflect that (to prevent other readers in future from being misguided)…

Note: That the timings you posted are not slow at all for any version of Linux…

This time jump (+ ~4s) is related to your network speed because it tries to check for updates, which is not slow at all either :wink:

You can disable some background services:

  1. lvm
  2. Modemmanager
  3. Plymouth (increases the boot time a lot)

You are precisely 180 degrees wrong and I resent you changing my title on the basis of your faulty comprehension of what I wrote.

There is not much you can do to make your system faster.

My workstation takes about 2 minutes to be ready - some systems takes longer than others - despite being highend. The hardware has a lot of initializing selfchecking stuff when being powered up for the first time every day.

 $ systemd-analyze blame
2min 183ms systemd-networkd-wait-online.service
    7.146s NetworkManager-wait-online.service
    7.128s man-db.service
    3.970s plymouth-quit.service
    3.947s plymouth-quit-wait.service
     756ms dev-nvme0n1p2.device
     746ms boot-efi.mount
     477ms a-iso.mount
     477ms a-private.mount
     475ms tmp.mount
     290ms systemd-udev-trigger.service
     260ms systemd-remount-fs.service
     227ms systemd-network-generator.service
     213ms systemd-tmpfiles-setup.service
     208ms systemd-modules-load.service
     173ms systemd-vconsole-setup.service
     170ms systemd-journal-flush.service
     164ms plymouth-read-write.service
     151ms lvm2-monitor.service
     149ms modprobe@fuse.service
     144ms systemd-sysusers.service
     134ms ldconfig.service
     128ms user@1000.service
     108ms systemd-random-seed.service
      91ms udisks2.service
      90ms modprobe@drm.service
      89ms systemd-journal-catalog-update.service
      88ms systemd-resolved.service
      77ms plymouth-start.service
      77ms polkit.service
      76ms a-virtualbox.mount
      76ms systemd-networkd.service
      74ms systemd-fsck@dev-disk-by\x2duuid-C7B2\x2d374E.service
      71ms modprobe@dm_mod.service
      69ms alsa-restore.service
      68ms systemd-logind.service
      67ms dbus.service
      65ms ModemManager.service
      54ms systemd-user-sessions.service
      54ms systemd-sysctl.service
      43ms user-runtime-dir@1000.service
      42ms systemd-tmpfiles-setup-dev.service
      42ms pamac-daemon.service
      41ms kmod-static-nodes.service
      41ms modprobe@configfs.service
      40ms packagekit.service
      37ms systemd-timesyncd.service
      36ms systemd-tmpfiles-clean.service
      36ms systemd-update-utmp.service
      33ms systemd-journald.service
      26ms upower.service
      23ms systemd-udevd.service
      23ms systemd-update-done.service
      16ms NetworkManager.service
      13ms sys-fs-fuse-connections.mount
      12ms sys-kernel-config.mount
      10ms a-projects.mount
       7ms dev-hugepages.mount
       7ms dev-mqueue.mount
       6ms sys-kernel-debug.mount
       6ms sys-kernel-tracing.mount
       5ms dev-disk-by\x2duuid-0f15b575\x2d4f23\x2d4dd3\x2dac6b\x2ddb1f1ac3381f.swap
       2ms modprobe@loop.service
       2ms rtkit-daemon.service
       1ms nordvpnd.socket
 $ inxi -SCmG
  Host: tiger Kernel: 6.2.0-1-MANJARO arch: x86_64 bits: 64
    Desktop: KDE Plasma v: 5.27.1 Distro: Manjaro Linux
  RAM: total: 62.62 GiB used: 41.06 GiB (65.6%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges
  Info: 12-core model: AMD Ryzen Threadripper PRO 5945WX s bits: 64
    type: MT MCP cache: L2: 6 MiB
  Speed (MHz): avg: 3339 min/max: 1800/7015 cores: 1: 3638 2: 3625 3: 1800
    4: 3630 5: 1800 6: 4100 7: 3986 8: 4540 9: 3637 10: 3632 11: 1800 12: 3628
    13: 3622 14: 1800 15: 4539 16: 4100 17: 3619 18: 3626 19: 1800 20: 4539
    21: 3631 22: 1800 23: 3625 24: 3636
  Device-1: AMD Ellesmere [Radeon Pro WX 7100] driver: amdgpu v: kernel
  Device-2: Logitech HD Webcam C525 type: USB driver: snd-usb-audio,uvcvideo
  Display: wayland server: v: with: Xwayland v: 22.1.8
    compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
    dri: radeonsi gpu: amdgpu resolution: 5120x1440
  API: OpenGL v: 4.6 Mesa 22.3.5 renderer: AMD Radeon Pro WX 7100 Graphics
    (polaris10 LLVM 15.0.7 DRM 3.49 6.2.0-1-MANJARO)

But if you do not intend to use snaps you can win a couple of seconds by reconfiguring the system.

  • apparmor
  • snapd

Plymouth is the moving dots - if you want to be without you can reconfigure your system.

pkgfile - is a convenience tool to locate files in packages - a pacman metadata explorer

I also read somewhere that 6.2 is faster than 6.1 kernel

You can configure your system to ignore cpu vulnerability mitigations - quite simple actually

Add nowatchdog mitigations=off to the kernel arguments in /etc/default/grub - remember to rebuild config.

Blacklist for watchdog - will speedup shutdown

echo "blacklist iTCO_wdt" > sudo tee -i /etc/modprobe.d/blacklist-watchdog.conf

Here is my boot time:

2.216s systemd-modules-load.service
1.163s systemd-random-seed.service
 259ms dev-nvme0n1p8.device
 211ms systemd-udev-trigger.service
 187ms user@1000.service
 171ms udisks2.service
 101ms systemd-journal-flush.service
  68ms systemd-journald.service
  64ms upower.service
  62ms systemd-tmpfiles-clean.service
  54ms boot.mount
  45ms systemd-udevd.service
  37ms systemd-fsck@dev-disk-by\x2duuid-1f4562ba\x2d4176\x2d40fd\x2d8f2c\x2ded1c4e047fc3.service
  36ms systemd-fsck@dev-disk-by\x2duuid-25ec34ea\x2d8afd\x2d4def\x2db2c8\x2d71869900a867.service
  34ms systemd-tmpfiles-setup.service
  32ms systemd-fsck@dev-disk-by\x2duuid-47570dc3\x2df04d\x2d4f24\x2db9ff\x2ddf0ea792a2b9.service
  31ms cups.service
  30ms home.mount
  29ms boot-efi.mount
  27ms systemd-logind.service
  25ms tmp.mount
  22ms systemd-tmpfiles-setup-dev.service
  21ms data.mount
  20ms NetworkManager.service
  20ms dev-nvme0n1p7.swap
  19ms var.mount
  19ms user-runtime-dir@1000.service
  19ms systemd-fsck@dev-disk-by\x2duuid-49A2\x2dBD43.service
  19ms dbus.service
  18ms modprobe@fuse.service
  12ms polkit.service
   8ms dev-hugepages.mount
   8ms dev-mqueue.mount
   7ms alsa-restore.service
   7ms sys-kernel-debug.mount
   6ms sys-kernel-tracing.mount
   6ms systemd-remount-fs.service
   6ms systemd-update-utmp.service
   6ms systemd-sysctl.service
   6ms kmod-static-nodes.service
   5ms modprobe@configfs.service
   5ms modprobe@drm.service
   3ms systemd-user-sessions.service
   3ms sys-kernel-config.mount
   2ms rtkit-daemon.service
   1ms sys-fs-fuse-connections.mount

I appreciate your efforts and willingness to help but you have wasted your time because of TriMoon’s injudicious changing of my title. I listed boot time primarily as a possible symptom of my partitioning, not the major problem. I was hoping to get some suggestions for ways to re-partition the disk, or some links to good tutorials on how to re-partition an in-use disk without losing data.

You cannot find such thing.

You cannot modify mounted partitions and you cannot repartition without loosing data.

Before venturing into adjusting partitions you must ensure you have a valid backup of your preciousss

Partitioning on ssd is merely setting up fences to separate data.

Back in the days with spinning disks - it could be an issue if you didn’t get the parameters right - with todays SSD there is no need - and it will not affect the read/write speed of your ssd as it is memorycells not magnetic plate.

When you - as you state - has been using Ubuntu for years - you should know that automounted removable devices end up in a volatile structure


Everything else is inside your home.

If you are used to Ubuntu then you are used to Nautilus - unless you used Xubuntu - then you wouldn’t have to state the above - as Xfce uses Thunar and this work the same no matter the distribution.

The gvfs packages is handling all the underlying stuff and pulls in the necessary dependencies.

If you want your removable devices to show up with a name instead of UUID - then use gparted to label the partiion - just remember - not all filesystems can be labelled with mounted.

The you should have specifically said that boot time was not the issue because partitioning of SSD does not affect boottime and as such you have yourself put emphasis on boottime which is also my impression from the content of your OT.

What you are trying to achieve is not clear.

I’m sorry if i misunderstood then, but that’s what i understood between all the text because of wrong markup… :woman_shrugging:
Feel free to undo my rename, but please be more specific and CLEAR about what you want…

Ok, show us.

What’s a BIOS log? Are you talking about post?

What should be /? The user’s home directory should be in /home, if the username is chas then it should be /home/chas. Not even root uses / as a home directory (it uses /root). Perhaps I’m missing something.

You’re auto-mounting the partition because it’s not configured to be mounted at /home during boot.

If that is the only partition named “Home” then this will configure your home partition to be used.

echo "LABEL=Home /home ext4 noatime 0 0" | sudo tee -a /etc/fstab

# if you have a problem then use the live USB, mount / and 
# post the contents of fstab here, comment out the line 
# we added and reboot

It looks like you already have a chas directory in your home partition, but the files may differ since you’ve been auto mounting it. Make sure all your files have been copied to the Home partition before rebooting. Be careful not to overwrite new files with old, if in doubt copy it all to a new directory (eg /run/media/chas/Home/chas/oldhome) and sort it out later.

Make sure you have a live USB just in case something goes wrong. Once you’re absolutely sure everything works and is where it’s meant to be, then you can use the live USB to delete the original files, it doesn’t hurt to leave it for a few days or weeks just in case you missed something. Be very careful!

If you’re unsure about doing any of this then read and ask questions.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.