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

5

Cheers for that. I’ll take a look tomorrow when I’ve got some free time

6

I had this issue as well and mine was a much more dumbed down fix but i’m posting to help someone else I hope.

On my UNAS_Pro I had to go into the UNAS settings/Services/ then enable NFS (because that’s what I was trying to use. Then I had to add a new NFS connection in that same page on the UNAS pro. Settings for this new connection was my home assistant IP, then under where you enter that you need to click add a shared drive, choose your drive, after that the link for the drive will appear under your new entry.

Hope it helps someone.

7

I’ve been fighting this and looking for a solution for a couple of weeks. Turns out it was throwing that error with my UNAS Pro because I was logged in via my Nabu Casa address. As soon as I logged into the local IP and added the share, everything worked.

8

I came here because I had the error in the original post. I found a fix,

I got this working with the HA network storage protocol set to Samba/Windows (CIFS) but it only worked after enabling NFS on my QNAP NAS.

Not sure why I needed to enable NFS then connect using CIFS but it works.