kamhighway

Thats right. I remember having to do that. It seemed scary to wipe out docker.img. The guys who know what they are doing said they do it all the time and it should only take a few minutes to recreate it. Trust them on this.

@Naldinho, When I had the problem I learned that in Unraid 6.2 they had upgraded the version of Docker. I don't know what the new version of Docker changed, but I was told the dockers were backward compatible to the version included with 6.1.9. I don't think that is true in all cases -- but smarter people than me have said so. After nuking the docker and reinstalling it fresh, I still had the same problem. That's when I decided to upgrade to 6.2 to test the assertion that it could not be the problem. All I can tell you is that after upgrading to 6.2, the docker started working.

@chbmb Did you make any changes to nextcloud's config.php to make it work behind the letsencrypt reverse proxy?

@nojas, I think you need to enter the URL of the login screen

@noja, When you enter https://172.16.100.5:8443/cloud in a browser, do you get to the nextcloud login screen?

@seefilms Yes, you will have to set up your dockers again. I can understand your hesitation, but it is actually pretty easy to do as per Squids message.

Having a problem getting a fresh install of latest version to be able to sign into plex and claim the server. These lines from the PMS Log file seems to say that it can resolve the host name plex.tv. I am using Unraid 6.1.9 and DNS is set to 8.8.8.8 and 8.8.4.4. The docker network type is set to "Host". Maybe the problem is curl_easy_perform? Thank you for looking. Aug 01, 2016 12:16:24.914 [0x2b81e1001700] DEBUG - HTTP requesting POST https://plex.tv/users/sign_in.xml Aug 01, 2016 12:16:24.915 [0x2b81e1001700] ERROR - Error issuing curl_easy_perform(handle): 6 Aug 01, 2016 12:16:24.915 [0x2b81e1001700] WARN - HTTP error requesting POST https://plex.tv/users/sign_in.xml (6, Couldn't resolve host name) (Couldn't resolve host 'plex.tv') Aug 01, 2016 12:16:24.915 [0x2b81e1001700] DEBUG - MyPlex: Did update authToken for 'kamhighway' (returnCode: -6) Aug 01, 2016 12:16:24.915 [0x2b81e1001700] DEBUG - MyPlex: Got a token poked, let's act on it. Aug 01, 2016 12:16:24.915 [0x2b81e1001700] DEBUG - Sync: onMyPlexSignOut Update: After much experimentation, I've reached the conclusion that this docker does not function properly on UR 6.1.9. After upgrading UR to 6.2 RC3, I am now getting the expected behavior. This may in fact be a problem with all dockers that have been updated to work with the version of docker included with UR 6.2. I suspect the version of docker included with 6.1.9 is not capable of running dockers that have been updated for UR 6.2.

I've added allow_unsafe_assigned_interrupts=1 to syslinux.cfg and tried it with and without the ACS override. I still get the same error. Thanks for your help saarg. I appreciate your efforts. Update: I think I've got this working now. The answer was to uncomment relaxed_acs_check = 1 in /etc/libvirt/qemu.conf. Update: Turned off PCIe ACS override, rebooted. Confirmed that VM still starts up without error Update: Removed vfio_iommu_type1.allow_unsafe_interrupts=1 from syslinux.cfg. Confirmed that VM starts up without error.

I saw this error message in the libvirtd log: internal error: Device 0000:04:00.0 is behind a switch lacking ACS and cannot be assigned So I turned on the ACS override option. After rebooting, tried to start the VM, but got the same error message as before.

@saarg, Thanks for taking a look. tower-2-diagnostics-20160718-1408.zip

@saag I have added all 4 of the nics on the card to xml, but I still get the same error "Execution error, Requested operation is not valid: PCI device 0000:04:00.0 is not assignable." I checked the bios and vt-d is enabled. Are there any other bios settings to check? Here's xml I added for the 4 ports: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x07' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x05' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x09' function='0x0'/> </hostdev>

I have tried to follow the OP's directions and cannot get this working. I want to pass through a quad port NIC to a VM. lspci reports the 4 port card as this: 04:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) 04:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) 05:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) 05:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) lspci -n reports: 04:00.0 0200: 8086:10bc (rev 06) 04:00.1 0200: 8086:10bc (rev 06) 05:00.0 0200: 8086:10bc (rev 06) 05:00.1 0200: 8086:10bc (rev 06) I've edited syslinux.cfg to add this line: append pci-stub.ids=8086:10bc initrd=/bzroot I've added this to the xml for the vm: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> </hostdev> After I add this, I click "update" to save the changes. When I look at the XML again it shows an extra line which I've bolded: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x02' slot='0x06' function='0x0'/> <----This line was added. </hostdev> When I try to start the VM, I get "Execution error, Requested operation is not valid: PCI device 0000:04:00.0 is not assignable." I'm running unraid 6.1.9 pro. Would appreciate some help.

