#Supervisor holding on to old network path for frigate, won't let me create a new one

1 messages · Page 1 of 1 (latest)

shut lodge
#

I'll continue this in a thread. After getting that message I added an empty file at /mnt/data/supervisor/.mounts_credentials/frigate to see what if it would move past it. I tried re-adding the new network storage (which is at a new IP address, as the old NAS isn't available), and it gave me the following error in the Hosts log:

Jan 09 22:00:11 homeassistant systemd[1]: Mounting Supervisor cifs mount: frigate...
Jan 09 22:00:11 homeassistant kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
Jan 09 22:00:11 homeassistant kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers
Jan 09 22:00:11 homeassistant kernel: CIFS: Attempting to mount \192.168.1.214\Volume_1
Jan 09 22:00:15 homeassistant mount[2126467]: Password for root@//192.168.1.214/Volume_1\frigate:
Jan 09 22:00:15 homeassistant mount[2126466]: mount error(113): could not connect to 192.168.1.214Unable to find suitable address.
Jan 09 22:00:15 homeassistant kernel: CIFS: VFS: Error connecting to socket. Aborting operation.
Jan 09 22:00:15 homeassistant kernel: CIFS: VFS: cifs_mount failed w/return code = -113
Jan 09 22:00:15 homeassistant systemd[1]: mnt-data-supervisor-mounts-frigate.mount: Mount process exited, code=exited, status=32/n/a
Jan 09 22:00:15 homeassistant systemd[1]: mnt-data-supervisor-mounts-frigate.mount: Failed with result 'exit-code'.
Jan 09 22:00:15 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: frigate.

#

What's notable about this is that the IP address in this error (192.168.1.214) is the old NAS address. The new address I tried to configure is at 192.168.1.104. Somehow, some part of the supervisor has help onto the old NAS IP address, and associated it with the network storage share named 'frigate'. I can't create a new folder anywhere in the system (local or network) with the name 'frigate' while this is happening, and without a folder named 'frigate', and I can't seem to get Frigate to run.

#

Is there somewhere else I can look to see where HA is holding on to this mapping?