Sissy

No problem at all. I'm grateful whenever someone finds the time to assist me. I will have to do learn Unraid's routing UI. I'm guessing it can't be that different than pfSense and my EdgeRouter 4. With a dynamic IP address as the end-point, I'm going to have to think about how to handle the routing. It's a shame I can't just check a box that says "accept tunnel open requests on any NIC and reply out the same NIC through which the tunnel was opened."

Thanks for your reply. Feature request: With multiple NICs being common, users should be able to assign to which NIC WireGuard tunnels connect, even if they can only pick a single NIC for all WireGuard tunnels. I have two connections, a 940/880 Mbps (down/up) residential Internet connection and a 50/10 Mbps business Internet connection. The former has a dynamic IP and terms of service that prohibit running servers (think VPN) while the latter has multiple static IPs and permits servers of any kind. I don't want my Unraid box using up the very limited bandwidth of the business connection, or taking the massive performance hit. Therefore, I had set the metric on the residential gateway lowest. But I do want WireGuard on the business connection with a static IP address (via NAT port forwarding). While I would like to have a Wireguard tunnel available on the residential connection, it would be for emergency use only, such as when I am out of town and there's been some sort of network outage on the business side. That would be unlikely to be detected as a server with only sporadic, personal use.

Is there anyone offering paid support for WireGuard in Unraid? I have asked this question three times in the forums and once in a private DM to bonienl and have not received even a single answer.

I've had no success at getting questions answered about multi-NIC Unraid WireGuard installations. I've posted here and here in this thread and had zero responses, publicly or privately. I also private-messaged bonienl, author of the WireGuard plugin, more than a week ago. Although he has been logged on since then, I've not had any response from him, either. I've not seen any information on how to, or if you can, selectively bind an instance of WireGuard to a particular NIC. Based on my experimentation, it appears to attach itself to whatever NIC attached to the gateway with the lowest metric. In my case, I have two NICs attached to two different network segments, each with its own gateway (Verizon on one, Cox on the other). I want to bind WireGuard to each NIC so that I have redundant paths into my local network so that a single point of failure cannot lock me out when I am operating remotely. Maybe as time goes on, mechanisms to do what we want, and/or documentation as to how to do it, will be developed.

Ping. Anyone?

Dual-homed Unraid NAS (version 6.9.2) with WireGuard (plugin version 2021.04.12) tunnels on each of the two Ethernet adapters? I have an Unraid NAS with two Ethernet adapters. One adapter connects to a Verizon FIOS residential network segment (192.168.1.0/24) and the other connects to a Cox Business Services network segment (192.168.0.0/24). I would like to have WireGuard VPN tunnels on both of the Unraid NAS Ethernet adapters so that I can remotely tunnel in on either network connection (think failure of a router, firewall, cable modem, ONT, etc.). I can't see a way to bind tunnel wg0 to eth 0 and tunnel wg1 to eth 1. It appears that the WireGuard plugin attaches any tunnel created to the Ethernet adapter attached to the gateway with the lower metric. If a VPN tunnel is established on the Cox Business Services Ethernet adapter (eth 0), I want WireGuard to use the Cox gateway associated with that adapter. If it comes in on the Verizon side, I want the Verizon gateway used. Thanks in advance for any assistance.

Thank you. Based on the title of the thread, "WIREGUARD - VPN TUNNELED ACCESS," it appeared to be about the topic I was interested in -- tunneled access to my networks via WireGuard. I will repost my question at the link you provided.

Dual-homed Unraid NAS (version 6.9.2) with WireGuard (plugin version 2021.04.12) tunnels on each of the two Ethernet adapters? I have an Unraid NAS with two Ethernet adapters. One adapter connects to a Verizon FIOS residential network segment (192.168.1.0/24) and the other connects to a Cox Business Services network segment (192.168.0.0/24). I would like to have WireGuard VPN tunnels on both of the Unraid NAS Ethernet adapters so that I can remotely tunnel in on either network connection (think failure of a router, firewall, cable modem, ONT, etc.). I can't see a way to bind tunnel wg0 to eth 0 and tunnel wg1 to eth 1. It appears that the WireGuard plugin attaches any tunnel created to the Ethernet adapter attached to the gateway with the lower metric. If a VPN tunnel is established on the Cox Business Services Ethernet adapter (eth 0), I want WireGuard to use the Cox gateway associated with that adapter. If it comes in on the Verizon side, I want the Verizon gateway used. Thanks in advance for any assistance.

