Cifs_mount failed w/return code = -113

Hi everyone,

Im a bit new here so i hope i post this threat in a good way.
I have a error and i can’t get it out, it’s about a cifs error.

homeassistant kernel: CIFS: Attempting to mount //192.168.2.76/Muziek
homeassistant kernel: CIFS: VFS: Error connecting to socket. Aborting operation.
homeassistant kernel: CIFS: VFS: cifs_mount failed w/return code = -113

I know it cant acces my NAS because the ip adres is wrong.
I looked in settings/system/storage/ and in Network storage there are none connected drives or whatever.

How do i remove this error, can anyone please help

Hello There, a bunch of questions:

Did you configure it beforehand? Did it ever work?
What do you mean with ‘the up is wrong’?
The cifs server is on another IP address?

Is there is lingering config under the backup settings?

I have exactly the same issue - it continually trys to connect to my NAS. I have a different NFS for backups and this folder is succeffully connected to Music Assistant (checked and working). I tried adding this as a storage location in HA, and this works fine - connects and mounts…however these errors are still occuring and repeating. Something in the background is trying to connect (probably with old credentials) and failing.

2025-09-19 01:03:31.403 homeassistant kernel: CIFS: enabling forceuid mount option implicitly because uid= option is specified

2025-09-19 01:03:31.403 homeassistant kernel: CIFS: enabling forcegid mount option implicitly because gid= option is specified

2025-09-19 01:03:31.403 homeassistant kernel: CIFS: Attempting to mount //10.0.0.118/Music

2025-09-19 01:03:31.422 homeassistant kernel: CIFS: VFS: cifs_mount failed w/return code = -13

Hi i mean that my NAS has another ip adres for now.
The only thing for now is how to remove the error in my HA system, i cant find out how to do this

There must be a setting somewhere trying to connect to the (old) IP. So check the Music Assistant, the backup options, … to check if there is any lingering configuration to clean up.

Hi, thank you very mutch, music assistant whas the problem.
I looked everywhere and it was so simple thanks to you!

1 Like

I tried removing the music assistant add on just to try and yes the error went away. I’ve narrowed mine down to whenever I have a remote share connected - even successfully - it will show the error. I’ll see if anyone else on MA is having the same issue.