sephallen

I like this solution a lot - I too have a MikroTik router, I think I will need to have a play around with this!

You can set up some routing via the UI by navigating to: Settings -> Network Settings and scrolling down to the "Routing Table" section at the bottom. I'm not sure if this will fit your needs though!

Updated title as this is still an issue for me in the latest release of unRAID (6.12.6).

I've had this same issue for quite some time: but I have never been able to crack it by setting different static routes. The strange thing is, it used to "just work" but was broken by an unRAID update some time ago. If you ever figure it out, I'd love to know you you do it!

The repo already contains a docker-compose.yml template. If you clone the repo onto your server and run docker compose up, you should be good to go.

I always choose SAS over SATA for two main reasons: 1. The SAS interface is full duplex 2. In my experience, SAS drives tend to last longer

Since upgrading from 6.10, I have no longer been able to access the WebUI of any containers which utilise my "VPN tunneled access for docker" WireGuard (wg0) network when VPN'ed into my home network. VPN access to my home network goes via my router (running RouterOS) and not via unRAID directly. I have both an OpenVPN and WireGuard servers running on my router and neither is able to connect to these container WebUIs. I suspect this issue has something to do with being on a different LAN / subnet to my unRAID server while VPN'ed into the network. This is because I am able to remote into a VM running on unRAID (which is on the same subnet as the unRAID server) via my VPN and then browse to a container WebUI (on the wg0 network) using the VM's browser and it is accessible. I have tried playing around with static routes on my router, but sadly nothing has helped thus far. It used to work with no issues on unRAID 6.10 - is this a new bug introduced in 6.11?

Forgive me if this has been asked before, I did search the forums and Google, but I am coming up short. I have imported my WireGuard conf (AirVPN) and the peer type of access is set to "VPN tunnel for docker containers only". The tunnel appears to be connected and working, but the wg0 custom network does not appear in the drop down list of network options in the container settings. It also does not appear when running docker network ls I have restarted the docker service and recreated the WireGuard tunnel a few times, but this does not seem to help. I am running unRAID 6.10.3. Have I missed something obvious?

No worries, I'm glad someone else was able to find it useful. The container should persist after a reboot, but if you were to recreate your docker.img, you would need to find and run the command again. If you used the docker-compose template, you could simply run: docker-compose up -d within the same directory as the template to recreate the container (though you would need the docker-compose CLI tool installed on your unRAID machine).

Hi guys, the simplest way to get storman up and running would be to use this command: docker run -d --privileged --name storman -p 8443:8443 nheinemans/storman and then navigate to https://your-unraid-box:8443 (https is required, but it is using a self signed certificate, so you'll get a warning in your browser). The login credentials are root:root. If you preferred something a little more persistent, you could create a docker-compose template like this: version: '3.4' services: storman: image: nheinemans/storman container_name: "storman" privileged: true tty: true ports: - "8443:8443"

To conclude, I sourced a P620 at a good price (also HP branded) and it works perfectly. It definitely would seem the P400 is indeed faulty. Thanks for all your help with debugging!

