[SOLVEDSeeing this in dmesg. Do I have a problem or can I ignore this?

MAYBL8 · 2025-08-16 12:27:43

I am automounting a nas folder.
Here is the 2 systemd mount files:

[root@arch-linux system]# cat /etc/systemd/system/home-demo-mnt-server-music.mount
[Unit]
Description=server music mount

[Mount]
What=//192.168.68.15/Music
Where=/home/demo/mnt/server/music
Type=cifs
Options=_netdev,rw,file_mode=0700,dir_mode=0700,uid=1000,gid=1000,iocharset=utf8
TimeoutSec=30

[Install]
WantedBy=multi-user.target

[root@arch-linux system]# cat /etc/systemd/system/home-demo-mnt-server-music.automount
[Unit]
Descripion=server music mount

[Automount]
Where=/home/demo/mnt/server/music
TimeoutIdleSec=10

[Install]
WantedBy=multi-user.target

Here is the message I see in dmesg:

[   10.847323] Key type cifs.spnego registered
[   10.847340] Key type cifs.idmap registered
[   10.847805] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
[   10.847807] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[   10.847808] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[   10.847809] CIFS: Attempting to mount //192.168.68.15/Music
[   10.847832] CIFS: VFS: Error connecting to socket. Aborting operation.
[   10.847834] CIFS: VFS: cifs_mount failed w/return code = -101

However when I go look at the mounted folder it is there.
So I am confused . Do I have a problem or not?
Thanks

Last edited by MAYBL8 (2025-08-18 14:15:53)

seth · 2025-08-16 13:57:56

101 is ENETUNREACH and probably a temporary issue because the mount is attempted before the network is properly setup?

MAYBL8 · 2025-08-16 14:02:35

That makes sense . Is there a way to avoid this error or should I just ignore it because the drive is mounting later in the process somewhere.

seth · 2025-08-16 14:23:51

network-online.target - but those all have "issues" (they typically do not mean what you mean by "online" - imho the entire target is completely useless, but oh, well)

I tend to use https://wiki.archlinux.org/title/Fstab# … th_systemd for remote FS but you could depend the mount on a target that's specifically only reached once you can ping the host.
But if the mount is re-attempted, later succeeds and things juts work you can also just look the other side and ignore the niose.

MAYBL8 · 2025-08-16 16:09:05

I don't have anything relating to my nas in the fstab file:

[root@arch-linux system]# cat /etc/fstab
# /dev/sda9
UUID=1d3a68b1-8394-4fa4-9bed-dd1eb4e80e60	/         	ext4      	rw,noatime	0 1

# /dev/sda6
UUID=b51b04db-e40f-48c0-aaff-d669e1864bb2	/home         	ext4      	rw,noatime	0 1

# /dev/sda1
UUID=8BC3-B538      	/boot/efi     	vfat      	rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

# //192.168.68.15/Music /home/demo/mnt/music cifs _netdev,nofail,username=demo,password=demo 0 0

seth · 2025-08-16 16:20:38

Yeah, so the idea was to use x-systemd.automount - whether you do this via fstab or a "manual" systemd.mount doesn't really matter.

MAYBL8 · 2025-08-16 19:16:53

Isn't that what I am using?

seth · 2025-08-16 20:00:12

Depends on whether you also have enabled the mount.
If not, what is triggering the mount "too early"?

MAYBL8 · 2025-08-16 21:00:00

Well that is a great question. I thought just running the service with the correct parameters triggers the mount.
How do we investigate this?

seth · 2025-08-16 21:39:43

What service?
The idea about the automount is that the mount gets ignored until something accesses the mountpoint.

I'd suggest to remove the "manual" mount services, uncomment the fstab entry and add "noauto,x-systemd.automount,x-systemd.mount-timeout=30" to the present options.
If you're stiff encountering cifs errors (specifically "-101"), check the system journal for stuff that starts right before that or in doubt your can https://wiki.archlinux.org/title/Audit_ … ies_access

MAYBL8 · 2025-08-18 14:15:02

@Seth
Thanks for the info. I don't want to use fstab settings so I am not going to do that.
I am just going to ignore the message since it is working just fine as it is.

I will mark this solved.

Arch Linux

#1 2025-08-16 12:27:43

[SOLVEDSeeing this in dmesg. Do I have a problem or can I ignore this?

#2 2025-08-16 13:57:56

Re: [SOLVEDSeeing this in dmesg. Do I have a problem or can I ignore this?

#3 2025-08-16 14:02:35

Re: [SOLVEDSeeing this in dmesg. Do I have a problem or can I ignore this?

#4 2025-08-16 14:23:51

Re: [SOLVEDSeeing this in dmesg. Do I have a problem or can I ignore this?

#5 2025-08-16 16:09:05

Re: [SOLVEDSeeing this in dmesg. Do I have a problem or can I ignore this?

#6 2025-08-16 16:20:38

Re: [SOLVEDSeeing this in dmesg. Do I have a problem or can I ignore this?

#7 2025-08-16 19:16:53

Re: [SOLVEDSeeing this in dmesg. Do I have a problem or can I ignore this?

#8 2025-08-16 20:00:12

Re: [SOLVEDSeeing this in dmesg. Do I have a problem or can I ignore this?

#9 2025-08-16 21:00:00

Re: [SOLVEDSeeing this in dmesg. Do I have a problem or can I ignore this?

#10 2025-08-16 21:39:43

Re: [SOLVEDSeeing this in dmesg. Do I have a problem or can I ignore this?

#11 2025-08-18 14:15:02

Re: [SOLVEDSeeing this in dmesg. Do I have a problem or can I ignore this?

Board footer