I'm fine with LimeTech charging subscription fees for any kind of service, whether cloud-based backup, priority access to tech support, or any other service for which they incur ongoing costs. I hope such services are made available to licensees as well as future customers who choose to acquire Unraid through subscriptions. As long as LimeTech continues to offer traditional (non-subscription) Unraid OS licenses that include access to all 'core OS features' and upgrades, I will be rooting for them as they expand their customer base and revenue stream through subscription offerings. After all, it's in my best interests as a customer for LimeTech to be a thriving, profitable business.

No, we really got burned by a bunch of greedy companies, many of which started out by pushing subscriptions as options only to later remove the ability to buy traditional licenses. I have two packages I can think of right now where the publishers removed features and then charged customers subscription fees to get the features back. You say "of course," but you are the first person to clearly articulate what LimeTech means by a 'core' feature of the OS versus a "premium feature." Cloud-based backups was another example I had actually written up but deleted for brevity when I was citing things that might be examples of premium features. I'm okay with what you describe above and I think that most people would be. I think it's a mistake to refer to "premium features" and I would consider coining another term like "hosted features." I think it's important to tell traditional license holders that they will have access to all of the subscription-based features so long as they pay the associated subscription fees. So if I want a subscription to a year's worth of tech support, then I pay $X for it, regardless of whether I have Unraid through a traditional license or a monthly subscription (just to cite one example). Thank you for addressing my questions and concerns.

Fast forward four months: Which is it? Will customers who bought licenses still get "all future upgrades and features" or are there going to be new, "premium features" developed which will only be available to subscribers? Every major upgrade of Unraid has included "features not already included with the [prior version of] the OS." In the future, would such new features be termed "premium features" only available to subscribers? Finally, are we conflating "features" with "services"? I'm fine with there being a subscription offered for direct access to priority tech support, for example. But I'm not fine with discovering one day that ZFS is available on Unraid -- but only to subscribers. Thanks for considering my concerns.

I did as you directed and it worked perfectly! Unraid rebooted and immediately flagged the drive's health after providing a notification of the reallocated sector. Here's the file before and after acknowledging the condition: [email protected]:/boot/config/plugins/dynamix# cat monitor.ini [smart] cache.5="1" [email protected]:/boot/config/plugins/dynamix# cat monitor.ini [smart] cache.5="1" cache.ack="true" Thanks again. It would have taken me a long time to find that without your help. That's a supercomputer compared to my Thecus N5550 Unraid box! Atom D2550 vs. Intel Celeron J1800 My Thecus box is only dealing with two parity, three data drives, and a single cache SSD. It pretty much saturates gigabit, but it can't do any virtualization (I just want it to be a simple NAS, though). It looks like your DOM is a USB device that plugs into what seems to be a standard, two-row, dual-port USB header on the motherboard. I guess you could put your Unraid boot drive into that header using an appropriate, USB-A-terminated cable. I feel better with my Thecus DOM in an anti-static bag -- rather than plugged into the box, awaiting something stepping on it or the BIOS deciding to boot from it (think dying button cell battery). That it gives me a SATA port for the SSD is just a plus. My QNAP is a TS-853A, BTW. Thanks again.

Thank you, that's exactly what I wanted! I really appreciate all of your effort. I'll let you know how it goes. Which QNAP model?

You might want to back off on the condescension. I started working with hard drives when they had physical labels that listed the bad sectors; you would type in the list when initializing the drives. You can just see the corner of a metal computer case in background of that photo -- it's a CP/M-80 Z80 system that I built, initially with floppies and later upgraded with a 5MB (yes, megabyte), Tandon TM501, 5.25", full-height, drive interfaced to the computer with an MFM-to-SCSI adapter. I built that computer before IBM released a PC. I was already an embedded systems engineer at that time. The drive in question, a Samsung 840 EVO 1TB SSD (mentioned above), doesn't even report those attributes! Samsung's white paper entitled Using SMART Attributes to Estimate Drive Lifetime: Increase ROI by Measuring the SSD Lifespan in Your Workload says that "the most important indicators of drive health [on Samsung SSDs] are attributes 179, 181, 182, and 183." I think that I'll follow Samsung's guidance -- at least the attributes they identify are actually reported by the drive. Going forward, I will avail myself of this forum's "poll" feature should I seek community input on best-practices for running my Unraid server. Thank you for your input.

No problem at all; I appreciate your help. I didn't take any action yet based on the content of the file. I'm not in a hurry, so let me know whenever it's convenient for you.

