mchnz
May 30, 2025, 5:04am
1
I cannot mount an extfat sdcard on Tumbleweed.
% mount -o ro /dev/sdf1 /mnt/tmp2/
/sbin/mount.exfat: error while loading shared libraries: libfuse3.so.3: cannot open shared object file: No such file or directory
% rpm -q -l -v libfuse3-4
-rwxr-xr-x 1 root root 276680 Apr 27 11:00 /usr/lib64/libfuse3.so.3.17.2
lrwxrwxrwx 1 root root 18 Apr 27 11:00 /usr/lib64/libfuse3.so.4 -> libfuse3.so.3.17.2
% ldd /sbin/mount.exfat
linux-vdso.so.1 (0x00007f98588a2000)
libfuse3.so.3 => not found
libc.so.6 => /lib64/libc.so.6 (0x00007f9858600000)
/lib64/ld-linux-x86-64.so.2 (0x00007f98588a4000)
I don’t know how safe it is, but I can work around the issue by making a symlink:
% ln -s /usr/lib64/libfuse3.so.3.17.2 /usr/lib64/libfuse3.so.3
marel
May 30, 2025, 7:24am
2
The problem seems to be exFAT specific.
It looks to me a fuse exfat mount is tried but checking zypper on my system I see fuse-exfat is not installed, is it installed on your system?
mchnz
May 30, 2025, 9:36am
3
Correct, it’s an exfat issue. Another card, presumably in another format, mounted just fine.
% rpm -q -a | grep exfat
exfat-utils-1.4.0-2.4.x86_64
fuse-exfat-1.4.0-3.4.x86_64
A mount of this card had always worked in the past (always extracted from the same camera).libfuse3.so.3.17.2 to /usr/lib64/libfuse3.so.3 the mount worked as before. I’m assuming the problem is due to some zypper-dup I’ve done in recent weeks.
You need to install libfuse3-4.
hui
May 30, 2025, 2:18pm
5
libfuse3-4 provideslibfuse3.so.4…
Ok, spoke to soon.
On mine I have:
> ls /usr/lib64/ | grep libfuse
libfuse3.so.3.17.2
libfuse3.so.4
libfuse.so.2
libfuse.so.2.9.9
libfuse.so.2 links to libfuse.so.2.9.9
libfuse3.so.4 links to libfuse3.so.3.17.2
mchnz
May 30, 2025, 6:41pm
7
The best test for whether you might have the same problem is to do:
% ldd /sbin/mount.exfat
And see if it reports libfuse3.so.3 => not found
As mentioned in my original post I do have libfuse3-4 installed and it does not list a link or file for libfuse3.so.3.
For completeness, I should report that /usr/sbin/mount.exfat is from:
% rpm -q -f /sbin/mount.exfat
fuse-exfat-1.4.0-3.4.x86_64
(I’ve done an rpm --verify on libfuse3-4 and fuse-exfat-1.4.0)
1 Like
I am able to mount exfat devices and this is what mine looks like.
> ldd /sbin/mount.exfat
linux-vdso.so.1 (0x00007f8ee1a1f000)
libfuse3.so.4 => /lib64/libfuse3.so.4 (0x00007f8ee1000000)
libc.so.6 => /lib64/libc.so.6 (0x00007f8ee0c00000)
/lib64/ld-linux-x86-64.so.2 (0x00007f8ee1a21000)
And…
> sudo fsck -N /dev/sdd1
[sudo] password for root:
fsck from util-linux 2.40.4
[/usr/sbin/fsck.exfat (1) -- /dev/sdd1] fsck.exfat /dev/sdd1
I don’t know where your old libfuse3.so.3 came from or why it’s still there.
mchnz
May 31, 2025, 5:39am
9
Thanks, that was a good clue, I was looking in the wrong direction:
% rpm -q --verify fuse-exfat-1.4.0-3.4
..5...... /usr/sbin/mount.exfat-fuse
So mount.exfat-fuse doesn’t match the one packaged.
% rpm --upgrade --force /var/cache/zypp/packages/download.opensuse.org-oss/x86_64/fuse-exfat-1.4.0-3.4.x86_64.rpm
rpm -V fuse-exfat-1.4.0-3.4l
Fixed…
% dd /sbin/mount.exfat
linux-vdso.so.1 (0x00007f37a7070000)
libfuse3.so.4 => /lib64/libfuse3.so.4 (0x00007f37a6600000)
libc.so.6 => /lib64/libc.so.6 (0x00007f37a6200000)
/lib64/ld-linux-x86-64.so.2 (0x00007f37a7072000)
This is likely due to an issue I had with restore using rsync: recently, OpenSUSE wasn’t changing the date-times on re-released packages .
1 Like
You’re welcome. Glad I could help. I’ve been tuning the cooling on this machine. Your fans slow down at idle and the temps rise a little so I was reading while it cooled back down. I got my idle temp to drop by 4C.
I have an old 32GB USB stick that a friend gave me with some photos on it and I just happened to know where it was. I used it to check to see if my exfat was working. I have others but I knew it used exfat.
Forced reinstall of a package has helped me many times, and it’s probably failed twice as much, but having a good clue is the key.
Have a great day!
1 Like