Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. looking for a bit of scripting help... I am trying to fetch a TV Guide (xml file) that is around 40Mb. The server is unreliable. using this: curl -L --limit-rate 200K "http://provider.url/epg?username=un&password=pw" --speed-time 15 --speed-limit 1000 -o /mnt/user/appdata/tvheadend/data/cronIPTV_EPG.xml I have run this multiple times my so I know the syntax is OK. but about 3 in 5 fail!!! output: curl: (28) Operation too slow. Less than 1000 bytes/sec transferred the last 15 seconds How do I wrap this command in a loop so that it will try 10 times if it falls over with the "operation too slow" error?
  3. @Squid I can't search using dashes for some reason. If i try to search docker hub for "go-socks5-proxy" it changes it to "go socks5 proxy" causing it to load thousands of pages making it impossible to find.
  4. Yes, it took me like a month to find out a proper combination of settings to get my GPU to passthrough properly. Luckily I didn't give up
  5. Feature request: Can there be a don't remind me again box when opening this plugin? I've been debugging something and I have to restore my appdata a whole bunch of times since it's faster than writing copies, and I'm very familiar that "When a Backup is running (either manually or a scheduled backup), your docker applications will be stopped and then restarted at the conclusion of the backup" . Appreciate thinking about it.
  6. Today
  7. I have a question about a setting: In the "Docker Auto Update Settings" settings tab, there is the setting "Time to wait for docker graceful stop before killing". What unit of time does this use? Seconds or minutes? What command is used for a graceful stop versus killing? Does it kill dockerd or only containers currently running? Thank you!
  8. PCI Devices and IOMMU Groups IOMMU group 0: [1022:1482] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 1: [1022:1483] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 2: [1022:1483] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 3: [1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 4: [1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 5: [1022:1483] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 6: [1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 7: [1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 8: [1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 9: [1022:1484] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 10: [1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 11: [1022:1484] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 12: [1022:1484] 00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 13: [1022:1484] 00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 14: [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 15: [1022:1440] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 0 [1022:1441] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 1 [1022:1442] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 2 [1022:1443] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 3 [1022:1444] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 4 [1022:1445] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 5 [1022:1446] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 6 [1022:1447] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse Device 24: Function 7 IOMMU group 16: [1987:5016] 01:00.0 Non-Volatile memory controller: Phison Electronics Corporation Device 5016 (rev 01) IOMMU group 17: [1022:57ad] 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57ad IOMMU group 18: [1022:57a3] 03:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a3 IOMMU group 19: [1022:57a4] 03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a4 [1022:1485] 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:149c] 0a:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] 0a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller IOMMU group 20: [1022:57a4] 03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a4 [1022:7901] 0b:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 21: [1022:57a4] 03:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 57a4 [1022:7901] 0c:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 22: [1b21:1184] 04:00.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port IOMMU group 23: [1b21:1184] 05:01.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port [8086:2723] 06:00.0 Network controller: Intel Corporation Device 2723 (rev 1a) IOMMU group 24: [1b21:1184] 05:03.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port IOMMU group 25: [1b21:1184] 05:05.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port [8086:1539] 08:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03) IOMMU group 26: [1b21:1184] 05:07.0 PCI bridge: ASMedia Technology Inc. ASM1184e PCIe Switch Port IOMMU group 27: [1002:14a0] 0d:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Device 14a0 (rev c1) IOMMU group 28: [1002:14a1] 0e:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Device 14a1 IOMMU group 29: [1002:66af] 0f:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] (rev c1) IOMMU group 30: [1002:ab20] 0f:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] IOMMU group 31: [1022:148a] 10:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 32: [1022:1485] 11:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 33: [1022:1486] 11:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP IOMMU group 34: [1022:149c] 11:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller IOMMU group 35: [1022:1487] 11:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller IOMMU group 36: [1022:7901] 12:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 37: [1022:7901] 13:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
  9. If you are not already, try using the "Q35-3.1" machine, rather than the "i440fx-3.1" machine to which the "Windows 10" template defaults. That fixed it for me - [ASRock X570 Taichi, Ryzen 9 3950X and Radeon Vega VII] - in conjunction with the boot flag "video=efifb:off" outlined above.
  10. This is going to be a terrible post because I do not have a lot of information. I upgraded to 6.8.0-rc8 today from 6.8.0-rc7. I used the Unraid Nvidia plugin, but did not think that was the issue. After the upgrade my pfSense VM would halt while booting and never came up. I used the same Unraid Nvidia plugin to rollback to 6.8.0-rc7 and the VM booted without issue. If there are some logs that I can provide I will, but I am not sure where they would be, or even exist at this point since I rolled back and rebooted my server. I didn't see this issue reported so far from a quick search and wanted to see if anyone else was having this issue.
  11. Thanks Skitals for bring up about this f10 bios and the amazing iommu group it comes with. I couldn't get the usb controllers (or any devices) to passthrough using the vfio-pci.cfg method. BUt i was able to do it by editing my xml file. Now i don't need to buy a usb pcie card! Yay! Now lets hope we can pass the onboard audio in the future!
  12. I’ll third this. Exactly why I gave up on it some months ago. Not sure what it’s issue is.
  13. Isn't the stock cooler good enough? Are you trying to quiet it down or overclock?
  14. I am having the same problem. Wether I leave it default or specify a login and password when installing the docker it doesn't let me login. It seems to want an email for the username, but even if I specify a full email address it doesn't work.
  15. Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post
  16. Hey guys I had to setup a new controller and I used my backup and im trying to adopt my aps but my problem is with port 8080 I had to change it to 8082:8080 because my kodi-headless container is using 8080. I tried set-inform http://192.168.0.50:8082 and I also added the override inform host in settings but no luck what could I be missing?
  17. Let's see the IOMMU groups....and how is the groupings.
  18. Hey did you eventually get this to work using vfio-pci.cfg method? I can't seem to pass anything through using this method.
  19. Looking for advice on cause and how to do xfs_repair without causing further damage. Oldest diagnostics syslog had bunch of errors, looks to be caused after file system was taken offline after xfs error. Powered down and checked SATA cables, brought back up and disk 2 was unmountable and left it for advice to minimize loss. Edit: Ran xfs_repair -n on disk2 and it is a mess (1900+ lines). Last parity sync was 14 days ago and was clean. Format and rebuild? Replace disk2 and rebuild? tower-diagnostics-20191206-0312.zip tower-diagnostics-20191206-0329.zip
  20. I built a rig and am trying out Unraid. Here's the specs: Gigabyte B365M DS3H Board Intel i3-8100 Proc 16G G.Skill 9210-8i SAS in IT MODE Qty 4 Seagate 6TB SAS Disks (3 Array, 1 Parity) Kingson 1TB SSD (Cache) Roswiel 850W 80Plus Bronze PSU When I boot from my Stick, Unraid comes up fine. I setup my Array with 1 - 6TB Parity, 3 - 6TB Array Members, 1 - 1TB SSD for Cache. As soon as I attempt to start the array, I get 384 Errors on the parity disk and the Read Check Pauses itself. I've tried replacing my SAS cable, tried changing the order of the disks, tried using just two disks, tried removing the SSD.... Can't figure out why I keep getting these parity errors ONLY on the party disk, even though the Parity disk has been swapped out a few times with other disks (validated by Serial number). Not sure what else could be going on... advice??
  21. unRAID is hardware agnostic. The only hardware that matters for licensing purposes is the flash drive used to boot unRAID. Change hardware all you want. You can also extend the trial twice for 15 day each.
  22. I did some searching but couldn't seem to find a solution to my particular problem. Over black friday I picked up an M2 2TB ADATA SSD to replace my old 240GB SATA cache drive. I popped the NVMe drive in, moved the data off of my old cache drive, stopped the array, and tried to start it back up with the M2 drive as the cache drive, but I'm getting this error about "unsupported partition layout". Even when the array is stopped and the new drive is unassigned, there is a "FORMAT" button next to it, but the button is greyed out and doesn't do anything when I click it. I checked my log and I'm getting a weird looping error with unassigned devices plugin and the ca.backup plugin, but I'm not sure if those are related (log attached). Thanks for any help. log.txt
  23. Mover only acts on shares where it is enabled. If the share is cache : no or cache : only, mover won't act on that share.
  24. Hey @snoopy86, first of all thank you for all the work you put into these dockers! I have been looking into the Flickr Uploader, however I cant get it to work :/ I do have a Flickr Pro account and followed all the steps, however the validation URL does not seem to work. I only get to a page that tells me that I do not have permission to access. Are there any things I need to customize except for the folder paths during setup and the Api key / secret in the uploader.ini ? Is this app still working? I do not know a lot about the Flickr api but I took a look into it and found this : https://www.flickr.com/services/api/flickr.auth.checkToken.html Is the app still using the old authentication method ? would explain the Issue, or maybe I am just to stupid to set it up 😅 Anyway, excuse my bad English and greetings from Germany, Jason.
  25. Is there a setting in unRAID to disable mover? Scheduler setting doesn't allow you to disable it, but it does allow you to set the day of the week. Is that the best method for preventing mover from running during an unBALANCE move?
  1. Load more activity