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

Configuration
1

Dear community

image
image604×903 47.6 KB

Running system on Proxmox VM
HAOS 16.0
HA Core 2025.7.3

I had the NFS-Shares working, suddenly after some reboots to try some adaption in configuration.yaml I lost the NFS-Shares and could not restore the share in HA.
Renaming the Name of the Network-Storage did not helped, as I was reading in a different thread somewhere else.

A look in the protocol does show the failure below
Logger: homeassistant.components.hassio
Quelle: components/hassio/websocket_api.py:145
Integration: Home Assistant Supervisor (Dokumentation, Probleme)
Erstmals aufgetreten: 19:32:45 (4 Vorkommnisse)
Zuletzt protokolliert: 23:35:00

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

The NFS-Shares are still accessable from my laptop, I can read and write on the shares on the external server.

Attached you can find the /etc/exports from the NFS-Server
/export/bilder 192.168.1.0/24(rw,sync,no_subtree_check)
/export/daten 192.168.1.0/24(rw,sync,no_subtree_check)
/export/ha_backup 192.168.1.0/24(rw,sync,no_subtree_check)
/export/ha_camera 192.168.1.0/24(rw,sync,no_subtree_check)
#/export/movies 192.168.1.0/24(rw,sync,no_subtree_check)
/export/public 192.168.1.0/24(rw,sync,no_subtree_check)

/export 192.168.1.0/24(rw,sync,fsid=0,crossmnt,no_subtree_check)

Any Idea what to do?
Thank you for your help

2

Have you tried restarting home assistant?

3

Hello Tom.
Each server was restartet serveral times, sorry that I forgot to mention it directly.
HA was completly restartet, NFS Server rebootet.

I have a complete backup from HA from the day before, where the NFS shares were working. I restored the backup and the failure is still present.
Therefore I consider it as system issue from Linux (Alpine) host, but I do not know yet where to search.

Regards

4

Dear all,
summary of my activities.
It seems that the NFS-Unmount was not performed in propper manner during the reboot. Therefor a hidden mount lock was still existing even if the system was shut-down.
With ssh account to HA shell, I stopped manually any share and mount option, deleted the mount points and rechecked if any files left at the mount points.
After I changed to Samba Shares, then I could establish the network storage for backup and media.
This isn’t a satisfactory process, as I could not investigate the real issue.
Bottom line it seems the NFS share weak with Home Assistant.

Dancing Samba might have more swing and spirit than a boaring NFS.

Issue not solved but closed for me.
Any comments are highly welcome

Regards

5

You should open an issue for that. GitHub · Where software is built

6

I have this issue now too but how do i fix it as im not as clued up on this, step by step for a dummy would be appreciated

7

Dear Mat,
Sorry for late response as I was not aware of your question.
As I am right now in vacation I cannot give for this weekend any proposal
I need to check the different steps and try summarize early next week.
What I can tell I asked AI for any suggestions based on the command line information.
Regards

8

Hey bud, I still not been able to get it working again but i will try the AI thing tonight. Thanks for the reply i appreciate it as its doing my head in

9

Hello Mat, sorry for beeing this late, I had some major issues to repair.
So I tried to retrace the steps I did

At my NFS-Server (Debian 12):
Stopped all my services
sudo systemctl stop nfs-kernel-server
sudo systemctl disable nfs-kernel-server

in case still existing /media/deb_nfs_bilder or similar
sudo umount /media/deb_nfs_bilder 2>/dev/null
sudo rm -rf /media/deb_nfs_bilder

With this steps I stopped all NFS-services and I removed on my Proxmox Debian VM the packages related to NFS

Further steps I opened the console (via ssh) on homeassistent server and checked for any mounts
ha mounts info

try to enforce the unmount of the folder deb_nfs_bilder
ha mounts reload
ha mounts remove deb_nfs_bilder

in case unmount not successful
ha mounts unmount deb_nfs_bilder`

manually check for mount-folder still existing
ls -la /media/deb_nfs_bilder

clear the folders and remove old files in case still existing
umount /media/deb_nfs_bilder 2>/dev/null
rm -rf /media/deb_nfs_bilder

then I checked again on homeassistent server if this file exists /mnt/data/supervisor/mounts.json
cat /mnt/data/supervisor/mounts.json

In case your shared folder is mentioned, delete it manually, reboot.
The issue I could solve by applying all above steps. Now I use SAMBA server instead.