I've got an 8-bay QNAP and it's working fine. The Thecus, on the other hand, is pretty much abandoned with no software updates in years. I took out the DOM, built a power cable, and attached my 1TB Samsung 840 EVO in its place. Thecus was kind enough to pre-punch holes in the top to screw a 2.5" drive up there. (see attached photo) Looking at disk.cfg, I do wonder if deleting it would cause me to have to reconfigure a boatload of stuff. Also, I'm not seeing any line that looks like it's related to the acknowledgement of the thumbs down health status. But I'll have to try it later. # Generated settings: startArray="no" spindownDelay="1" queueDepth="auto" spinupGroups="yes" defaultFormat="2" defaultFsType="xfs" shutdownTimeout="90" luksKeyfile="/root/keyfile" poll_attributes="1800" nr_requests="Auto" md_scheduler="auto" md_num_stripes="1280" md_queue_limit="80" md_sync_limit="5" md_write_method="auto" diskComment.0="" diskFsType.0="auto" diskSpindownDelay.0="-1" diskSpinupGroup.0="" diskComment.1="" diskFsType.1="xfs" diskSpindownDelay.1="-1" diskSpinupGroup.1="" diskExport.1="e" diskFruit.1="no" diskCaseSensitive.1="auto" diskSecurity.1="public" diskReadList.1="" diskWriteList.1="" diskVolsizelimit.1="" diskExportNFS.1="-" diskSecurityNFS.1="public" diskHostListNFS.1="" diskExportAFP.1="-" diskSecurityAFP.1="public" diskReadListAFP.1="" diskWriteListAFP.1="" diskVolsizelimitAFP.1="" diskVoldbpathAFP.1="" diskComment.2="" diskFsType.2="xfs" diskSpindownDelay.2="-1" diskSpinupGroup.2="" diskExport.2="e" diskFruit.2="no" diskCaseSensitive.2="auto" diskSecurity.2="public" diskReadList.2="" diskWriteList.2="" diskVolsizelimit.2="" diskExportNFS.2="-" diskSecurityNFS.2="public" diskHostListNFS.2="" diskExportAFP.2="-" diskSecurityAFP.2="public" diskReadListAFP.2="" diskWriteListAFP.2="" diskVolsizelimitAFP.2="" diskVoldbpathAFP.2="" diskComment.3="" diskFsType.3="xfs" diskSpindownDelay.3="-1" diskSpinupGroup.3="" diskExport.3="e" diskFruit.3="no" diskCaseSensitive.3="auto" diskSecurity.3="public" diskReadList.3="" diskWriteList.3="" diskVolsizelimit.3="" diskExportNFS.3="-" diskSecurityNFS.3="public" diskHostListNFS.3="" diskExportAFP.3="-" diskSecurityAFP.3="public" diskReadListAFP.3="" diskWriteListAFP.3="" diskVolsizelimitAFP.3="" diskVoldbpathAFP.3="" diskComment.29="" diskFsType.29="auto" diskSpindownDelay.29="-1" diskSpinupGroup.29="" cacheId="Samsung_SSD_840_EVO_1TB_S1D9NEAD932978J" cacheFsType="btrfs" cacheComment="" cacheSpindownDelay="-1" cacheSpinupGroup="host3" cacheUUID="b708b8bc-d59a-499e-8daa-3e3a8b6282f2" cacheExport="e" cacheFruit="no" cacheCaseSensitive="auto" cacheSecurity="public" cacheReadList="" cacheWriteList="" cacheVolsizelimit="" cacheExportNFS="-" cacheSecurityNFS="public" cacheHostListNFS="" cacheExportAFP="-" cacheSecurityAFP="public" cacheReadListAFP="" cacheWriteListAFP="" cacheVolsizelimitAFP="" cacheVoldbpathAFP=""

Thank you! I don't rm, I mv -- momma didn't raise no fools! My Unraid box (repurposed Thecus N5550) is doing a parity check right now, so I'll let that finish before I start experimenting, rebooting, etc. Really appreciate the help.

Thanks Vr2lo! Here's the output of the ls command on /boot/config: [email protected]:/boot/config# ls -lrt total 88 drwx------ 2 root root 4096 Nov 30 06:15 wireguard/ drwx------ 2 root root 4096 Nov 30 06:15 ssh/ -rw------- 1 root root 33 Nov 30 06:15 machine-id -rw------- 1 root root 169 Nov 30 06:16 docker.cfg drwx------ 3 root root 4096 Nov 30 06:16 ssl/ -rw------- 1 root root 256 Nov 30 06:16 Trial.key -rw------- 1 root root 119 Nov 30 06:18 flash.cfg -rw------- 1 root root 106 Nov 30 07:13 network.cfg -rw------- 1 root root 71 Nov 30 07:13 go drwx------ 2 root root 4096 Nov 30 18:04 shares/ -rw------- 1 root root 378 Dec 7 15:39 network-rules.cfg -rw------- 1 root root 7 Dec 9 16:13 drift -rw------- 1 root root 512 Dec 9 17:49 random-seed drwx------ 2 root root 4096 Dec 9 18:42 plugins-removed/ drwx------ 8 root root 4096 Dec 9 18:42 plugins/ -rw------- 1 root root 33 Dec 9 18:56 smart-all.cfg -rw------- 1 root root 714 Dec 9 18:57 ident.cfg -rw------- 1 root root 577 Dec 9 18:57 share.cfg -rw------- 1 root root 2411 Dec 9 20:48 disk.cfg -rw------- 1 root root 199 Dec 10 06:46 domain.cfg -rw------- 1 root root 4096 Dec 10 11:53 super.dat -rw------- 1 root root 796 Dec 10 11:53 parity-checks.log

