Ahmed

I just noticed i can't run an update using the updater.phar anymore. docker exec -it nextcloud updater.phar OCI runtime exec failed: exec failed: unable to start container process: exec: "updater.phar": executable file not found in $PATH: unknown anyone else having this issue? im on v27 docker exec -it nextcloud occ -V Nextcloud 27.0.0

just in case this helps anyone else. I realised when i was testing this, i had put the iommu=pt but only for the boot without gui. When I first tested this it failed and no disk were shown and it was only because i didn't append it to the end of the gui boot line e.g. default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot iommu=pt label Unraid OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui iommu=pt So essentially you will need to add it to all the boot options if you want the disks to be shown. Or you can just manually add it if you are not running it headless.

awesome - will give that a go then. thanks heaps.

will this work for: Marvell Technology Group Ltd. 88SE9230 01:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller [1b4b:9230] (rev 11)

Not 100% sure this is going to work properly and im sure there's prob a better way to do this.. i just wrote up a super amazing script to export the data into influxdb #!/usr/bin/env bash #set -x RAW=$(/usr/local/bin/corsairmi) OUTPUT=/mnt/user/appdata/telegraf/corsair-telegraf.csv function simple() { # echo $(echo "$RAW" | grep "$1" | cut -d ':' -f2 | cut -d ' ' -f 2) echo "$RAW" | grep "$1" | tr -s ' ' | cut -d ':' -f 2 | cut -d ' ' -f 2 } function rail() { # echo "$RAW" | grep -A 3 "output ${1}v" | grep "$2" | tr -s ' ' | cut -d ' ' -f 2 echo "$RAW" | grep "$1" | grep "$2" | tr -s ' ' | cut -d ' ' -f 3 } temp_0=$(simple "temp1") temp_1=$(simple "temp2") powered=$(simple "powered") uptime=$(simple "uptime") supply=$(simple "supply volts") total_watts=$(simple "total watts") # 12V Rail volts_12v=$(rail "output0 volts") amps_12v=$(rail "output0 amps") watts_12v=$(rail "output0 watts") # 5V Rail volts_5v=$(rail "output1 volts") amps_5v=$(rail "output1 amps") watts_5v=$(rail "output1 watts") # 3.3V Rail volts_3_3v=$(rail "output2 volts") amps_3_3v=$(rail "output2 amps") watts_3_3v=$(rail "output2 watts") # InfluxDB output echo "power_supply temp_0=\"$temp_0\",temp_1=\"$temp_1\",total_time=\"$powered\",uptime=\"$uptime\",supply_volts=\"$supply\",total_watts=\"$total_watts\",12v_volts=\"$volts_12v\",12v_amps=\"$amps_12v\",12v_watts=\"$watts_12v\",5v_volts=\"$volts_5v\",5v_amps=\"$amps_5v\",5v_watts=\"$watts_5v\",3.3v_volts=\"$volts_3_3v\",3.3v_amps=\"$amps_3_3v\",3.3v_watts=\"$watts_3_3v\"" > $OUTPUT WIth the output file you can import it straight to influxdb with a cron job to run for like every 5min. Here is how i did it manually # curl -i -XPOST 'http://influxdb-ip:8086/write?db=telegraf' --data-binary @/dir/of/corsair-telegraf.csv HTTP/1.1 204 No Content Content-Type: application/json Request-Id: fd24688f-5c64-11ea-93c0-7085c242ccc6 X-Influxdb-Build: OSS X-Influxdb-Version: 1.7.10 X-Request-Id: fd24688f-5c64-11ea-93c0-7085c242ccc6 Date: Mon, 02 Mar 2020 09:05:40 GMT and now i have to figure out how to get grafana to show the results. fun times!! ***ok scratch that. it didnt seem to work...... seems like it wont input the results even though they appear to be clearly showing in the file.

Thats exactly what i was thinking and was hoping for an answer.