I don't believe the other poster managed to get their's working - I couldn't see any more posts about it. I have tried changing slots, but I end up with the same results. Other things I've tried: Installing as a second GPU in my desktop machine and booting into Windows 10 (UEFI mode) - GPU not detected in the device manager at all. Created a bootable legacy boot WIndows 10 USB drive - GPU still not showing in device manager. Removed my main GPU and installed P400 into primary slot - no video output at all, not even the BIOS (potentially could still be due to UEFI?). Note - I am using a mini display port to HDMI adpater with the P400 - not sure if this could cause issues. Switched the server board primary video output to PCI-E - no output but some beeping. Passed the P400 as a secondary GPU (VNC as primary) into a fresh Windows 10 VM in unRAID - P400 detected and drivers installed successfully but the GPU would not fully initialise in the device manager (Code 43) which prevents me from running the UEFI update tool from Nvidia (https://www.nvidia.com/en-us/drivers/nv-uefi-update-x64/). At this point, I am beginning to suspect the GPU is faulty.

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890 Northbridge only dual slot (2x16) PCI-e GFX Hydra part (rev 02) Subsystem: ASUSTeK Computer Inc. RD890 Northbridge only dual slot (2x16) PCI-e GFX Hydra part 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD/ATI] RD890S/RD990 I/O Memory Management Unit (IOMMU) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD890S/RD990 I/O Memory Management Unit (IOMMU) 00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GFX port 0) Kernel driver in use: pcieport 00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP Port 0) Kernel driver in use: pcieport 00:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP Port 4) Kernel driver in use: pcieport 00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP Port 5) Kernel driver in use: pcieport 00:0b.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD990 PCI to PCI bridge (PCI Express GFX2 port 0) Kernel driver in use: pcieport 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] Subsystem: ASUSTeK Computer Inc. SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] Kernel driver in use: ahci Kernel modules: ahci 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller Subsystem: ASUSTeK Computer Inc. SB7x0/SB8x0/SB9x0 USB OHCI0 Controller Kernel driver in use: ohci-pci 00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller Subsystem: ASUSTeK Computer Inc. SB7x0 USB OHCI1 Controller Kernel driver in use: ohci-pci 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller Subsystem: ASUSTeK Computer Inc. SB7x0/SB8x0/SB9x0 USB EHCI Controller Kernel driver in use: ehci-pci 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller Subsystem: ASUSTeK Computer Inc. SB7x0/SB8x0/SB9x0 USB OHCI0 Controller Kernel driver in use: ohci-pci 00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller Subsystem: ASUSTeK Computer Inc. SB7x0 USB OHCI1 Controller Kernel driver in use: ohci-pci 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller Subsystem: ASUSTeK Computer Inc. SB7x0/SB8x0/SB9x0 USB EHCI Controller Kernel driver in use: ehci-pci 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3d) Subsystem: ASUSTeK Computer Inc. SBx00 SMBus Controller Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4 00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller Subsystem: ASUSTeK Computer Inc. SB7x0/SB8x0/SB9x0 IDE Controller Kernel driver in use: pata_atiixp Kernel modules: pata_atiixp 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller Subsystem: ASUSTeK Computer Inc. SB7x0/SB8x0/SB9x0 LPC host controller 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI2 Controller Subsystem: ASUSTeK Computer Inc. SB7x0/SB8x0/SB9x0 USB OHCI2 Controller Kernel driver in use: ohci-pci 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 Kernel modules: k10temp 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 Kernel modules: fam15h_power 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 00:19.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 00:19.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 00:19.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 00:19.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 Kernel modules: k10temp 00:19.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 Kernel modules: fam15h_power 00:19.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 00:1a.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 00:1a.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 00:1a.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 00:1a.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 Kernel modules: k10temp 00:1a.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 Kernel modules: fam15h_power 00:1a.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 00:1b.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 0 00:1b.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 1 00:1b.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 2 00:1b.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 3 Kernel modules: k10temp 00:1b.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 4 Kernel modules: fam15h_power 00:1b.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5 01:01.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 10) Subsystem: ASPEED Technology, Inc. ASPEED Graphics Family Kernel modules: ast 01:02.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a Controller (rev 70) Subsystem: ASUSTeK Computer Inc. FW322/323 [TrueFire] 1394a Controller 02:00.0 RAID bus controller: Adaptec Series 7 6G SAS/PCIe 3 (rev 01) Subsystem: Adaptec Series 7 - ASR-71605 - 16 internal 6G SAS Port/PCIe 3.0 Kernel driver in use: aacraid Kernel modules: aacraid 03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection Subsystem: ASUSTeK Computer Inc. Motherboard Kernel driver in use: e1000e Kernel modules: e1000e 04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection Subsystem: ASUSTeK Computer Inc. Motherboard Kernel driver in use: e1000e Kernel modules: e1000e 05:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) Subsystem: ASUSTeK Computer Inc. SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] Kernel driver in use: mpt3sas Kernel modules: mpt3sas 06:00.0 VGA compatible controller: NVIDIA Corporation GP107GL [Quadro P400] (rev a1) Subsystem: Hewlett-Packard Company GP107GL [Quadro P400] Kernel driver in use: nvidia Kernel modules: nvidia_drm, nvidia 06:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) Subsystem: Hewlett-Packard Company GP107GL High Definition Audio Controller Showing up as a HP too (like a previous poster, though there is no HP branding on the card itself - just Nvidia.

Another P400 user here with the dreaded: However, the card does show up in System Devices and appears as an option in Graphics Card for a VM. I have read through the topic and here are some things I have tried: Reinstalling the drivers (currently using unRAID 6.8.3 with Nvidia driver version 440.59) Having something plugged into the card (I have the generic Nvida branded card with three mini display ports) Making sure I do not have Jellyfin auto starting (I actually removed Jellyfin many months ago) I don't actually get any output from the P400 but I assume this is because I have the onboard VGA enabled as the primary display adapter in the BIOS. My motherboard is a ASUSTeK Computer INC. KGP(M)E-D16 Version Rev 1 with the latest BIOS American Megatrends Inc. Version 3309. Dated: 06/16/2016. I do have Plug and Play OS disabled in my BIOS, should this be enabled? I haven't been able to determine if unRAID supports it.

When EC28 mentioned they had started from scratch, it reminded me that I had done the same over the weekend in order to try to fix the timeouts I often get (particularly when downloading larger files), but alas it didn't fix the issue. However, I also changed a setting in my rtorrent.rc and hadn't restarted yet - turns out the value was invalid and that's what the issue was. I have now corrected it and everything is working fine again. So AirVPN is a red herring - thanks for the help and sorry for wasting your time!

I'm having the same issue as you and I am also on AirVPN. I even tried rolling back a few versions of the docker image, but the same issues persists. I assume it must be AirVPN related. Generating new OVPN files from AirVPN (trying UDP and TCP) didn't solve the issue either. I will keep restarting in the hopes that my set up will magically start working too I guess!

The seller replaced the drive for me and the replacement seems to be working perfectly. Thanks again for all the help!

I don't have any other machines that support SAS drives sadly Thanks for all your help, I have contacted the seller and if I get it working somehow I'll post an update here.

Unfortunately, I have tried using Kapton tape on just pin 3 and pins 1, 2 and 3 but I am still unable to detect the drive in the BIOS. I am actually using a Logic Case SC-4320, which has hot swap drive bays (5 bays are powered by a single molex connector) and from what I can tell, molex isn't affected by the 3.3v issue, even though it ultimately ends up being a SATA power connector. Is there anything else I can try?

I'll give it a go and report back, thanks!

Hi everyone! I recently purchased a refurbished HGST 0F18370 6TB Helium drive for my unRAID server, but I am unable to get it to show in the BIOS. I have an ASUS KGPE-D16 on the latest BIOS and I already have a 4TB SAS drive working in it alongside a lot of different sized SATA drives (1 - 4TB). However, I cannot get the 6TB to be detected at all. I have tried different ports and toggled between IDE and AHCI but with no success. Am I missing something? Or is the drive perhaps dead? Thanks in advanced!

I've been leaving my Plex docker running for hours (2-3+) on both plexpass and latest and I am still unable to access the Plex UI. Strangely, the log is also empty. This also happens if I try a clean install with an empty settings directory and after deleting the docker container and image UPDATE:: After clearing out the container and image again and a few more restarts, I managed to get the "latest" non Plex Pass version up and running.

That was it, thanks! I did check for updates via the plugin prior to posting, but nothing showed so I updated manually instead.

I cannot create any new files on one of my shares, but all other shares are fine. For example, when I try to create a new folder named 'test' in the terminal I get this error message: mkdir: cannot create directory ‘test’: No such file or directory Though I am able to delete files on the faulty share. I have ran new permissions from the webgui and terminal but it did not help. I also reiserfsck --check all my data drives, one had some corruptions which I fixed and then re-ran the new permissions, but they problem is still there. This only started yesterday, I am running unraid 6 beta 10. Does anyone have any other suggestions?

I have the exact same issue which is why I'm only using the normal sickbeard. Would love to know why too!! Sent from my SM-N9005 using Tapatalk I'm not sure why that would be. The only real difference in my plugin is which repo it cloned from. Unless shockwave has an extra dependency I don't know about. Does the log show anything or perhaps the unread console when it hangs? Anything in the system log? Nothing really shows up in the SickRage log, you can view some examples here https://sickrage.tv/forums/forum/help-support/bug-issue-reports/7236-add-new-show-times-out-and-crashes-sickrage and as for the unraid syslog, nothing shows at all.