Michael Woodson

I can confirm I am having the same issues. I recently created a new VLAN for Unraid and changed the server's internal IP. The A record has not been updated, and it has been over 24 hours. The record shows incorrect IP even when queried outside my network. Is there any good way to force a refresh? on unraid 6.9.2.

An update on this to close it out. After replacing the SATA cable, and switching the SATA port the btrf errors continued after rebuild of the filesystem and docker image multiple times. I removed the suspect SATA SSD drive and went to a single cache drive and errors stopped. I have concluded that that SSD has failed and replaced it. All is restored and back to normal now.

Tonight a got a smart error "199 CRC error count" on one of the SSD drives and many errors as shown below. It seems this could be related to a bad SATA cable. I will swap the cable and power tomorrow. Any other ideas? Thank you,

I have had this continue to occur even after doing a complete format of the cache, rebuilding docker images, and restoring app data. These errors seems to occur after some Deluge activity. 2 SSDs btrfs-encrypted raid 1. Do I have a bad SSD? Is there a way to do a SSD test? tower-diagnostics-20201115-1632.zip

I have received and set up one of the Dell H200s. I have 2x new 10TB drives, which I would like to make both parity drives for the array and add the current parity 8TB drive back as a normal array disk. What is the best procedure to do this safely and smoothly? Is this guide still relevant? https://wiki.unraid.net/The_parity_swap_procedure Thank you!

This is excellent information! I hadn't considered SFF-8087 ports. How many SATA drives can this support per SFF-8087 port? It looks like 4 drives per port?!! I'm not sure that slot has the bandwidth for 8 drives. Do I need to do anything to upgrade or configure the card? What exactly is IT mode? Thank you!

I am looking to add on to my unraid server with room to grow and looking for something with an excellent track record of reliability. Willing to pay more for that quality. I didn't expect the search to be so hard. I currently have this motherboard: https://www.asrock.com/mb/intel/h97m pro4/ the card will go into the PCI Express 2.0 x16 Slot (PCIE2: x4 mode) slot. I have found this card, which seems like a good option: https://www.amazon.com/gp/product/B082D6XSZN/ref=ox_sc_act_title_4?smid=A1MK2DD7C33I65&th=1 . I uses "the Marvell 88SE9215 + JMicron JMB5xx chip". I will likely add at at least 4 more drives over the next 2 years. Any Advice? Thank you,

