Jump to content

sephallen

Members
  • Posts

    33
  • Joined

  • Last visited

Posts posted by sephallen

  1. 6 hours ago, andenker said:

    After posting this, I looked at the issue from a different angle. I used DHCP option 121 on my MikroTik router to supply the static route to Unraid via DHCP. Worked flawlessly. I actually like this approach better since the routing stuff belongs to, well, a router.

     

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

  2. 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?

  3. 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?

  4. 5 minutes ago, kim_sv said:

    Thank you for this! Been looking for a way to monitor my Adaptec 71605, since the sensors from it isn't visible to unRAID.

     

    Maybe a daft question, but what do you mean by "more persistent"? I ran the storman command on top and that gave me a StorMan docker container and I've logged into the UI on port 8443. Won't this container persist after reboot or is there some problem with that metod I don't get?

     

    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).

  5. 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"

     

    • Thanks 1
  6. 22 hours ago, saarg said:

    Looks like it's detected and loaded the kernel modules.

    Did the other guy manage to get it running? I don't remember.

     

    Have you tried changing slots?

    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.

     

  7. 6 minutes ago, saarg said:

    Post the output of lspci -k

    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.

  8. Another P400 user here with the dreaded:

    Quote

    No devices were found

    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.

  9. 3 minutes ago, binhex said:

    EC28's issue was not related to airvpn, i could see a tunnel was established but he was unable to access the web ui, im not sure of the reason why this has now been resolved for him but i doubt its vpn provider related.

     

    please do the following:-

    https://github.com/binhex/documentation/blob/master/docker/faq/help.md

    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!

  10. 19 hours ago, EC28 said:

    Well, of all the damnedest things in the world, it decided to just start working.  Only issue I'm having now is that the UDP trackers error out.  That may be a AirVPN issue, as I don't see an option to tell it to let me use both UDP and TCP ports.  Looks like you have to pick one or the other. But what's strange is that the OVPN file I used is a UDP port.  And the port I have forwarded, which shows as open on their website, is both TCP and UDP.  But hey, at least we're working now!

     

    https://pastebin.com/Kp0dgAQG

     

    Now if I can just figure out the ratiocolor plugin.

     

    https://github.com/Gyran/rutorrent-ratiocolor

    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!

  11. 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?

  12. 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!

  13. 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.

×
×
  • Create New...