Unable to mount network storage

Installation
1

Hi all,

I was running HA through Docker on my Synology NAS. Decided to transfer over to Proxmox vm on a mini pc using backup/restore. Everything seemed to work perfectly fine but just realised that my network storage wasn’t there. When I try to add through NFS it I get the following error

Could not unmount media due to: Transaction for mnt-data-supervisor-mounts-media.mount/stop is destructive (mnt-data-supervisor-mounts-media.mount has ‘start’ job queued, but ‘stop’ is included in transaction).

Screenshot 2025-02-16 105537
Screenshot 2025-02-16 105537708×707 32.1 KB

“media” being the name I’m trying to give the storage. This was the name it had previously and trying another name or a different location on my NAS gives the same result.

The log shows the following
Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:141
integration: Home Assistant Supervisor (documentation, issues)
First occurred: 13:56:53 (8 occurrences)
Last logged: 19:37:18

Failed to to call /mounts - Could not unmount media due to: Transaction for mnt-data-supervisor-mounts-media.mount/stop is destructive (mnt-data-supervisor-mounts-media.mount has ‘start’ job queued, but ‘stop’ is included in transaction).

Also tried CIFS and got the same error

I’ve had a look at /etc/fstab but there’s no mention of the mounts I want to use there

Any help would be greatly appreciated.

Thanks in advance

2

Have you had any success with this? I have the same exact issue. I can not mount my NAS for backups. I restored my HA as I moved from a temp VM to the perm one - and restored. Everything works execpt trying to add the NAS for backups. Receive the same error.

3

Unfortunately not. I’ve been working on this issue, on and off for over a year now but haven’t got anywhere. Asked in a fair few places for advice in that time but the only replies I’ve ever had are from people who have the same issue.

4

I ran into the same issue and ended up debugging it by experimenting with the NFS server export options for my share.

Initially, my /etc/exports entry looked like this:

/mnt/nfsshare 192.168.1.0/24(ro,all_squash,insecure,async,no_subtree_check,anonuid=1000,anongid=1000)

I started removing options one by one and tested the NFS connection after each change. Eventually, I got it working with this configuration:

/mnt/nfsshare 192.168.1.0/24(ro,all_squash,insecure,async,no_subtree_check)

In my case, it turned out that the issue was caused by the anonuid=1000,anongid=1000 parameters. Removing them resolved the problem.

Start with the basic parameters (rw,sync,no_subtree_check,insecure) and go from there.

Context:
Home Assistant Core v. 2025.5.1