all good. so just adding a variable with the location of the config file in appdata is all it needs. sweet.

Can you please explain where you found the conf file? i did a search and can find it under /var/lib/docker/btrfs/subvolumes/ but i dont think that would be the usual place holder for docker configs. Usually as itimp stated its under /mnt/user/appdata/docker/blah

Ok - ignore that ^^ its working fine.. just has a whole bunch of forbidden's and then it starts working - AWESOME> thanks

So i noticed you have to have an account created to actually test out bbc iplayer via the web. I have firefox setup to pass through privoxy and it works fine. When I start this docker, it fails when it goes to download the show: 2018-12-19 12:37:31,057 DEBG 'get-iplayer' stdout output: ERROR: Failed to download URL (3/3): https://vod-hls-uk-live.akamaized.net/usp/auth/vod/piff_abr_full_sd_ad/bc93a0-b0bsqzq1/vf_b0bsqzq1_18dd5df3-b811-4b90-823d-526d62850072.ism.hlsv2.ism/vf_b0bsqzq1_18dd5df3-b811-4b90-823d-526d62850072.ism.hlsv2.m3u8?__gda__=1545215848_543fe08296c477c872ae1594981a858e ERROR: Response: 403 Forbidden ERROR: Ignore this error if programme download is successful Any suggestions? going to the link via browser i get the "Access Denied You don't have permission to access blah blah " Which makes me think its looking for authentication before it will allow me to dl using this app? So does this docker work without a user login to bbc iplayer?

Hey @JonMielIV - so when you edit the config for this container, you just click on the 'Add another Path, Port, Variable, Label or Device' then add they new variables in and start the docker. When you start up this docker, you can watch the logs to see it go through the proxy you setup in deluge (which has privoxy included). Just make sure you have set that up and the proxy (privoxy) is working properly. If you haven't got deluge setup with privoxy then you will obviously need to get that sorted first. On another note - I also noticed the VPN service provider I'm using is geoblocked (PIA) so no BBC for me until I get another VPN provider.

Ok ok ... figured it out - just needed to add a variable to add the proxy.

Unless I’ve miss understood - anyone around that can help me ?

Hi - thanks for the docker but I am not exactly sure how to get it to work with privoxy. I have privoxy working and connected to London. How do I point this docker to work through privoxy? Sorry for the newbish question (and I see its sort of been answered on page 1 of this thread - but it doesnt explain how to actually do it). Thanks in advance!!

Thanks for your patch - works fine now. Also I left it as the IP as it was the default config from PIA - so i didnt bother. Cheers for the advice.

Ok thanks. I have attached a copy of the supervisord.log file (removed my pia login details). supervisord.log.txt I did notice a difference in the logs Before: 2018-03-10 17:48:40.892760 [info] VPN_REMOTE defined as '109.201.154.183' 2018-03-10 17:48:40.914705 [info] VPN_PORT defined as '1198' 2018-03-10 17:48:40.936820 [info] VPN_PROTOCOL defined as 'udp' 2018-03-10 17:48:40.958032 [info] VPN_DEVICE_TYPE defined as 'tun0' and after: 2018-03-14 22:39:46.979625 [info] VPN_REMOTE defined as '109.201.154.183' 2018-03-14 22:39:47.002382 [info] VPN_PORT defined as '109 2018-03-14 22:39:47.002426 1198' 2018-03-14 22:39:47.028200 [info] VPN_PROTOCOL defined as 'udp' 2018-03-14 22:39:47.051138 [info] VPN_DEVICE_TYPE defined as 'tun0' Looks like its missing the VPN_Port defined as '1198' and is taking the first part of the IP 109, after the last update.