No one knows?

You are correct and that aligns with what I know about SMART attributes. (Don't get me started about the stupidity of not being able to clear UDMA CRC errors -- which are almost always caused by bad cables or connectors. I've got a perfectly healthy drive with a bunch of UDMA CRC errors left over from some long-ago-corrected cabling issue.) I did acknowledge it, turning the thumbs down into a thumbs up, but then had second thoughts. Now I want to "undo" my acknowledgement so that the drive health goes back to a thumbs-down on the Dashboard. As I wrote previously, "I want it to go back to showing thumbs down for any drive with more than 0 reallocated sectors -- like it did before I acknowledged the thumbs down on that cache drive." There must be a way to return the Dashboard GUI to its default behavior. But I've been poring over menus and config files and I'm not seeing where the reallocation count limit has been changed for that SSD. So any help is appreciated.

Thanks, but that didn't affect the thumbs-up I am seeing on the Dashboard. It started at a thumbs up "healthy" on the cache drive and it stayed at a thumbs up "healthy" even though there is one reallocated sector. I want it to go back to showing thumbs down for any drive with more than 0 reallocated sectors -- like it did before I acknowledged the thumbs down on that cache drive.

Sorry for the convoluted subject line. I'll explain. I have a 1TB SSD with a single reallocated sector. I've set that up as my cache drive, but the Dashboard tab on Unraid was showing a thumbs-down 👎 next to "healthy" for that drive. So I clicked on it to override it to healthy, thinking that the status going to unhealthy again will alert me to new sector reallocations. But I had second thoughts and wondered how I could reset it so that it would go back to the default behavior of a thumbs-down for that SSD. At first, I hoped it was a browser cookie, but I proved that wrong. Does anyone know how to return that indicator to its normal function (thumbs down on that drive because it has a reallocated sector)?

I have a directory within a share that I wish to sync: /mnt/user/Unraid_Public/Sissy/Music I put that path in to a clean install of the Syncthing app on my Unraid system. I repeatedly got permission errors when mkdir tried to create the path. Every single directory was drwxrwxrwx below /mnt/ I even tried changing /mnt/ with a chmod 777. Still no joy. I uninstalled Synthing thinking I would start fresh. But then I found that uninstalling it left droppings -- /mnt/user/appdata/syncthing/ with various files and directories under it. How is that an uninstall? I'm sure that there must be simple directions somewhere, perhaps in a wiki, that explains how to sync an existing directory using Syncthing under Unraid. This stuff of going through pages of Docker and Syncthing settings and trying to figure out what settings need to change is nuts.

Fantastic! I searched all through the menus and didn't see anything. It never occurred to me that it would be a plugin (I only brought up Unraid a day ago).

Coming from QNAP and Thecus to Unraid, I find one important feature missing: A simple means of identifying drives by physical location in the chassis. I recommend that Unraid implement a feature where a user could help Unraid construct a graphic representation of drive location by providing the following: Horizontal or vertical drives? Number of rows? Number of columns? Then provide a means for the user to map controllers to physical disk locations (perhaps SCSI device numbers if those don't change). Examples: Vertical drive orientation, 1 row, 5 columns Horizontal drive orientation, 6 rows, 4 columns Horizontal drive orientation, 5 rows, 1 column. I am not suggesting that the Unraid GUI provide a photorealistic representation, just line drawings that repeat horizontal and vertical rectangles to represent the relative locations of drives, with red/green indicators to show drives being bad/good. Rather than having to shut down the Unraid server and pull the drives out one at a time searching for a serial number, the user could be presented with an image that showed them precisely which drive had failed. I know that this would not address every possible configuration, and that various customers have mixed vertical and horizontal orientation drives, sometimes in multiple chassis. But it would help a very large percentage of Unraid customers. Note: I recognize that there are ways to identify which drives are in which physical locations, including high-tech solutions utilizing Post-Its, label makers, sketches, etc. This is a feature request for those who find those methods lacking.