@CHBMB, Do you use the letsencrypt docker to do the reverse proxy?

How do I change the included ssl certificate and key to the ones I have from letsencrypt?

Thank you Squid. That fixed it. I did not realize that CA eliminated the need to have the repositories entered on the docker page.

I just used CA to install Linuxserver.io's nginx docker without any problems. Could it be that the flash drive is only a problem for the nextcloud docker?

Tried to install using community applications and got a screenful of error messages. Screenshot attached. I updated the Community applications to the latest version before clicking on the add button. Running UR 6.1.9

@GreenEyedMonster Happy to help. I went through the same learning curve you did a couple of weeks ago. Now that I know how the interface is supposed to work, I can make do with the UI as it is. I find it painful to watch dlandon have to educate us all one by one as we each go down the learning curve so I thought I'd pitch in here. Please monitor this thread and help the next guy who has the same problem to take a little of the burden of supporting this great plugin off dlandon's shoulders.

@ GreenEyedMonster Do you have destructive mode turned on? It's in Settings->User Utilities->Unassigned Devices

@tmchow telnet into your unraid server and navigate to /mnt/disks/usenet and see if the file is there.

It works great now. If I could make a suggestion, I think it would be nice to have a toggle for destructive mode next to the toggle labeled "Complete" on the main page. Then add a second button for each drive that is always there labeled "Format" and have it greyed out if the destructive mode toggle is off. If destructive mode is on, and you click the format button, have UD delete the existing partition. One more thought: Put a link to this support thread next to the words "Unassigned Devices" in the title bar of this plugin on the main page. Now that I understand how the UI works, I don't need these changes. But, I think they would make UD more intuitive so you would not have to provide as much support to the next guy who gets stuck. You did a great job on this. If you PM me an email address I can use to paypal you, I'd like to buy you a cup of coffee.

That was it. I guess when I updated UD this morning, the setting for destructive mode went back to disabled and I did not think to check. Once the drive is formated, the button toggles between mount and unmount. Is there a way to get the format button back again? Nevermind: I see now what you were trying to say yesterday. Clicking on the red X next to the partition name and then hitting enter will delete the partition and the format button reappears. This is great.

Clicking on the drive serial number does not reveal anything.

I set up a test server so I can help with debugging. I put 2 small hard drives into the test server and precleared them. The format button appears, but is greyed out. See attached image. This is with UD version 2016.04.16a. Here is what's in UD's log: Apr 14 15:48:04 Removing configuration '//192.168.8.183/cache'. Apr 16 09:26:34 Disk with serial 'ST3120213AS_4LS3VKRS' is not set to auto mount and will not be mounted... Apr 16 09:28:04 Disk with serial 'ST3120213AS_4LS3VKRS' is not set to auto mount and will not be mounted... Apr 16 10:43:07 Disk with serial 'ST3160812AS_9LS4XQQE' is not set to auto mount and will not be mounted... Apr 16 10:57:40 Disk with serial 'ST3160812AS_9LS4XQQE' is not set to auto mount and will not be mounted... Apr 16 11:32:31 Disk with serial 'ST3120213AS_4LS3VKRS' is not set to auto mount and will not be mounted... Apr 16 11:43:21 Disk with serial 'ST3160812AS_9LS4XQQE' is not set to auto mount and will not be mounted... Apr 16 13:34:57 Adding disk '/dev/sdj1'... Apr 16 13:34:57 Mount drive command: /sbin/mount -t precleared -o auto,async,noatime,nodiratime '/dev/sdj1' '/mnt/disks/ST3120213AS_4LS3VKRS' Apr 16 13:34:57 Mount of '/dev/sdj1' failed. Error message: mount: unknown filesystem type 'precleared' Apr 16 13:34:57 Adding disk '/dev/sdk1'... Apr 16 13:34:57 Mount drive command: /sbin/mount -t precleared -o auto,async,noatime,nodiratime '/dev/sdk1' '/mnt/disks/seagate160' Apr 16 13:34:57 Mount of '/dev/sdk1' failed. Error message: mount: unknown filesystem type 'precleared'

@tmchow, The web page I linked to had a pretty good explanation of each step. I don't recall there being a 2TB limit on the size of the partition. If that article does not answer your question, there were many others that I was able to find through google. When you figure it out, post back how you did it so the next person doesn't have to do the same research.