mauriceatkinson@btconnect.

I have updatedto 6.12.10 and still the issue of not being able to connect via zerotier unless you add the comma in the listening interface exists. I am going to raise a support call and see if I can get this on the fixing radar.

I have the same issue with the parity disk being disabled. I swopped this out for a new drive and all worked for a few weeks and now the new replacement drive is showing as disabled. I have looked at the diagnostic data for the failed drive but I am at a loss as to the probelm. I have attached the diagnostic zip file and would appreciate any direction as to what is causing the issue. cheers Maurice freedom-diagnostics-20240409-2016.zip

Yes notifications is enabled and in summerized display. i am not aware of any specific Unraid Connect settings I need to make. is there any?

I have just seen on one of my Unraid servers that the parity disk is disabled. Not sure why but I will swop out the disk. However the only way I found out was when I directly accessed the unraid server. I also use the Unraid Connect dashboard/plugin to keep an eye on the servers but this did not indicate any problems with the server which I am very surprised about as this is such a severe problem The Unraid Connect dashboard shows the server with the green online icon. There is no indication that the parity disk is disabled. This is a major flaw with the Unraid Connect plugin/dashboard and needs to be included in the next update

Not sure if anyone else has this problem but.. my config is as above but I find that whenever the unraid server is powered off or crashes I cannot get access to the unraid server via zerotier. According to my.zerotier.com the server is up and I can ping it. I have found that if I add a comma after the zerotier address in the include listening interfaces I can then access again remotely (until another reboot/crash). I would love to get this fixed.

Did you get this resolved as I have the same issue?

I have been running a Home Assistant VM for a few years with no problems but it now fails to start with the message " Execution error - internal error: process exited while connecting to monitor" I have attached the diagnostics file and would appreciate any pointers to resolve the issue. cheers Maurice aarc-diagnostics-20240208-0135.zip

@xtrap225 are you remotely rebooting your Unraid server running Mesh Central and Intel AMT? I can reboot my local Unraid server using web AMT but am struggling to find out how to install/run Mesh on my Unraid server. Cheers

I run an external Mesh Central server to manage my remote servers and workstations so I can use Intel AMT to remotly power cycle the devices. I would like to add my three Unraid servers into Mesh Central and wonder if anybody has already done this. I have Intel AMT active on all the Unraid servers but I need to run a MeshCMD command for an agentless join or I need to install the Mesh agent software to get the servers to join my Mesh Central system. Can anyone give me any pointers as to how to achieve this? Cheers Maurice

Hi I wonder if anybody has got the Grafana docker to work with ssl? I am installing Grafana to connect to an existing influx db in order so it can be used to make a single dashboard panel available to an external web page. In order to embed the grafana dashboard panel iframe I need to be using https so trying to see if anybody has got ssl working with this docker container. I am new to docker and whilst I can see the Grafana commands needed I cannot run this as sudo. Any help or direction to implement ssl in the container would be much appreciated.

I have an intermittant problem where a working VM will not restart due to a missing usb. When unraid is restarted I often see this particular VM stopped. When looking in the vm unraid setup the required usb is passed through but not enabled - instead the "missing usb" is enabled and the vm wont start. Disabling the missing usb and re-enabling the correct usb means I can restart the vm. Does anyone have any idea as to why the passed through USB is not being seen and stopping the vm starting? cheers

With the X13SAE-F being such a powerful motherboard it is a shame there is no support for 10gbe that I can see.

I am running 6.11.5 and having issues with vm's stopping. In the logs I am seeing this error. I am running 4 x vms and 2 docker containers on an i7 8700K with 32gb of memory. Does anybody have any ideas how to resolve. aarc-diagnostics-20230213-1511.zip

thanks for info but not sure about the corrupted vdisk. I eventually got the vm to start but I am now seeing the vm stopping periodically. When I start the vm I am seeing this error in the logs. Feb 13 21:53:19 AARC kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=emulator,mems_allowed=0,global_oom,task_memcg=/machine/qemu-6-HomeAssistant.libvirt-qemu,task=qemu-system-x86,pid=26652,uid=0 Feb 13 21:53:19 AARC kernel: Out of memory: Killed process 26652 (qemu-system-x86) total-vm:18519360kB, anon-rss:17569780kB, file-rss:40kB, shmem-rss:26604kB, UID:0 pgtables:36024kB oom_score_adj:0

i am still having this problem and I would welcome any ideas to resolve

