psychic99

Members
  • Posts

    5
  • Joined

  • Last visited

psychic99's Achievements

Noob

Noob (1/14)

3

Reputation

  1. Seems like you can do everything in containers (there are containers for tailscale and bittorrent I use) so I would divest and use a container cluster and have unraid as the NAS. For the NAS portion your current hardware is more than capable-- an embedded board is more than enough. As for containers I use Rancher/Harvester using etcd in 3 node and you can scale them as needed.
  2. I did a little digging and it seems that Maple Ridge or Goshen Ridge (TB4) controllers are supported as of mainline kernel 5.11: Source: https://www.phoronix.com/news/Intel-Maple-Ridge-Linux There is also a document which goes deep into TB: https://stderr.nl/Blog/Hardware/Thunderbolt/TechnologyOverview.html My box on 6.1-74. I assume 6.5 is coming because this is not an LTS kernel, but good luck. I have a TB3 NVMe and a laptop w/ TB3 I may try it out this weekend if I have some time.
  3. I went into the kernel modules built in the latest unraid on my machine and here are the kernel modules compiled. You can also see the thunderbolt network service is there and the ko thunderbolt net module is also compiled in. In the case of this TB3 network adapter I don't know if it needs to load the net module or not, but it is there. You may have to load it manually though (if it is necessary). This would be interesting to see if it is actually plug and play. I have no USB4 ports to test. alias tbsvc:knetworkp00000001v*r* thunderbolt_net alias wmi:86CCFD48-205E-4A77-9C48-2021CBEDE341 intel_wmi_thunderbolt alias pci:v*d*sv*sd*bc0Csc03i40* thunderbolt LM in kernel driver: thunderbolt-net.ko.xz thunderbolt.ko.xz I am not sure USB4 is compiled into the kernel yet so the modprobe needs to know about the port and how to attach the module to it but I am unsure it will work w/ USB4 but probably a trad TB3 port. But that is conjecture because I didn't look at the kernel symbols and have no idea what the Mobo would report upon plug. With all of that said just because you CAN do it, if it's not supported by limewire then you will be on your own.
  4. First question is do you need a 10 gig NIC, and the issue among other things is B-series may at best have a TB header but it still requires a MATCHED TB card which will cost hundreds. If you want 10 gig it will be cheaper to just buy a new Mobo (you should consider Z-series) in the future as it has general better connectivity OR there are some mobo out there that have native TB3 in the mid $250+ range. So money wise it is definitely better and for compatibility to upgrade the mobo first, I'm pretty sure you cannot use TB on this board in the config you have. You could consider a mITX which has dual 2.5 and you could bond them and use scalable CIFS if that is a reason, then of course there is upgrading your entire network apparatus. 5 Gig should be enough and if you need critical work consider direct connection first.
  5. I have the DFI plugin working, and I also use luck backup to archive data off the array (which now has hash) which copies to a drive using the unassigned devices plugin. When the data gets copied over (using fuse) it archives the entire directories (cache and array) so this means newer files do not have hashes against them. What I want to do however is when they are archived to this mount point I would like to compare the hashes created w/ DFI plugin versus what has been archived for obvious reasons (if i need to restore I want a good copy!). 1. What method would recommend to do this (I am sure someone has done this) 2. Is there a reason why unassigned plugin mount points are excluded from the DFI (only disks in the array). I don't think what I am trying to accomplish is unique -- I suppose I could nix luck and go to something like rsync w/ checksum. Let me know what your thoughts are. I am simply trying to ensure what is archived is archived with 100% fidelity. BTW I also send most of this data to the cloud but the local disk is the first restore candidate. Thanks.