kamhighway
-
Posts
294 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by kamhighway
-
-
I used community applications to find an existing docker on docker hub. The one I chose is fbmac/mybb. I got it started using the template built by CA with almost no effort -- just mapping host port 6080 to port 80 of the container. Upon first start, I got to the setup screen and got myBB working with needo's mariaDB docker. The last set up screen said to create a blank file in /install named lock to prevent the installer from starting up again. This is where my problems started.
The container did not have nano installed, so I typed apt-get update, then apt-get install nano. Nano installed but would not start because TERM was not defined. After typing export TERM=xterm, nano started up and I created the lock file. I have figured out how to commit the changed container so the next time it starts up, nano will still be installed. However, the new container does not seem to save TERM=xterm so I find I have to export that again after each startup.
I've tried adding a variable to the template called TERM and setting it to xterm, but that does not work. I'm sure I'm missing something simple and would appreciate some help to point me in the right direction.
-
IPMI has its own IP address which is different than the motherboard's IP. On the mac, I use LanScan to list out the IPs on my network sorted by the manufacturer of the device. The supermicro board will show up on the list twice. One of them is for IPMI, and the other is for the motherboard.
Alternatively, you can use IPMIview which you can download from Supermicro. It will take a range of IP addresses and tell you which ones are IPMI.
-
@gridrunner, Just wanted to say thanks. Your post helped me too.
-
@squid, I've deleted the old docker.img, but do not see where you go to create a new one. I've looked at the advanced docker settings and filled out both fields, but a new docker.img is not created.
Update: I had entered /mnt/disks/ssd960 as the location for docker.img. This location is on an SSD that is mounted by Unassigned Devices. When I changed the location to /mnt/cache/docker it worked. Looks like you can no longer have docker.img on a disk that is mounted with unassigned devices.
-
upgraded from 6.1.9 to rc3. First problem is that the docker tab has disappeared. I have disabled and then re-enabled docker but status continues to say "stopped."
-
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.
-
Check these forums before you open the box. The problem may be resolved with the current version. Perhaps someone else who is still using this card can chime in. If no one is using this card, that should be a big red flag.
-
I would reconsider your choice of HBA.
I used to use the SM AOC-SAS2LP-MV8. It was fine under Unraid v5, but then at some point in the v6 betas a problem was discovered which by now hopefully has been resolved. I, however, could not wait for LT to fix it so I replaced it with a Dell HBA that my brother helped me flash into IT mode.
The SM HBA has been the topic of many posts in these forums. If you already have it, I would try it. The problems may already have been solved. But if you are buying a new HBA, I'd search the forums to be sure the problems have been solved before spending the money on this HBA.
-
You could try to add allow_unsafe_assigned_interrupts=1 in your syslinux.cfg after append and see if that changes anything.
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.
-
-
@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?
-
@aptalca, Thank you for your message. You hit the nail on the head. I've got the green lock now. Thanks for your efforts on this docker.
-
I've installed this docker and the log shows that the certificates were created. When I go to the letsencrypt docker webui, I see the default landing page that says the webserver is working properly. However, chrome still displays the lock with the red "X" indicating that the page is insecure. Is there something else that I need to do to get the green lock?
-
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
-
That board is for socket 2011 v3 cpus. The cheap E5 2670s on ebay are v1 cpus. v1 and v2 cpus will work in the same socket 2011 boards. But, 2011 v3 boards are not compatible with v1 or v2 cpus.
-
@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
-
I bought a couple of these about a year ago and found they had WD reds in them. They have been working fine. Earlier this year I bought two more and there were greens in them. The greens are working fine after using wdidle to change one setting. The newer green drives are also about 32MB smaller than the older drives. This makes no difference as a data drive, but I cannot use it as a parity drive because it is slightly smaller than some of the other 5TB drives.
Trying to learn docker by making one for myBB
in Docker Engine
Posted
@Squid: I can do that, but there are a ton of setting to tweak and it would be useful to be able to edit files in the container.
An alternative is to map the document root to a /mnt/cache/appdata/mybb. But when I did that mybb would not start saying I didn't have permission. I checked the permissions that mybb said were important and found them to be fine. I think the issue has something to do with the owner of the files on /mnt/cache/appdata/mybb is not the same as the owner of the original files in the container.