HumanTechDesign

As I have never seen an answer to that, but I'm still looking into this issue: Bump.

Great new updates, working flawlessly! Thank you once more! When it comes to encryption, I might have another feature request (although I'm not sure if that is something for your plugin or on the ZFS for Unraid plugin side): I have two encrypted datasets (encrypted using CLI long before your plugin was around). In order to ensure an actual at rest protection for these datasets, they need to be unmounted AND the key unloaded (see here for example). Unfortunately, Unraid does not do this by default when shutting down (based on this comment but also general first-hand experience). Therefore I have a User Script to run at array stop (containing the commands zfs unmount tank/dataset zfs unload-key -r -a and the respective opposite commands for loading the key and mounting on start of the array). However, I sometimes had the problem, that the User Script did not properly execute completely (sometimes because the device was still busy) before the server shut down, resulting in a kind of unclean shutdown (auto-starting a scrub on the next boot). My workaround so far was stopping the array manually (and waiting for correct locking of the datasets) before shutting down. I was wondering if there is a way for your plugin to communicate with Unraid to encrypt at shutdown after unmounting with a higher priority than the User Scripts plugin.

Awesome, yes, this one worked. I was apparently overcomplicating things! Also just a heads up: I was gonna report the issue that datasets with spaces in them (e.g. when there is a VM called Windows 10) weren't picked up correctly. This now apparently also seems to be solved, as it now correctly shows actually all datasets. So thank you very much once more! EDIT: Now that I'm here anyways, could I make two wishes (really not in a position to ask an open source developer, but I was thinking, maybe you could think about them) 1.) Could you think about a feature to delete multiple snapshots at once? Maybe just by having multiple checkboxes or by being able to select multiple rows in the Snapshot Admin? 2.) Maybe add another confirmation dialog when deleting a snaphot? Right now you really need to make sure that you clicked the button on the right row

Hi, first of all thank you for this great plugin! Really useful to manage snapshots etc. Concerning this new change in pattern construction: I'm not that strong in pattern matching and therefore have problems to adapt this to my setup. Could you maybe provide some basic examples for really generic use cases (e.g. excluding all datasets below a certain folder etc.)? In my case, I have my docker system share on a dedicated SSD ZFS pool. Due to the docker-ZFS implementation, it generates a dataset for every layer of all the images (see e.g. this explanation). With the previous regex, I just exluded all sub datasets below the "system" share. I now tried just the basic versions (SSDPool is my mountpoint) /SSDPool/system/ /SSDPool/system/%w+ /SSDPool/system/(%w+) but none of them matched. Is there a way to match the whole content of the system subdirectory?

Going for a long shot here, but did you ever figure out what caused this? Running into the exact same issue here!

