Post upgrade to Ubuntu 25.10, rclone failes to mount remotes it previously could

Help and Support
1

What is the problem you are having with rclone?

After upgrading from Ubuntu 24.04 to Ubuntu 25.10, rclone no longer mounts my smb share.

As in, before the upgrade it worked, after it does not work.

Run the command 'rclone version' and share the full output of the command.

rclone v1.73.0
- os/version: ubuntu 25.10 (64 bit)
- os/kernel: 6.17.0-12-generic (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.25.6
- go/linking: static
- go/tags: none

Which cloud storage system are you using? (eg Google Drive)

smb mount served by zfs and smbd on a home server. As in the dataset has “sharesmb” set to “on”.

The path to the mount is something like: /poolname/dataset/folderToMount which then becomes smb://homeserver/poolname_dataset_folderToMount.

Server info:

cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Ubuntu 24.04.3 LTS"

# zfs --version
zfs-2.2.2-0ubuntu9.4
zfs-kmod-2.3.1-1ubuntu2

The command you were trying to run (eg rclone copy /tmp remote:tmp)

./rclone mount --log-level DEBUG --allow-other --log-format date,time,pid homeserversmb:/zpool_dataset /extra/testmount

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

[homeserversmb]
type = smb
host = XXX
user = XXX
pass = XXX

A log from the command that you were trying to run with the -vv flag

2026/01/31 20:48:53 [1248298] DEBUG : rclone: Version "v1.73.0" starting with parameters ["./rclone" "mount" "--log-level" "DEBUG" "--allow-other" "--log-format" "date,time,pid" "homeserversmb:/zpool_dataset" "/extra/testmount"]
2026/01/31 20:48:53 [1248298] DEBUG : Creating backend with remote "homeserversmb:/zpool_dataset"
2026/01/31 20:48:53 [1248298] DEBUG : Using config file from "/home/david-reagan/.config/rclone/rclone.conf"
2026/01/31 20:48:53 [1248298] DEBUG : fs cache: renaming cache item "homeserversmb:/zpool_dataset" to be canonical "homeserversmb:zpool_dataset"
2026/01/31 20:48:53 [1248298] INFO  : smb://username@homeserverdns:445/zpool_dataset/: poll-interval is not supported by this remote
2026/01/31 20:48:53 [1248298] DEBUG : smb://username@homeserverdns:445/zpool_dataset/: Mounting on "/extra/testmount"
2026/01/31 20:48:53 [1248298] NOTICE: mount helper error: fusermount3: mount failed: Permission denied
2026/01/31 20:48:53 [1248298] CRITICAL: Fatal error: failed to mount FUSE fs: fusermount: exit status 1

What I’ve checked:

  • Confirmed that rclone can list the files from the remote just fine. (rules out dns/firewall issues)
  • Turned off apparmor to make sure it was not the issue. systemctl stop apparmor
    • After failing to see anything journalctl or dmesg from apparmor…
  • Made sure fuse3 was installed. dpkg --get-selections | grep fuse
  • Manually ran modprobe fuse
  • Made sure I used rclone from what is in the Ubuntu repos. (In case there was some default config that would help.)
  • Downloaded the currently available rclone and used it instead of what was in Ubuntu’s repos.
  • Made sure fuser was as up to date as what Ubuntu has in it’s repos. fusermount3 version: 3.17.4
  • Ran dpkg-reconfigure fuse3 just to make sure nothing weird happened there during the upgrade.
  • Added user_allow_other to /etc/fuse.conf and tried using, and not using, the "--allow-other" flag.
  • Set mount point directory permissions to 777 for the full path to the target directory.
  • Confirmed the user/group id numbers on the server side have the same number as what I’m using on my client.
  • # ls -al /dev/fuse
crw-rw-rw- 1 root root 10, 229 Jan 31 14:00 /dev/fuse
  • used mount -t cifs to confirm I can mount it that way. It worked.
  • Confirmed I could list an S3 (Wasabi) remote, and then tried to mount it. I received the same fusermount3 error message.

FYI, I’m using rclone to mount so it can cache files locally. I did try not using rclone, and getting the cache working helped improve what I use that mount for.

The output I have above is from when I switched to a test mount point instead of what I actually use. The one I use was throwing a lot of vfs cache messages that didn’t seem helpful. Especially since the issue didn’t go away when i switch mount points.

At this point I’m at a loss. Is there a way to get more detailed information fuse about the error?

Any other ideas?

Thanks in advance!

2

welcome to the forum,

as a test, i would mount to subdir of my home dir.

1 Like
3

Thanks for the quick reply. :slight_smile:

That worked. Mounting at ~/rclonemount succeeded.

Why?

And how can I make it work where I actually want it to mount?

4

welcome

i am not an expert with fuse.
that fact that is works now, implies this is a not a rclone issue, not a fuse issue.

maybe, this is a linux user permission issue on the mountdir.
make sure the your username david-reagan has permission to the mountdir.

create a new mountpoint, just one level deep, such as /mounttest and try to mount to that.

5

as a test, run your original command, using sudo

6

Tried that after I read your reply. It didn’t work.

sudo runs into the same fusermount permission error.

Seems like I need to dig into how fuse actually works and how I might get it to output more helpful messages…

Maybe I’ll start with finding a changelog….

7

Ok. How does apparmor work anyway? I thought systemctl stop apparmor was supposed to stop it?

I’m asking because adding my secondary drive mount to the Allow both rw and ro type mounts section of /etc/apparmor.d/fusermount3 and starting apparmor let me mount to a subdirector of my secondary drive mount point.

Anyway, I’m off to figure out how you’re actually supposed to modify apparmor profiles to set up a permanent fix, but still…

8

Adding:

/etc/apparmor.d/local/fusermount3

      mount fstype=@{fuse_types} options=(nosuid,nodev) options in (ro,rw,noatime,dirsync,nodiratime,noexec,sync) -> /secondary_drive/**/,
      umount /secondary_drive/**/,
      # vim:ft=apparmor

Then systemctl restart apparmor (or reload).

Allows rclone to mount in subdirectories of /secondary_drive.