inix -b
❱inxi -b
System:
Host: greg-venusseries Kernel: 6.12.4-1-MANJARO arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.2.4 Distro: Manjaro Linux
Machine:
Type: Desktop System: Micro (HK) Tech product: Venus Series v: N/A
serial: <superuser required>
Mobo: Shenzhen Meigao Equipment model: AHWSA serial: <superuser required>
UEFI: American Megatrends LLC. v: AHWSA.1.22 date: 03/12/2024
CPU:
Info: 14-core (6-mt/8-st) 13th Gen Intel Core i9-13900H [MST AMCP]
speed (MHz): avg: 492 min/max: 400/5200:5400:4100
Graphics:
Device-1: Intel Raptor Lake-P [Iris Xe Graphics] driver: i915 v: kernel
Display: x11 server: X.Org v: 21.1.14 with: Xwayland v: 24.1.4 driver: X:
loaded: modesetting dri: iris gpu: i915 resolution: 3840x2160~60Hz
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.8-arch1.1
renderer: Mesa Intel Graphics (RPL-P)
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Network:
Device-1: Intel Ethernet I226-V driver: igc
Device-2: Intel Ethernet I226-LM driver: igc
Device-3: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
driver: mt7921e
Drives:
Local Storage: total: 1.84 TiB used: 175.93 GiB (9.3%)
Info:
Memory: total: 32 GiB note: est. available: 31.07 GiB used: 5.55 GiB (17.8%)
Processes: 391 Uptime: 7m Shell: fish inxi: 3.3.37
I switched to using systemd automounts because I was having a lot of trouble with suspend/wake cycles hanging, and I was advised on the forum to learn to use this method.
But now I’m experiencing an issue with automounts in my Manjaro Linux setup that’s causing significant boot delays. I’ve configured several SMB shares using systemd
with .automount
units, and while they work perfectly once the system is running (mounting on demand and unmounting after the TimeoutIdleSec
interval), they are still being accessed during boot, causing long delays.
Here is an example of one of my automount configurations:
/etc/systemd/system/mnt-TRUENAS_manjaro_home.mount:
[Unit]
Description=Mount SMB Share - manjaro_home Mount
After=network-online.target
Wants=network-online.target
[Mount]
What=//192.168.1.100/manjaro-home
Where=/mnt/TRUENAS_manjaro_home
Type=cifs
Options=vers=2.0,credentials=/home/greg/.smbcredentials-scale,iocharset=utf8,file_mode=0666,dir_mode=0777,_netdev
[Install]
#WantedBy=multi-user.target
/etc/systemd/system/mnt-TRUENAS_manjaro_home.automount:
[Unit]
Description=Automount SMB Share - TRUENAS Manjaro Home
ConditionPathExists=/mnt/TRUENAS_manjaro_home
[Automount]
Where=/mnt/TRUENAS_manjaro_home
TimeoutIdleSec=30
[Install]
#WantedBy=multi-user.target
Despite the automount setup, the .mount
units seem to be triggered during boot. Here’s the relevant portion of the output from systemd-analyze blame
:
17.942s mnt-mandie_music_local.mount
17.917s mnt-TRUENASSCALE_cavern.mount
17.902s mnt-TRUENASSCALE_mandie.mount
17.846s mnt-TRUENASSCALE_media.mount
17.795s mnt-TRUENAS_cavern.mount
11.847s mnt-TRUENASSCALE_home.mount
11.828s mnt-TRUENASSCALE_manjaro_home.mount
11.712s mnt-TRUENAS_manjaro_home.mount
I’ve confirmed that the shares are functioning as expected after boot, but something is attempting to access the mount points during startup, triggering these delays. I’ve tried adding the noauto
option to the .mount
units and confirmed that the .automount
units are enabled, but the issue persists.
What I’ve done so far:
- Verified that the
.automount
units are enabled and the.mount
units are not explicitly enabled. - Added the
noauto
option to the.mount
files. - Increased the
TimeoutIdleSec
in.automount
files to reduce unnecessary mount/unmount cycles. - Tried
WantedBy
included & not included. - Checked
journalctl
logs but haven’t found any clear indicators of what’s accessing the mount points during boot.
Has anyone encountered this issue before? How can I prevent these automounts from being triggered during boot? Any help or pointers would be greatly appreciated!
Cheers,