Hey there, new Unraid user here. I'm currently in the process to plan out the further VM use of my server, I had a look at the IOMMU groups of my board. It's a ASrock B550M Steel Legend (BIOS P2.30 (February 2022)) with a Ryzen 5 Pro 4650G (Renoir). When researching the board's capabilities, I stumbled upon this post (referencing this pastebin with IOMMU groups of this board). Unfortunately, I don't know, which BIOS this is on, but generally, the groups seem quite well separated: IOMMU Group 0: 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 01:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ee] 01:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] Device [1022:43eb] 01:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43e9] 02:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea] 02:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea] 02:07.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea] 02:08.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea] 02:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43ea] 03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] [1002:67ff] (rev ff) 03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] [1002:aae0] 06:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) 07:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a) IOMMU Group 1: 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 10: 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 [1022:1440] 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 [1022:1441] 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 [1022:1442] 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 [1022:1443] 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 [1022:1444] 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 [1022:1445] 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 [1022:1446] 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 [1022:1447] IOMMU Group 11: 09:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function [1022:148a] IOMMU Group 12: 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] IOMMU Group 13: 0a:00.1 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP [1022:1486] IOMMU Group 14: 0a:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] IOMMU Group 15: 0a:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487] IOMMU Group 2: 00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] 00:03.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge [1022:1483] 08:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) 08:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] [1002:aaf0] IOMMU Group 3: 00:04.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 4: 00:05.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 5: 00:07.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 6: 00:07.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU Group 7: 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge [1022:1482] IOMMU Group 8: 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] [1022:1484] IOMMU Group 9: 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51) I now have my board here and in the process of preparing it, I updated the BIOS to Version P2.30 (February 2022). I forgot to have a look at the IOMMU groups before flashing, but right now, Unraid lists the following devices for me (which looks way worse to me): IOMMU group 0: [1022:1632] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge IOMMU group 1: [1022:1632] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1634] 00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:1634] 00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge [1022:43ee] 01:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43ee Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 004: ID 26ce:01a2 ASRock LED Controller Bus 001 Device 005: ID 0781:556b SanDisk Corp. Cruzer Edge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub [1022:43eb] 01:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43eb [1:0:0:0] disk ATA Samsung SSD 870 1B6Q /dev/sdb 500GB [2:0:0:0] disk ATA Samsung SSD 870 1B6Q /dev/sdc 500GB [3:0:0:0] disk ATA ST18000NM000J-2T SN02 /dev/sdd 18.0TB [4:0:0:0] disk ATA ST18000NM000J-2T SN02 /dev/sde 18.0TB [1022:43e9] 01:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43e9 [1022:43ea] 02:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea [10ec:8125] 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) [144d:a808] 04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [N:0:4:1] disk Samsung SSD 970 EVO Plus 1TB__1 /dev/nvme0n1 1.00TB IOMMU group 2: [1022:1632] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1635] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1002:1636] 05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir (rev d9) [1002:1637] 05:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 1637 [1022:15df] 05:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:1639] 05:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub Bus 003 Device 003: ID 0463:ffff MGE UPS Systems UPS Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub [1022:1639] 05:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1 Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 006 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive [1022:15e3] 05:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller IOMMU group 3: [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 4: [1022:1448] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 0 [1022:1449] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 1 [1022:144a] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 2 [1022:144b] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 3 [1022:144c] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 4 [1022:144d] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 5 [1022:144e] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 6 [1022:144f] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 7 I currently have no dGPU installed, but I was thinking about passing trough the front USB IO Hub (and possibly other stuff). I am of course aware of the possibilities to break up the groups via the different methods (the classic https://www.youtube.com/watch?v=qQiMMeVNw-o), but I'm just a little surprised to see such strong differences in grouping. As I'm rather new to the topic, I was wondering, which factors actually influence the groupings. CPU? Kernel? Or basically only Chipset and corresponding BIOS? Would you expect the BIOS update (as I said, unfortunately, I did not check prior to flashing) to make groupings so much worse or did I just miss something in the configuration? Thanks in advance!

Hey there, Unraid newcomer here. I'm currently in the process of migrating from a Syno over to Unraid. One of the reasons was the plan to share (and receive) large files from users outside my home network. With the Syno box I did not share any services directly to the outside but rather had a VPN running on my (edge, bare metal) pfsense but I was thinking, that I might now find a solution with the shiny new server. With Unraid I had a feeling that it was somehow almost "common practice" to make containers (such as Nextcloud, Plex etc.) available trough a proxy. However, in my eyes, this does not solve the problem of eventually being subject to brute force attempts (or worse). I know of the approach of using the Argo/CF tunnel to avoid having open ports to the outside. Nevertheless, the actual line of defense is still the HTTP Auth in the proxy and/or the login screen of the application. In my eyes, this still seems like a problem, if an exploit within those applications is discovered. Therefore I was thinking about segregating private and public services by actually duplicating the dockers (i.e. having a "public" Nextcloud exposed to the Internet and a "private" Nextcloud only available locally) and also having separate shares that they can access. However, as I'm not that deep in the docker space, I don't know, if this is best practice, if it creates a big (MGMT and processing) overhead to have multiple instances of the same container and if it actually brings any security advantage. Therefore, I'm looking for answers to the following questions: 1.) Is there any security benefit of running the same service in two different container instances and subnets? I especially want to prevent "container breakout" (between containers but also to the host)? (I already know of this thread, but I just want to know if there are other vectors such as Dirty Pipe and its - possible - threats or the general "plugins as root" problem) 2.) Is there a better way to achieve the possibility to make certain services availble to the public while at the same time making sure that the "most precious" private data stays safe from stuff like ransomware, hackers gaining root within a container etc. If there is no good answer to these questions I might stay with my stance on just running everything only locally behind the firewall etc. but maybe I'm just missing something or you have good arguments why the points are listed are not actually problems. Thanks in advance!!!