I actually got it to work! For others with a Intel NUC and for future me in 10-20 years if I make it that long attached are the Configuration setting that worked on my system and a screenshot of the actual mapped drive. I think the main thing that got it going was deleting the mountoptions* (nosuid, relatime, noexec, X) that came preloaded with the Addon. Thank you Lucio for this great addon!
Great Addon!
After fixing all problems (gpt, label) my disc is recognized perfectly.
I want to use my second disk for frigate addon recordings. But frigate is pointing on /root/media/frigate with lower case. Samba NAS is creating /root/media/FRIGATE with upper case.
Label of file systems is “frigate”.
Any idea to solve that?
I already tried to set a symbolic link with “ln -s”. But I figured out that symbolic links to smb shares are not supported.
Is there any mount option like “everything in lower case”?
Hello, what about speed? Are there any config options or future updates to speedup connection to the drive slightly?
I know Samba is not the fastest way of sharing files but still I know that
You can have more speed in Samba share inside OMV.
socket options = TCP_NODELAY SO_RCVBUF=65536 SO_SNDBUF=65536
read raw = yes
write raw = yes
max xmit = 65535
dead time = 15
getwd cache = yes
Can we somehow use it in our addon?
Did you ever get the drive to spin-down correctly? I have a 5TB Seagate that never spins down when connected to my Intel NUC but spins down when I connect it to my Asus router.
Hi, thank you for this great addon 
.
I just started to use it as m my pi3/openmediavault does not boot anymore
It works fine with my two usb ntfs disk on my fanless mini Pc with haos.
I’have seen that ntfs is experimental in the starting log.
For me and all the readers information , what are the possible issues please ?
Thank you so much for this addon. I have it working on a 1TB HDD, and I recently purchased a 10TB to replace it, but am struggling to get it loaded into Samba NAS and need some assistance troubleshooting.
I deleted all partitions from the drive, created a single ext4 partition that fills as much of the drive as possible labeled “frigate”, and I get the below error when loading up Samba NAS. It correctly finds “frigate” earlier on in the logs, and I can see the USB device under the hardware tab so I know it’s being read. None of my Samba NAS configuration settings changed when I swapped over from the old HDD. I’ve also tried partitioning the drive using Gparted and Minitool Partition Wizard with similar results.
Am I supposed to leave a small portion of the HDD unallocated or something?
[07:14:17] ERROR: Got unexpected response from the API: Reloading FRIGATE did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-FRIGATE.mount for details.
[07:14:17] WARNING: Retry 1/3 Error Automount FRIGATE Msg: {"name":"FRIGATE","usage":"media","type":"cifs","server":"172.30.32.1","share":"FRIGATE","username":"_ha_mount_user_","password":"********"}
[07:14:18] ERROR: Got unexpected response from the API: Reloading FRIGATE did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-FRIGATE.mount for details.
[07:14:18] WARNING: Retry 2/3 Error Automount FRIGATE Msg: {"name":"FRIGATE","usage":"media","type":"cifs","server":"172.30.32.1","share":"FRIGATE","username":"_ha_mount_user_","password":"********"}
[07:14:19] ERROR: Got unexpected response from the API: Reloading FRIGATE did not succeed. Check host logs for errors from mount or systemd unit mnt-data-supervisor-mounts-FRIGATE.mount for details.
[07:14:19] WARNING: Retry 3/3 Error Automount FRIGATE Msg: {"name":"FRIGATE","usage":"media","type":"cifs","server":"172.30.32.1","share":"FRIGATE","username":"_ha_mount_user_","password":"********"}
Here are the logs from Host:
2024-10-12 11:14:11.587 homeassistant kernel: audit: type=1334 audit(1728731651.585:7385): prog-id=1615 op=UNLOAD
2024-10-12 11:14:12.641 homeassistant kernel: EXT4-fs (sdb1): mounted filesystem 30cde37a-1a36-b541-8d56-22e68e076cc0 r/w with ordered data mode. Quota mode: none.
2024-10-12 11:14:17.614 homeassistant systemd[1]: Mounting Supervisor cifs mount: FRIGATE...
2024-10-12 11:14:17.615 homeassistant mount[2559291]: error 2 (No such file or directory) opening credential file /mnt/data/supervisor/.mounts_credentials/FRIGATE
2024-10-12 11:14:17.617 homeassistant systemd[1]: mnt-data-supervisor-mounts-FRIGATE.mount: Mount process exited, code=exited, status=2/INVALIDARGUMENT
2024-10-12 11:14:17.617 homeassistant systemd[1]: mnt-data-supervisor-mounts-FRIGATE.mount: Failed with result 'exit-code'.
2024-10-12 11:14:17.617 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: FRIGATE.
2024-10-12 11:14:18.734 homeassistant systemd[1]: Mounting Supervisor cifs mount: FRIGATE...
2024-10-12 11:14:18.742 homeassistant mount[2559306]: error 2 (No such file or directory) opening credential file /mnt/data/supervisor/.mounts_credentials/FRIGATE
2024-10-12 11:14:18.746 homeassistant systemd[1]: mnt-data-supervisor-mounts-FRIGATE.mount: Mount process exited, code=exited, status=2/INVALIDARGUMENT
2024-10-12 11:14:18.746 homeassistant systemd[1]: mnt-data-supervisor-mounts-FRIGATE.mount: Failed with result 'exit-code'.
2024-10-12 11:14:18.747 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: FRIGATE.
2024-10-12 11:14:19.863 homeassistant systemd[1]: Mounting Supervisor cifs mount: FRIGATE...
2024-10-12 11:14:19.868 homeassistant mount[2559321]: error 2 (No such file or directory) opening credential file /mnt/data/supervisor/.mounts_credentials/FRIGATE
2024-10-12 11:14:19.870 homeassistant systemd[1]: mnt-data-supervisor-mounts-FRIGATE.mount: Mount process exited, code=exited, status=2/INVALIDARGUMENT
2024-10-12 11:14:19.870 homeassistant systemd[1]: mnt-data-supervisor-mounts-FRIGATE.mount: Failed with result 'exit-code'.
2024-10-12 11:14:19.871 homeassistant systemd[1]: Failed to mount Supervisor cifs mount: FRIGATE.
Any help would be greatly appreciated!
EDIT: I spent an entire night trying to figure this out, and 10 minutes after posting this, I learned that I had to physically power cycle the host machine by pressing the power button on my NUC. Frustrating when the fix is that simple, but boy is it satisfying to have this back up and running! Thank you for this contribution to the community!!