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.

In the usage scenario you described, Minio would run on the server, as a storage container and Duplicati would just run on the client machines.

Nextcloud is great as a replacement for Microsoft OneDrive or Google Drive. For periodic backups of folders with versioning across the WAN, I've been a big fan of running Minio docker on the unRAID server and using Duplicati on the clients to back up to it. The argument can also be made for running a Nextcloud docker on the unRAID server instead, and either using the nextcloud app on the client or Duplicati for the folder backups. (the nextcloud server + nextcloud app option is perhaps simpler for the client end user) There exist great tutorials for setting up nextcloud on unRAID, such as https://www.youtube.com/watch?v=fUPmVZ9CgtM

Thanks for the assistance. Would it be helpful to clarify in the wiki articles that replacing parity drive with same size is the same procedure as for replacing a data drive? (I may be slow on the uptake, but I didn't come across that info before asking it here)

So, in my case, I'd probably want to: stop array un-assign parity drive start array to forget old assignments shut down server, take out old parity drive, put new parity drive in its slot, start server stop array assign new parity drive start array to build new parity on the new drive Of course, I guess I run the risk of data loss if one of the data drives fails while the parity is being re-created. Sound about right?

Hi, my parity drive is failing, under warranty, and I'll replace it with same size/model drive. How do I do that? I've seen the wiki article about swapping for a larger parity drive, and the wiki article about replacing a data drive, but nothing about the steps for simply replacing the (single) parity drive with same size. I'm sure Unraid must make this fairly simple (as they do other drive replacements). Thank you for any assistance! Ari

https://www.mrg-effitas.com/test-library/ https://www.av-comparatives.org/test-results/ https://www.av-test.org/en/antivirus/home-windows/ Your (informed) choice.

Personally I really liked the plugin. Even though it is clear that it does not provide 100% protection, and preventing ransomware in the first place is more important, I still felt that it provided an additional layer. (seriously, we hear about a good number of malware designed to wait for a while and gather info about how to traverse any network locations available before launching an attack - so Unraid shares would be a target) Wish it still worked, but had to disable it and uninstall as it stopped working for me a few Unraid versions ago.

What have I set wrong with this plugin? I see two issues with my setup currently: 1) I still have to wait for disks to spin up when I'm browsing network shares that should be cached, and 2) the FolderCaching plugin keeps cycling my CPU seems to run for 30 seconds, takes a break, then runs another 30 seconds. I had thought that the plugin allow me to browse the network shares to see folder and files names without spinning up disks unless I actually transfer files and also would use some CPU initially to make a list of the folders and files to cache, and then stop using a lot of system resources until those folders/files are updated. I'm running unraid 6.8.3 and foldercaching 2.2.7. Here is my CPU output from NetData. You can see that I disabled the Folder Caching plugin after 08:44:00 in the graph. As soon as I turn off the plugin, the CPU goes back to normal. Here are my settings for the plugin: I've attached the size of the shares below in case needed. However, I do not have the total number of files in each share. How should I configure Folder Caching to 1) allow me to browse folders and filenames in the included shares without spinning up disks until I need a file and 2) stop using so many CPU resources? Thanks for any assistance. Ari

Alas - I thought this was such a nice idea and a really nice implementation of it. Of course, doesn't stop all ransomware attacks, but certainly better than nothing! Really too bad this is now depreciated and there isn't an alternative. (or is there an alternative?)

Alex, Just enable Docker (instructions here), install Community Applications (instructions here), and then use it to search for "moodle". This will enable you to install it as a Docker image.