hello, not sure whats changed with the new update but I cant get openvpn to work with PIA using openvpn-ip anymore Log file is showing: 2018-03-14 20:57:36,641 DEBG 'start-script' stdout output: [info] Starting OpenVPN... 2018-03-14 20:57:36,646 DEBG 'start-script' stdout output: Wed Mar 14 20:57:36 2018 WARNING: file 'credentials.conf' is group or others accessible Wed Mar 14 20:57:36 2018 OpenVPN 2.4.4 x86_64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 26 2017 Wed Mar 14 20:57:36 2018 library versions: OpenSSL 1.1.0f 25 May 2017, LZO 2.10 2018-03-14 20:57:36,647 DEBG 'start-script' stdout output: [info] OpenVPN started 2018-03-14 20:57:36,647 DEBG 'start-script' stdout output: Wed Mar 14 20:57:36 2018 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2018-03-14 20:57:36,647 DEBG 'start-script' stdout output: Wed Mar 14 20:57:36 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]109.201.154.183:1198 2018-03-14 20:57:36,647 DEBG 'start-script' stdout output: Wed Mar 14 20:57:36 2018 UDP link local: (not bound) 2018-03-14 20:57:36,647 DEBG 'start-script' stdout output: Wed Mar 14 20:57:36 2018 UDP link remote: [AF_INET]109.201.154.183:1198 2018-03-14 20:57:36,648 DEBG 'start-script' stdout output: Wed Mar 14 20:57:36 2018 write UDP: Operation not permitted (code=1) 2018-03-14 20:57:39,088 DEBG 'start-script' stdout output: Wed Mar 14 20:57:39 2018 write UDP: Operation not permitted (code=1) If i try PIA openvpn-tcp it works fine, but its very very slow. Would be really grateful for any help

Sorry, I meant i removed the old: VT6421 IDE/SATA PCI Controller. After removing it (with VT-d disabled) i still couldn't see the drives but was watching the logs and noticed that it was still trying to load the IDE drivers. I re-enabled the script which is supposed to start the AHCI driver and then restarted. BOOM it now sees the disk coming out of both Rocketraid controllers. I also left VT-d disabled but removed the "iommu=pt" from the /boot/syslinux/syslinux.cfg file and its working fine. Shame VT-d had to be disabled but at least it will give me time to sort out a new card as you suggested. So at this point, the script still appears to be relevant in some cases. Thanks again for your help, This little project has been fun so far aside a few small hiccups here n there.

OMG Thanks - that actually helps and makes sense (well sort of). So i had 3 sata controllers 2x AHCI 01:00.0 RAID bus controller: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller (rev 01) Subsystem: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller 03:00.0 RAID bus controller: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller (rev 01) Subsystem: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller and 1 IDE/PATA 05:00.0 RAID bus controller: VIA Technologies, Inc. VT6421 IDE/SATA Controller (rev 50) Subsystem: VIA Technologies, Inc. VT6421 IDE/SATA Controller So when i was enabling the script and got them errors in the log, i guess there was a conflict on who it was trying to bring up and how. Now that i have removed it, its working and i can see both cards as well as the disk's connected to them. Cheers for your help bud!

Yes, sorry I had turned it back on. Its off now.

Here is my diagnostics files. thanks for helping look into this.

Thanks for pointing me to that @johnnie.black but upon trying the suggestion there, it still does not appear to pickup my HDD's. I stopped using that script as it just continued to give me that same error in the logs. I added the "iommu=pt" in the syslinux.cfg and also disabled VT in bios. # cat syslinux.cfg default /syslinux/menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append iommu=pt initrd=/bzroot label unRAID OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label unRAID OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest # lspci -k |grep Rocket 01:00.0 RAID bus controller: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller (rev 01) Subsystem: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller 03:00.0 RAID bus controller: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller (rev 01) Subsystem: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller If I understood correctly (from all of what I have read so far), it also appears that the patch was applied some time ago so im not sure adding the iommu=pt is actually making any difference at this stage as i am using Unraid 6.3.5. Just find it odd that the system can see the correct information regarding the cards i have installed, but i cant see the disk/s attached.

