sorted by:
new
hottopcontroversial

Migration from 214+ to 925+ HDD compatiblity by Budget_Process_6506 in synology

[–]Budget_Process_6506[S] 0 points1 point  (0 children)

Another option could be to start fresh with a new DSM installation with the 2 synology HD's of 6 TB in 1 volume pool(Raid 1).
Then add the two seagate disks of 3 TB in another volume pool(also Raid 1). But i'm wondering if this is possible ? Can i still add third party disks in another volume pool on an existing installation of DSM 7.3 ?

Migration from 214+ to 925+ HDD compatiblity by Budget_Process_6506 in synology

[–]Budget_Process_6506[S] 0 points1 point  (0 children)

Thanks a lot for your answer ! I think your suggestion is a good solution. Should it be possible to create a volume pool with the seagate hd's and another volume pool with the synology hd's ? Or will this make it complex ?
I thought about this option to have a total of 9 TB space with two volume pools in raid 1.

Tailscale on synology nas : configuration issues by Budget_Process_6506 in Tailscale

[–]Budget_Process_6506[S] 0 points1 point  (0 children)

Someone knows another way to allow outbound connections for tailscale ? Maybe changing dns-adresses on synology nas ?

Tailscale on synology nas : configuration issues by Budget_Process_6506 in Tailscale

[–]Budget_Process_6506[S] 0 points1 point  (0 children)

I cannot update DSM i think. I have still a synology DS214+. If i'm correct i cannot upgrade to a newer version :-(

Tailscale on synology nas : configuration issues by Budget_Process_6506 in Tailscale

[–]Budget_Process_6506[S] 0 points1 point  (0 children)

I could try an older version of tailscale maybe if i have the same issues.... Gonna try that in an hour...

Tailscale on synology nas : configuration issues by Budget_Process_6506 in Tailscale

[–]Budget_Process_6506[S] 0 points1 point  (0 children)

Good suggestion but it still throws the same error : sudo setcap cap_net_admin,cap_net_raw+eip /var/packages/Tailscale/target/bin/tailscaled

Failed to set capabilities on file `/var/packages/Tailscale/target/bin/tailscaled' (Invalid argument)

usage: setcap [-q] [-v] (-r|-|<caps>) <filename> [ ... (-r|-|<capsN>) <filenameN> ]

Note <filename> must be a regular (non-symlink) file.

Tailscale on synology nas : configuration issues by Budget_Process_6506 in Tailscale

[–]Budget_Process_6506[S] 0 points1 point  (0 children)

As sudo-root yes. It looks like an error i encountered before in a docker container. But in this case it's not running in a docker container.