The method I have found to update each of the Jitsi docker involves using Portainer. In the Portainer GUI, click Stacks > selected docker-jitsi-meet -> select all and stop all -> Select each Container one at a time (i.e. click on it's name) -> Click Recreate and click "Pull latest image" and then "Recreate" -> once all are updated start all containers -> restart letsencrypt -> done @SpaceInvaderOne Is there a better way? Also, can you help enable Colibri for Jitsi stats? I can't seem to figure it out with this set up. Thank you!

Anyone know the best way to update the Jitsi containers, if necessary? Maybe in portainer?

I had a flawless 5 person meeting last night after removing the listen 80 from the above letsencrypt.conf file. Things really start to breakdown if connections are allowed through non-https, so this is critical. I am using Google domains (private domain) and forwarding directly my IP to that meet.* private domain. Now users are only taken to the https site. Additionally, I only have the 3 ports open which spaceinvader recommended. Not port 4443 as I spoke of earlier, 4443 is not a part of the quick install guide. https://github.com/jitsi/jitsi-meet/blob/master/doc/quick-install.md

I've had people complain of this as well. In fact, had someone who could not get their video to work even after trying to force the permissions on within the browser (the latest version of chrome). Others in the same meeting had no issues.

It looks like I have resolved this issue by commenting out this line of the lets-encrypt jitsimeet.subdomain.conf config file. Now things only direct to https.

Hi @SpaceInvaderOne, Correct me if I wrong, but does video bridge need port 4443 forwarded to it? https://github.com/jitsi/jitsi-meet/blob/master/doc/manual-install.md Thank you again for all you do! Edit: things seem to improve dramatically with multi-users and when switching from wifi to cellular once 4443 is forwarded to the server.

One issue I am having is that people can access a non secure version of the jitsi meet. i.e. meet.mydomain.com takes you to a http site. https://meet.mydomain.com is a secure site with the letsencrypt reverse proxy cert and that all works. I have letsencypt generating a top-level cert and a single sub domain cert as well. When I visit mydomain.com it takes you straight away to the https site basic "welcome to our site" page. I have played around with my domain settings and no luck. I have my sub domain (meet) directly resolving to my IP and same with my top level domain. I am beginning to think this may be a jitsi setting that needs to forward people to the secure site. Any help is appreciated. I have set up following Space Invader to a T, I believe. Beyond the above everything is working and I had success with a few meetings. Thank you!

+1 for some help getting this to work.

++++++1 !. This would be so helpful for me during quarantine. Edit: I see there is a broken-out Jitsi components version in the app store. Is there a way to put this in a single docker and then we can also put together an install guide?

I am running a VM as a Q35-4.1 machine in RC4. Do I need to do anything to the VM prior to moving to RC5? What was the reason to reverting to qemu 4.01? Thank you!

I have learned that this issue only effects me when my 1GBit connection is maxed out and writing to disk for about 20 seconds after which point every VM and docker grinds to a halt. Then after about another 20 seconds things start to resume and if the network activity is not complete this process repeats. I still have $100 on the table for when this is fixed. When 6.8 is fully released (Not RC) and fixes this issue, where can I donate to unraid? Thank you,

I want to add my hat into the list of people experiencing this issue with 6.7.x. I have run down what seems like every rabbit hole trying to fix the problem thinking it was related to a CPU pinning or isolation issue. I wish I had found this post sooner. There should be a list of known ongoing problems linked to the Unraid dashboard. I know Unraid runs very barebones as a company, but this seems like an urgent issue. Indeed, Unraid is not that expensive, but I have come to rely on it more and more. I think it should be priced higher and even have an ongoing monthly fee to fund a higher level of development work. Therefore, also mark me down as someone willing to pay for a higher level of support and development and premium features. Unraid was born out of a group of people who wanted something better and now is going more mainstream to less technically savvy people. This issue has been extremely troublesome to me, and I have spent so much time on it that I will donate $100 to whoever proves they find the fix.

I experienced this same error on 6.6.1. I had to recreate the VM by first creating a new Windows 10 VM and then copying over the old XML and relinking the image. The new VM with the same XML did not yield the error which I did not understand. 2 VMs with the same XML. One would start, and the other would give the error below. This is a detail of my post from Sept. 29th. -->

Linux 4.18.10-unRAID. root@Tower:~# for usb_ctrl in $(find /sys/bus/usb/devices/usb* -maxdepth 0 -type l); do pci_path="$(dirname "$(realpath "${usb_ctrl}")")"; echo "Bus $(cat "${usb_ctrl}/busnum") --> $(basename $pci_path) (IOMMU group $(basename $(realpath $pci_path/iommu_group)))"; lsusb -s "$(cat "${usb_ctrl}/busnum"):"; echo; done Bus 1 --> 0000:00:1a.0 (IOMMU group 5) Bus 001 Device 002: ID 8087:8009 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 2 --> 0000:00:1d.0 (IOMMU group 10) Bus 002 Device 002: ID 8087:8001 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 3 --> 0000:00:14.0 (IOMMU group 2) Bus 003 Device 003: ID 13fe:1f00 Kingston Technology Company Inc. Kingston DataTraveler / Patriot Xporter Bus 003 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 4 --> 0000:00:14.0 (IOMMU group 2) Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Below is a new Windows 10 VM I created as a workaround that links to the same disk image above which does start:

I am getting the same error "XML error: Attempted double use of PCI Address 0000:00:07.0" after editing a Windows 10 VM after upgrade to 6.6.1. Would not save the configuration and the VM would not start. I tried to edit the VM to use USB 2. Now neither will work. The error on the start of the VM is "unsupported configuration: usb controller type ich9-usb-ehci1 doesn't support 'ports' with this QEMU binary" Below is XML:

Agreed. As a new unraid user this has been a real pain to get gpu pass through with my single gpu nvidia setup. Still working on it.