After working for months with no issues I now have a Windows 11 VM stuck in an Automatic Repair loop. When the vm starts it shows the Tiano Core and shows Prepairing Automatic Repair but then the VM gets powered off. Does anybody have any ideas to resolve? Below is the VM log file text error warn system array login -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ -chardev socket,id=charchannel0,fd=38,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -chardev 'socket,id=chrtpm,path=/run/libvirt/qemu/swtpm/9-AARC Virtual PC-swtpm.sock' \ -tpmdev emulator,id=tpm-tpm0,chardev=chrtpm \ -device '{"driver":"tpm-tis","tpmdev":"tpm-tpm0","id":"tpm0"}' \ -device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:1,websocket=5701,audiodev=audio1 \ -k en-us \ -device '{"driver":"qxl-vga","id":"video0","max_outputs":1,"ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"bus":"pcie.0","addr":"0x1"}' \ -device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.4","addr":"0x0"}' \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/4 (label charserial0) qxl_send_events: spice-server bug: guest stopped, ignoring 2023-01-29 01:41:34.395+0000: shutting down, reason=crashed 2023-01-29 01:43:09.418+0000: Starting external device: TPM Emulator /usr/bin/swtpm socket --ctrl 'type=unixio,path=/run/libvirt/qemu/swtpm/10-AARC Virtual PC-swtpm.sock,mode=0600' --tpmstate dir=/var/lib/libvirt/swtpm/42c8abb6-a6d2-24d7-37f7-bcaf2d9f79ad/tpm2,mode=0600 --log 'file=/var/log/swtpm/libvirt/qemu/AARC Virtual PC-swtpm.log' --terminate --tpm2 2023-01-29 01:43:09.455+0000: starting up libvirt version: 8.7.0, qemu version: 7.1.0, kernel: 5.19.17-Unraid, hostname: AARC LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME='/var/lib/libvirt/qemu/domain-10-AARC Virtual PC' \ XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-10-AARC Virtual PC/.local/share' \ XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-10-AARC Virtual PC/.cache' \ XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-10-AARC Virtual PC/.config' \ /usr/local/sbin/qemu \ -name 'guest=AARC Virtual PC,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-10-AARC Virtual PC/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}' \ -blockdev '{"driver":"file","filename":"/etc/libvirt/qemu/nvram/42c8abb6-a6d2-24d7-37f7-bcaf2d9f79ad_VARS-pure-efi-tpm.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}' \ -machine pc-q35-7.1,usb=off,dump-guest-core=off,mem-merge=off,memory-backend=pc.ram,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format \ -accel kvm \ -cpu host,migratable=on,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff,hv-vendor-id=none,host-cache-info=on,l3-cache=off \ -m 16384 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":17179869184}' \ -overcommit mem-lock=off \ -smp 6,sockets=1,dies=1,cores=3,threads=2 \ -uuid 42c8abb6-a6d2-24d7-37f7-bcaf2d9f79ad \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=39,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device '{"driver":"pcie-root-port","port":16,"chassis":1,"id":"pci.1","bus":"pcie.0","multifunction":true,"addr":"0x2"}' \ -device '{"driver":"pcie-root-port","port":17,"chassis":2,"id":"pci.2","bus":"pcie.0","addr":"0x2.0x1"}' \ -device '{"driver":"pcie-root-port","port":18,"chassis":3,"id":"pci.3","bus":"pcie.0","addr":"0x2.0x2"}' \ -device '{"driver":"pcie-root-port","port":19,"chassis":4,"id":"pci.4","bus":"pcie.0","addr":"0x2.0x3"}' \ -device '{"driver":"pcie-root-port","port":20,"chassis":5,"id":"pci.5","bus":"pcie.0","addr":"0x2.0x4"}' \ -device '{"driver":"ich9-usb-ehci1","id":"usb","bus":"pcie.0","addr":"0x7.0x7"}' \ -device '{"driver":"ich9-usb-uhci1","masterbus":"usb.0","firstport":0,"bus":"pcie.0","multifunction":true,"addr":"0x7"}' \ -device '{"driver":"ich9-usb-uhci2","masterbus":"usb.0","firstport":2,"bus":"pcie.0","addr":"0x7.0x1"}' \ -device '{"driver":"ich9-usb-uhci3","masterbus":"usb.0","firstport":4,"bus":"pcie.0","addr":"0x7.0x2"}' \ -device '{"driver":"virtio-serial-pci","id":"virtio-serial0","bus":"pci.2","addr":"0x0"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/domains/AARC Virtual PC/vdisk1.img","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \ -device '{"driver":"virtio-blk-pci","bus":"pci.3","addr":"0x0","drive":"libvirt-3-format","id":"virtio-disk2","bootindex":1,"write-cache":"on"}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/Windows11/Win11_EnglishInternational_x64v1.iso","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"raw","file":"libvirt-2-storage"}' \ -device '{"driver":"ide-cd","bus":"ide.0","drive":"libvirt-2-format","id":"sata0-0-0","bootindex":2}' \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.229-1.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device '{"driver":"ide-cd","bus":"ide.1","drive":"libvirt-1-format","id":"sata0-0-1"}' \ -netdev tap,fd=44,id=hostnet0 \ -device '{"driver":"virtio-net","netdev":"hostnet0","id":"net0","mac":"52:54:00:26:a4:d4","bus":"pci.1","addr":"0x0"}' \ -chardev pty,id=charserial0 \ -device '{"driver":"isa-serial","chardev":"charserial0","id":"serial0","index":0}' \ -chardev socket,id=charchannel0,fd=38,server=on,wait=off \ -device '{"driver":"virtserialport","bus":"virtio-serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"org.qemu.guest_agent.0"}' \ -chardev 'socket,id=chrtpm,path=/run/libvirt/qemu/swtpm/10-AARC Virtual PC-swtpm.sock' \ -tpmdev emulator,id=tpm-tpm0,chardev=chrtpm \ -device '{"driver":"tpm-tis","tpmdev":"tpm-tpm0","id":"tpm0"}' \ -device '{"driver":"usb-tablet","id":"input0","bus":"usb.0","port":"1"}' \ -audiodev '{"id":"audio1","driver":"none"}' \ -vnc 0.0.0.0:1,websocket=5701,audiodev=audio1 \ -k en-us \ -device '{"driver":"qxl-vga","id":"video0","max_outputs":1,"ram_size":67108864,"vram_size":67108864,"vram64_size_mb":0,"vgamem_mb":16,"bus":"pcie.0","addr":"0x1"}' \ -device '{"driver":"virtio-balloon-pci","id":"balloon0","bus":"pci.4","addr":"0x0"}' \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/4 (label charserial0) qxl_send_events: spice-server bug: guest stopped, ignoring 2023-01-29 01:43:21.061+0000: shutting down, reason=crashed

thanks, could you point me to where you saw the errors - so I can learn for next time!! Brand new disk as well.

I replaced a faulty disk and the rebuild starts but after a short period of time I see the message "Read-Check 0.7 % • Paused" and I see in the logs it states the disk is reporting write errors. This is a new drive. The weird thing is the symptoms look to be the same as the previous drive I swapped out I have changed the cables around with a working drive but the issue still exists. Does anybody have any idea as to why this is happening? freedom-diagnostics-20230114-0959.zip

reseated all the disks and this looks better. sorry for posting

I had a faulty data disk which I replaced and initially all looked good with Unraid rebuilding parity. However as I could access my VM's I took a deeper look and I am now seeing lots of "disk0 read error" messages in the log. I have rebooted and in the console it states "mounting disks" but this is stuck on disk 1. I have attached the diagnostic file and I would appreciate any guidance you have in resolving this issue. freedom-diagnostics-20230110-1636.zip

I have the same issue any ideas as to the problem? Starting Freshclamd ClamAV update process started at Sun Oct 2 14:57:04 2022 daily.cld database is up-to-date (version: 26677, sigs: 2006327, f-level: 90, builder: raynman) main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr) bytecode.cvd database is up-to-date (version: 333, sigs: 92, f-level: 63, builder: awillia2) Sun Oct 2 15:07:38 2022 -> SelfCheck: Database status OK. Sun Oct 2 15:17:39 2022 -> SelfCheck: Database status OK. Sun Oct 2 15:27:40 2022 -> SelfCheck: Database status OK. Sun Oct 2 15:37:41 2022 -> SelfCheck: Database status OK.

perfect I can see it now. thanks

I dont have the check for update option. see first post with screenshot attached showing this.

I dont have a check for update option.

I am looking to upgrade my unraid to the latest verson but I am at a loss as to why I dont have any ability in the gui to upgrade. When 6.10 was released I did see an upgrade option but I thought I would wait until the initial issues were fixed. However when I now look in the tools/settings/update os I dont get the option to upgrade. Does anyone have any ideas what is wrong?