Hi there - I have just received my new Vero V - thanks a lot! I am experiencing issues playing Flac files - from the logs it appears to be an NFS issue. M4a files from the same source play fine. A debug log is attached.
Expected outcome
A flac audio file can be played when it resides on an NFS share
Actual outcome
No audio plays and the UI skips to the next track (if “automatically play next track” is on ), and so on.
Steps to Reproduce:
- Play a Flac audio file from an NFS network share
Debug Log
Full log is linked here but the pertinent error messages appear to be:
2025-11-30 17:49:35.142 T:11648 error <general>: Read - Error( -34, read call failed with "NFS4: READ (path (null)) failed with NFS4ERR_OLD_STATEID(-5)" )
2025-11-30 17:49:35.176 T:11648 error <general>: Read - Error( -34, read call failed with "NFS4: READ (path (null)) failed with NFS4ERR_BAD_STATEID(-22)" )
2025-11-30 17:49:35.176 T:11648 error <general>: Process - <nfs://192.168.1.133/volume1/media/Audio/Bastille/All This Bad Blood/1-01 Pompeii.flac> source read failed with -34!
Are you doing NFS mounts through Kodi (i.e. setup the source in Kodi and point it to the NFS mount) or via fs/autofs mounts on the OSMC file system (in which case the Kodi source points to a “local” directory). I ask only because I’m doing the latter to a NFS mount from my Synology NAS and haven’t had any problems playing FLAC files (or anything else). The built in Kodi NFS is OK, but the OSMC mounts tend to give me better performance.
Also, what’s serving your NFS mounts?
Hi - thanks for the reply.
NFS mounts added by Kodi via Settings→Media→Audio
I haven’t had any issues playing any other types of media from the same sources, including MP3, AAC or various video formats - only FLAC.
The NFS mounts are on a Synology Diskstation.
I could just mount the file shares on the OSMC linux filesystem, but they are not always on and the Kodi WOL feature works well. I have not had much success setting up an equivalent for autofs.
Resolved - or possible workaround - by setting the NFS Client (Services→NFS Client) protocol to v3 rather than v4 (v4 is supported and enabled on the server).
I’ll see if I can reproduce this using Kodi running on desktop, if so will report upstream as it’s not really an OSMC issue.
Do let us know the desktop OS
In general it doesn’t seem be limited to flac or the Vero. I’m having the same error on a Raspberry Pi 4, but with MP3 and AAC via NFS (even converted some files just for investigation):
Read - Error( -34, read call failed with “NFS4: READ (path (null)) failed with NFS4ERR_BAD_STATEID(-22)
MP3/AAC via SMB from the same source in LAN (Linux Mint PC) works fine.
Strange: Videos (AVI, MKV) via NFS from the same source work fine with the exact same setup.
Following the advice above to switch OSMC from NFS4 to NFS v3 as a workaround seems to have helped.
.
While the exact opposite (long video files) has been described here: Playback stops due to unreliable NFSv4 mount · Issue #22862 · xbmc/xbmc · GitHub The fix was claimed to be merged end of 2023 in KODI v21 NFSv3 and NFSv4 fixes and improvements by thexai · Pull Request #22897 · xbmc/xbmc · GitHub (but I’m no developer whatsoever, to judge that)
So I suspect it has been integrated in OSMC also by 2025… :-S