pXius
-
Posts
23 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by pXius
-
-
If you're using Authentication version 3 breaks the ability to log in. You get an HTTP 500 error. SABNZBD forum says it will be fixed in the next version.
In the meantime, disable auth, or use your reverse proxy's HTML auth.
Alternatively, roll back to version 2 by pasting
linuxserver/sabnzbd:2.3.9-0ubuntu1jcfp218.04-ls67
into you template's repository field, instead of linuxserver/sabnzbd:latest
Link to the thread.
-
On 12/23/2019 at 12:45 AM, Viper359 said:
Had a different parity drive fail that night.
Switched out the HBA to an LSI one.
Rebuilt the parity drive. Ran 10hrs, no errors
Started Rebuilding the other dropped drive.
21 drives running now, we shall see if this was the issue. Just waiting for rebuild to finish on the last drive.
Did you ever resolve the issue?
I'm having the same problems using a Netapp X2065A-R6 HBA and a DS4246.
At first I thought it was being caused by a bad interposer, but after reading your thread and having it happen to a second drive, I'm not so sure.
I'm considering removing all the interposers and running straight SATA. I've done this in the past but I get issues with drive detection in unRaid on 8TB+ drives when I reboot or power cycle without interposers.
edit: UPDATE
Ok, I've played around a bit, using "new config" and "parity is valid" to move drives around and add/remove interposers.
Interposers changes the drive name, hence the "New Config".
Anyway,
I'm starting to think I had bad interposers on the drives that got kicked. Having a bunch of extra's, I replaced the interposers on those drives and so far everything seems fine.
In a perfect world I'd just not use interposers at all, because I lose most of the smart data, including drive temps and the ability to properly spin up and down (temps did work for awhile but stopped a few updates back), but without interposers I have a hard time detecting drives that are 8TB's and larger. Sometimes I need to replug those drives once or twice before they're detected after a reboot. Interposers solves that issue.
To save myself all the headache I've ordered an LSI card and the appropriate cable which will hopefully allow me to run the SATA drives without interposers once again. Looking forward to having SMART data again.
-
EU Endpoints working again.
Quick question, Is there a way to get the webui to function if you're using a custom br ip? When I use a custom IP my web ui no longer loads. Bridge obviously works just fine.
Also, I AM using a server that supports port forward. Sweden. Tried Frankfurt as well.
PS. Disabling VPN lets web ui function even on a custom IP. I've tried a ton of things but I'm at a loss.
-
54 minutes ago, binhex said:
if you use pia and you are seeing the above in your log then the issue is that the pia api is down, looks like they are having technical difficulties right now, see here:-
https://www.reddit.com/r/PrivateInternetAccess/comments/fs7ja0/cant_get_forwarded_port/
For now your only option is to set STRICT_PORT_FORWARD to 'no', this will allow you to connect but you will NOT have a working incoming port, so speeds will be slow at best.
Just to be clear, there is nothing i can do about this guys, its a vpn provider issue.
Been pulling my hair out of my head thinking I messed up somewhere. Great....
-
I'm looking forward to the multiple cache pools.
I'm currently running my VM's and Docker containers off unassigned devices because my cache drive exclusively handles the decompression on incoming downloads. Even with an NVME drive, I get media playback issues if I decompress incoming downloads while streaming, and that's with CPU pinning. The drive is the bottleneck.
Having multiple cache pools will make life so much easier especially for docker apps that don't like running off any directory that isn't /mnt/user like musicbrainz.
As for larger arrays with better redundancy; you could run unRaid on ESXi or Proxmmox and set up ZFS pools to pass through as virtual drives to unRaid. That way you can haz all the storage in raidz (see what I did there) and still use the unRaid array in the way you're used to.
The only downside with something like ZFS is that it's best to start off with all your storage drives and not adding single drives over time.
I also have no idea if you can pass something like a GPU from say Proxmox to unRiad and then from unRiad into a docker/VM, and whether there's a performance penalty for doing so.
-
6 minutes ago, Djoss said:
I just changed the 'latest' tag to point to the previous version.
So just update the container again...
Awesome! Thanks!
-
Just ran into the error as well.
Is there an easy way to roll back to an older release? -
Having similar issues. Installed musicbrainz for the first time, can't log into web gui. Just times out.
Using port 5000. I've tried using a custom IP for the docker as well as bridge. Musicbrainz itself functions as I can see it doing database work as folders are created etc. Just can't access the web gui.
Using Unraid 6.8.2
My appdata is hosted on a Unassigned device using RW/slave.
EDIT:
Solved - Sort of.
It seems that musicbrainz doesn't like being run in unassigned devices. I was able to get it working using /mnt/cahce/musicbrainz/ instead of my normal app data location.My new issues is that Picard can't use my mirror server. It requires a Authentication key only generated by the master site.
-
7 hours ago, itimpi said:
Just for interest - why not roll back to 6.8.0 stable rather than the RC?
Was on 6.8.0- RC5 before trying 6.8.1, so just loaded RC9 out of curiosity.
Will probably jump on 6.8 stable tonight. -
Ok so the Nvidia 6.8.1 breaks a few things for me as well.
The first is I'm guessing the driver for a Intel PRO/1000 Pt Dual Port Server PCIE NIC. So I have to use my on board networking. Not a huge issue.
My bigger issue is that my Dell Perc H200 SAS card doesn't work with this build, meaning half of my array isn't detected.
Rolled back to 6.8.0 RC9 for now and all is working.Thanks for the awesome work!
-
I'm having an issue with the BitWarden container.
Version 1.9.1-8be2ed62Unraid Version: 6.8.0-rc 3
Regardless of what I set the port to in the template, it will keep using port 80. This makes my port forwarding tricky considering port 80 is already being used.
Any ideas?
-
Is there any sort of Trim Support for SSD's in Unassigned Devices?
I run my Dockers/VM's off a NVME SSD in Unassigned Devices as my normal ssd cache pool is very heavily utilized.
Thanks!
-
12 hours ago, antanoid said:
some direction would be nice on this, any ideas welcome!
You having the same issue I had, how are you trying to connect to your WEBUI? On what IP range is your Deluge and what IP range is the mashine you are trying to connect from?
Also, give your Deluge an IP other than that of the Unraid machine. -
Download the Firefox container from the APPS section in unraid.
If your Deluge docker is using the same IP as your host unraid machine, then use the same IP for firefox as well.
If your deluge docker has an ip different from that of the host machine, you will need to use a different IP for the firefox docker as well. It's a security thing.After that you can access the Deluge docker via the firefox docker by entering the deluge IP in the firefox address bar.
When outside your network you'll need to access your local network via a VPN of sorts. My router has a openVPN server as a feature, so I just connect to that when away from home.
-
7 hours ago, binhex said:
i see nothing wrong in the log, however all the important stuff has been removed so its hard to tell if you have a config issue, if your lan_network is correct then my next guess would be browser issue, try accessing web ui from another machine.
Ended up being an issue logging onto my home network remotely via a VPN.
I'm now just using the Firefox docker container to access Deluge when away from home.
Thanks for the help and the awesome contribution to the community! It's appreciated a million times over! -
Another "Can't access the webGui post".
Been running fine for months, not sure what changed.
I've tried different PIA endpoints to no avail.
Seems to connect to the VPN, webgui just won't launch.
Any ideas?2019-06-10 23:47:52,096 DEBG 'start-script' stdout output: [debug] OpenVPN command line:- /usr/bin/openvpn --daemon --reneg-sec 0 --mute-replay-warnings --auth-nocache --setenv VPN_PROV 'pia' --setenv DEBUG 'true' --setenv VPN_DEVICE_TYPE 'tun0' --setenv VPN_REMOTE 'de-frankfurt.privateinternetaccess.com' --script-security 2 --writepid /root/openvpn.pid --remap-usr1 SIGHUP --log-append /dev/stdout --pull-filter ignore 'up' --pull-filter ignore 'down' --pull-filter ignore 'route-ipv6' --pull-filter ignore 'ifconfig-ipv6' --pull-filter ignore 'tun-ipv6' --pull-filter ignore 'persist-tun' --pull-filter ignore 'reneg-sec' --remote 185.220.70.171 1198 udp --remote 185.220.70.166 1198 udp --remote 185.220.70.138 1198 udp --remote 185.220.70.152 1198 udp --remote 185.220.70.155 1198 udp --remote 185.220.70.136 1198 udp --remote 185.220.70.169 1198 udp --remote 185.220.70.172 1198 udp --remote 185.220.70.134 1198 udp --remote 185.220.70.140 1198 udp --remote 185.220.70.131 1198 udp --remote 185.220.70.144 1198 udp --remote 185.220.70.170 1198 udp --remote-random --up /root/openvpnup.sh --up-delay --up-restart --keepalive 10 60 --setenv STRICT_PORT_FORWARD 'yes' --disable-occ --auth-user-pass credentials.conf --cd /config/openvpn --config '/config/openvpn/DE Frankfurt.ovpn' 2019-06-10 23:47:52,096 DEBG 'start-script' stdout output: [info] Starting OpenVPN... 2019-06-10 23:47:52,110 DEBG 'start-script' stdout output: Mon Jun 10 23:47:52 2019 WARNING: file 'credentials.conf' is group or others accessible Mon Jun 10 23:47:52 2019 OpenVPN 2.4.7 [git:makepkg/2b8aec62d5db2c17+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 19 2019 Mon Jun 10 23:47:52 2019 library versions: OpenSSL 1.1.1b 26 Feb 2019, LZO 2.10 2019-06-10 23:47:52,110 DEBG 'start-script' stdout output: [info] OpenVPN started 2019-06-10 23:47:52,110 DEBG 'start-script' stdout output: Mon Jun 10 23:47:52 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts [debug] Waiting for valid IP address from tunnel... 2019-06-10 23:47:52,110 DEBG 'start-script' stdout output: Mon Jun 10 23:47:52 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]185.220.70.170:1198 2019-06-10 23:47:52,110 DEBG 'start-script' stdout output: Mon Jun 10 23:47:52 2019 UDP link local: (not bound) Mon Jun 10 23:47:52 2019 UDP link remote: [AF_INET]185.220.70.170:1198 2019-06-10 23:47:52,261 DEBG 'start-script' stdout output: Mon Jun 10 23:47:52 2019 [84dcd2f8211fd75d6fad788d96ffef26] Peer Connection Initiated with [AF_INET]185.220.70.170:1198 2019-06-10 23:47:58,533 DEBG 'start-script' stdout output: Mon Jun 10 23:47:58 2019 TUN/TAP device tun0 opened Mon Jun 10 23:47:58 2019 /usr/bin/ip link set dev tun0 up mtu 1500 2019-06-10 23:47:58,534 DEBG 'start-script' stdout output: Mon Jun 10 23:47:58 2019 /usr/bin/ip addr add dev tun0 local 10.37.10.6 peer 10.37.10.5 2019-06-10 23:47:58,534 DEBG 'start-script' stdout output: Mon Jun 10 23:47:58 2019 /root/openvpnup.sh tun0 1500 1558 10.37.10.6 10.37.10.5 init 2019-06-10 23:47:58,537 DEBG 'start-script' stdout output: [debug] Waiting for valid IP address from tunnel... 2019-06-10 23:47:58,537 DEBG 'start-script' stdout output: [debug] Waiting for valid IP address from tunnel... 2019-06-10 23:47:58,538 DEBG 'start-script' stdout output: Mon Jun 10 23:47:58 2019 Initialization Sequence Completed 2019-06-10 23:47:58,639 DEBG 'watchdog-script' stdout output: [debug] Valid IP address from tunnel acquired '10.37.10.6' [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.37.10.6 different, marking for reconfigure 2019-06-10 23:47:58,642 DEBG 'start-script' stdout output: [debug] Valid IP address from tunnel acquired '10.37.10.6' 2019-06-10 23:47:58,642 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2019-06-10 23:47:58,643 DEBG 'start-script' stdout output: [debug] Valid IP address from tunnel acquired '10.37.10.6' 2019-06-10 23:47:58,643 DEBG 'start-script' stdout output: [debug] Port forwarding is enabled 2019-06-10 23:47:58,643 DEBG 'start-script' stdout output: [debug] Checking endpoint 'de-frankfurt.privateinternetaccess.com' is port forward enabled... 2019-06-10 23:47:58,643 DEBG 'start-script' stdout output: [debug] Valid IP address from tunnel acquired '10.37.10.6' 2019-06-10 23:47:58,644 DEBG 'start-script' stdout output: [debug] Attempting to get external IP using Name Server 'ns1.google.com'... 2019-06-10 23:47:58,645 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2019-06-10 23:47:58,646 DEBG 'start-script' stdout output: [info] Attempting to curl https://www.privateinternetaccess.com/vpninfo/servers?version=82... 2019-06-10 23:47:58,787 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address 185.220.70.170 2019-06-10 23:47:58,847 DEBG 'watchdog-script' stdout output: [debug] External IP address from tunnel is '185.220.70.170' 2019-06-10 23:47:58,847 DEBG 'watchdog-script' stdout output: [debug] Waiting for file '/home/nobody/vpn_incoming_port.txt' to be generated (contains PIA API generated incoming port number)... 2019-06-10 23:47:59,030 DEBG 'start-script' stdout output: [info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200 2019-06-10 23:47:59,077 DEBG 'start-script' stdout output: [debug] PIA endpoint 'de-frankfurt.privateinternetaccess.com' is in the list of endpoints that support port forwarding 2019-06-10 23:47:59,077 DEBG 'start-script' stdout output: [info] List of PIA endpoints that support port forwarding:- [info] ca-toronto.privateinternetaccess.com [info] ca-montreal.privateinternetaccess.com [info] ca-vancouver.privateinternetaccess.com [info] de-berlin.privateinternetaccess.com [info] de-frankfurt.privateinternetaccess.com [info] sweden.privateinternetaccess.com [info] swiss.privateinternetaccess.com [info] france.privateinternetaccess.com [info] czech.privateinternetaccess.com [info] spain.privateinternetaccess.com [info] ro.privateinternetaccess.com [info] israel.privateinternetaccess.com [debug] Attempting to get dynamically assigned port... 2019-06-10 23:47:59,080 DEBG 'start-script' stdout output: [info] Attempting to curl http://209.222.18.222:2000/?client_id=1450c6c2e51317ffe1d184a94bab67aacf61835be0969a7f1cb66ff362bfbd8c... 2019-06-10 23:47:59,928 DEBG 'start-script' stdout output: [info] Curl successful for http://209.222.18.222:2000/?client_id=1450c6c2e51317ffe1d184a94bab67aacf61835be0969a7f1cb66ff362bfbd8c, response code 200 2019-06-10 23:47:59,951 DEBG 'start-script' stdout output: [debug] Successfully assigned incoming port 24365 2019-06-10 23:48:00,849 DEBG 'watchdog-script' stdout output: [debug] Incoming port for tunnel is '24365' 2019-06-10 23:48:00,849 DEBG 'watchdog-script' stdout output: [info] Deluge incoming port 6890 and VPN incoming port 24365 different, marking for reconfigure 2019-06-10 23:48:00,849 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2019-06-10 23:48:01,063 DEBG 'watchdog-script' stdout output: [info] Deluge listening interface currently defined as 0.0.0.0 [info] Deluge listening interface will be changed to 0.0.0.0 [info] Saving changes to Deluge config file /config/core.conf... 2019-06-10 23:48:01,288 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2019-06-10 23:48:01,498 DEBG 'watchdog-script' stdout output: [info] Deluge process listening on port 58846 2019-06-10 23:48:01,865 DEBG 'watchdog-script' stdout output: Setting random_port to False.. Configuration value successfully updated. 2019-06-10 23:48:02,227 DEBG 'watchdog-script' stdout output: Setting listen_ports to (24365, 24365).. Configuration value successfully updated. 2019-06-10 23:48:02,614 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2019-06-10 23:48:02,614 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2019-06-10 23:48:02,614 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started 2019-06-10 23:48:02,615 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 24365 [debug] Deluge incoming port is 24365 [debug] VPN IP is 10.37.10.6 [debug] Deluge IP is 10.37.10.6 2019-06-10 23:48:32,616 DEBG 'watchdog-script' stdout output: [debug] Waiting for valid IP address from tunnel... 2019-06-10 23:48:32,729 DEBG 'watchdog-script' stdout output: [debug] Valid IP address from tunnel acquired '10.37.10.6' 2019-06-10 23:48:32,734 DEBG 'watchdog-script' stdout output: [debug] External IP address from tunnel is '185.220.70.170' 2019-06-10 23:48:32,735 DEBG 'watchdog-script' stdout output: [debug] Incoming port for tunnel is '24365' 2019-06-10 23:48:32,737 DEBG 'watchdog-script' stdout output: [debug] VPN incoming port is 24365 [debug] Deluge incoming port is 24365 [debug] VPN IP is 10.37.10.6 [debug] Deluge IP is 10.37.10.6 -
Just ordered a PERC H200.
Going to try to get a refund on the H330. -
Can't even get this thing to initialize in windows. Just gives me a code 10 error.
Tried Server 2016.
Going to try windows 7 now. If I can get it recognized I can at least update the firmware.
UPDATE:
Ok, so got it recognized in Win7 and was able to update the firmware.
I can also see the drive in Raid0 in explorer.
HBA mode also works in Win7.Same issue when going back to unRaid. The megeraid_sas driver fails to initialize.
I'm out of ideas. I just don't get how it works for 2 members but not others.
-
18 minutes ago, johnnie.black said:
There are some conflicting reports, but most likely itwon't work, e.g:
So I've got 3 options where I stand.
1. Force load the megaRAID_sas driver, or get a hold of the driver one Tom distributed to some members for testing. Either way, I don't know how to initialize a driver manually after the server starts.
2. Update the firmware, I'm busy doing this now.
3. There was mention of setting each drive to it's own raid0. I'm yet to try this.
-
So I just got a dell PERC H330.
I set it to HBA mode and it detects all my attached disks.
The Controller is detected by unriad
Similar to this img:
The disks however are not detected or passed through.
From what I can tell, it seems that the MEGAraid driver is not loading.Based on this thread, a driver was in development and working as per one of the posters. Is this driver part of unRaid yet? Latest build. Do I have to do something to get it to load?
[Support] Linuxserver.io - SABnzbd
in Docker Containers
Posted
You can roll back to ver 2. here.
https://forums.unraid.net/topic/40756-support-linuxserverio-sabnzbd/?do=findComment&comment=884284
But you'll probably need to change your flow going forward.