adoucette

@SpaceGator - agree. I was also interested in same so I reached out to SwissBit tech support. Unfortunately they told me that those do not have a unique GUID: ("No unique GUID for each drive" seems to be the most likely interpretation of what they told me. The reply could really be interpreted either as that, or as "Each individual drive has a unique GUID, but it is not unique to every model number." Perhaps that clarity and resulting specificity was lost in translation.)

I just received ONE of the following devices: https://www.amazon.com/dp/B092DDRRRQ Unraid thought it was a unique GUID. I've moved an existing Unraid install and license key to it without problem. However, just as above, let the buyer beware. I only purchased one of them, and I cannot be sure that others will be unique (who knows? maybe I was simply the first to try to move Unraid onto one of these?).

I had assumed that because the poster was listed as an "administrator" on the forum and posting that "we've been internally testing and vetting" the devices that it was advice coming from Unraid's internal team and the device would work. Add this user to the list who bought the recommended device and found the GUID had already been blacklisted (used). Overall not too much $ lost I suppose, just $30 on Amazon for the device (plus $11 for a (really nice) enclosure for it). Unraid has been worth that and more, IMO. The post now says "caveat emptor". I would humbly suggest the admin team "caveat postor" to prevent similar in future.

@Miss_Sissy your .stl file worked perfectly to house the referenced parts. Just arrived. Thanks for sharing.

Too bad - that's exactly what I just purchased as well as got case printed for.

Downloaded the .stl files from Thiniverse, ordered them for printing from Craftcloud, total only $11 after production and shipping. Thank you Missy. Will donate to a local charity per your suggestion. Ari

@JonathanM Are you willing to share the .stl file for this? Perfect timing as my Samsung Bar 64GB USB stick just died after two years' use.

Yes! That's exactly it. I had only seen how to assign different models to different TPUs in the coral docs. Glad this was in the docs for Frigate. detectors: coral1: type: edgetpu device: pci:0 coral2: type: edgetpu device: pci:1 After saving this in the config.yml a d rebooting, Frigate shows both TPUs and a faster inference. Thanks for pointing me in the right direction.

I have just moved from the Coral USB accelerator to the Dual TPU using the Magic Smoke pci-e adapter plugged into a pcie x16 port on my motherboard. How do I ensure I'm using both TPUs in the Unraid Frigate docker? My Frigate Docker config has: Coral TPU Mapping: /dev/apex_0 My appdata/frigate config.yml file has: detectors: coral: type: edgetpu device: pci Using the ich777's Coral Accelerator Module Drivers, I can see both TPUs listed. How do I ensure (or configure) Frigate to use both TPUs? Thanks in advance, Ari

Hello, Does it matter that my array lists just parity and disks 3 and 5 (instead of 1 and 2), and my cache lists cache and cache 3? This came about after I replaced array 5x4TB drives with 3x14TB drives and upgraded the old cache drives. If it does matter, now or in future, how should I go about reconciling / re-enumerating (?) them? Thanks, Ari

Agree. I wish this plug in still was maintained and worked.

How do I go about standing up a new version as a docker in Unraid if new versions won't start because of this file system error? Is this just some config changes when I install the new docker instance?

For me, I just used the on board NIC and then later switched to a motherboard with Intel NICs on board.

I have a similar thought - as well as considering "/mnt/user" to be an important folder to be able to cache

+1 for that. I really hope that it can work again with mnt/user sometime soon.