supervisor: Re-adding Network Storage with same name fails

Describe the issue you are experiencing

I previously had a NAS set up to save my frigate data to. The name MUST be “frigate” in order for the add-on to function properly. I previously had this set up and working properly, but upgraded to a different NAS recently. After deleting the original network storage, rebooting, and going to re-add it with the new server and share it fails indefinitely. Changing the name to anything other than a previously used name works flawlessly.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Steps to reproduce the issue

1. Add a network storage
2. Delete the network storage
3. Reboot host
4. Add a network storage with the same name as step 1, but different server/share (should fail to add)

Anything in the Supervisor logs that might be useful for us?

23-09-24 13:06:34 ERROR (MainThread) [supervisor.mounts.mount] Reloading frigate did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-frigate.mount for details.
23-09-24 13:06:34 ERROR (MainThread) [supervisor.mounts.mount] Could not unmount frigate due to: Transaction for mnt-data-supervisor-mounts-frigate.mount/stop is destructive (mnt-data-supervisor-mounts-frigate.mount has 'start' job queued, but 'stop' is included in transaction).

System Health information

System Information

version	core-2023.9.2
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.11.5
os_name	Linux
os_version	6.1.45
arch	x86_64
timezone	America/Chicago
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
GitHub API Calls Remaining	4966
Installed Version	1.32.1
Stage	running
Available Repositories	1363
Downloaded Repositories	36

Home Assistant Cloud

logged_in	true
subscription_expiration	May 6, 2024 at 7:00 PM
relayer_connected	true
relayer_region	us-east-1
remote_enabled	true
remote_connected	true
alexa_enabled	false
google_enabled	false
remote_server	us-east-1-2.ui.nabu.casa
certificate_status	ready
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 10.5
update_channel	stable
supervisor_version	supervisor-2023.09.2
agent_version	1.5.1
docker_version	23.0.6
disk_total	78.0 GB
disk_used	37.7 GB
healthy	true
supported	true
board	ova
supervisor_api	ok
version_api	ok
installed_addons	Mosquitto broker (6.3.1), Ring-MQTT with Video Streaming (5.6.2), File editor (5.6.0), Terminal & SSH (9.7.1), Node-RED (14.5.0), Z-Wave JS UI (1.16.0), PS5 MQTT (1.3.1), Network UPS Tools (0.12.1), Crowdsec (1.5.2-ha1), ESPHome (2023.8.3), Double Take (1.13.1), Exadel CompreFace (1.1.0), Frigate Beta (0.13.0) (0.13.0-beta1)

Dashboards

dashboards	2
resources	20
views	11
mode	storage

Recorder

oldest_recorder_run	July 26, 2023 at 3:11 PM
current_recorder_run	September 24, 2023 at 1:12 AM
estimated_db_size	2585.71 MiB
database_engine	sqlite
database_version	3.41.2

Supervisor diagnostics

No response

Additional information

Not isolated to frigate, I did the same thing with my backups. Removed old and added new with the same name and received the exact same errors. Simply changing the name from “Backups” to “Backups_2” resolved the issue for this instance. As mentioned previously, this cannot be done for frigate as it is a requirement of the add-on for it to be named “frigate”.