I'm not sure what i missed and this is a fairly old thread but i cant seem to get my raidrocket 620 to work with unraid. my log shows Aug 26 16:20:48 Tower kernel: ata15: softreset failed (1st FIS failed) Aug 26 16:20:48 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:20:48 Tower kernel: DMAR: [DMA Write] Request device [01:00.1] fault addr 459d60000 [fault reason 05] PTE Write access is not set Aug 26 16:20:48 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:20:48 Tower kernel: DMAR: [DMA Read] Request device [01:00.1] fault addr 459d60000 [fault reason 06] PTE Read access is not set Aug 26 16:20:58 Tower kernel: ata15: softreset failed (1st FIS failed) Aug 26 16:20:58 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:20:58 Tower kernel: DMAR: [DMA Write] Request device [01:00.1] fault addr 459d60000 [fault reason 05] PTE Write access is not set Aug 26 16:20:58 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:20:58 Tower kernel: DMAR: [DMA Read] Request device [01:00.1] fault addr 459d60000 [fault reason 06] PTE Read access is not set Aug 26 16:21:33 Tower kernel: ata15: softreset failed (1st FIS failed) Aug 26 16:21:33 Tower kernel: ata15: limiting SATA link speed to 3.0 Gbps Aug 26 16:21:33 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:21:33 Tower kernel: DMAR: [DMA Write] Request device [01:00.1] fault addr 459d60000 [fault reason 05] PTE Write access is not set Aug 26 16:21:33 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:21:33 Tower kernel: DMAR: [DMA Read] Request device [01:00.1] fault addr 459d60000 [fault reason 06] PTE Read access is not set Aug 26 16:21:38 Tower kernel: ata15: softreset failed (1st FIS failed) Aug 26 16:21:38 Tower kernel: ata15: reset failed, giving up Aug 26 16:20:58 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:20:58 Tower kernel: DMAR: [DMA Read] Request device [01:00.1] fault addr 459d60000 [fault reason 06] PTE Read access is not set Aug 26 16:21:33 Tower kernel: ata15: softreset failed (1st FIS failed) Aug 26 16:21:33 Tower kernel: ata15: limiting SATA link speed to 3.0 Gbps Aug 26 16:21:33 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:21:33 Tower kernel: DMAR: [DMA Write] Request device [01:00.1] fault addr 459d60000 [fault reason 05] PTE Write access is not set Aug 26 16:21:33 Tower kernel: DMAR: DRHD: handling fault status reg 2 Aug 26 16:21:33 Tower kernel: DMAR: [DMA Read] Request device [01:00.1] fault addr 459d60000 [fault reason 06] PTE Read access is not set Aug 26 16:21:38 Tower kernel: ata15: softreset failed (1st FIS failed) Aug 26 16:21:38 Tower kernel: ata15: reset failed, giving up Aug 26 16:24:48 Tower sshd[5139]: Accepted none for root from 10.1.1.14 port 51364 ssh2 Aug 26 16:26:46 Tower emhttp: shcmd (24): rmmod md-mod |& logger Aug 26 16:26:46 Tower kernel: md: unRAID driver removed What I have done so far: I downloaded your script which shows my rocketraid in the list. I added the script to the go file ~# cat /boot/config/go #!/bin/bash # Enable AHCI Mode for e.g. RocketRAID 620 /boot/config/enable_ahci.sh # Start the Management Utility /usr/local/sbin/emhttp & Checking to see if unraid has picked up my devices (I have 2 cards): ~# lspci -nn |grep Rocket 01:00.0 RAID bus controller [0104]: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller [1103:0620] (rev 01) 03:00.0 RAID bus controller [0104]: HighPoint Technologies, Inc. RocketRAID 620 2 Port SATA-III Controller [1103:0620] (rev 01) Both Cards have been tested individually. Both cards work fine and are picked up by windows. I have changed sata cables, different hdd's and i end up with the same error. I feel like its something simple, and right in front of me but im just not winning here.