Hi all,
I’m hoping someone can clarify whether this is expected behaviour or whether I’ve misunderstood something.
I’m running Volumio 4 on a Raspberry Pi, with my music library on an external USB SSD formatted as exFAT. Playback works perfectly, but the drive is read-only when I access it over SMB from my Mac, so I can’t copy new music onto it over the network.
I thought I’d have a bit of a dig around over SSH to see if I could understand what was happening.
From what I can see, Volumio mounts my drive with
mount /dev/sdb2 /mnt/USB/MUSIIIICK -o noatime
The resulting mount options are
rw,noatime,fmask=0022,dmask=0022
and the mount is owned by root:root.
I then traced the mount process to
/volumio/app/plugins/system_controller/networkfs/index.js
where vfat and ntfs receive
noatime,dmask=0000,fmask=0000,iocharset=utf8
whereas exfat appears to fall through to simply: noatime
From my (very limited) understanding, that seems to result in the default exFAT permissions being applied, which then prevents write access over SMB.
Have I understood that correctly, or is there another reason exFAT is handled differently? Is this intentional, or could exFAT simply be missing from that special-case logic?
I’d really appreciate any clarification. I’m trying to understand how Volumio is intended to behave rather than just patching files if there’s already a supported approach.
Thanks very much.