paulmorabi

I'm looking to get this running for communicating Unraid status via SNMP with CheckMK (as the agent seems to not run well on Unraid and the plugin for it has been abandoned). From reading the previous posts, it seems there is an issue with this plugin persisting. If I proceed with setting this up, what do I need to do to make sure the rocommunity string remains public? (am very new to SNMP so excuse me if its a silly question).

Hi, After a few days of testing, I've tried the following: * The disk is connected to an LSI card. I have 2x 4-way data cables for connecting to disks. I swapped the data cable for a spare on the other cable. Still got the same error. * I have a power cable splitter that has 4x cables for connecting to disks. I swapped the power cable for an unused cable. Same error. * Replaced the power splitter cable entirely. Same error. * Plugged the disk into a free SATA power cable plug coming from the PSU. Same error. The error is: When it first occurred on Thursday, the next failure was nearly 24 hours later. It's now occurring at increasingly smaller intervals, down to only 3-4 hours. SMART extended self test reports no issues. Nothing else has changed in terms of hardware since the end of last year and between then and last week, this was never an issue. Could it be the disk or should I investigate further?

Hi, I've had a perfectly running Unraid system for a long time now and for the first time yesterday, one of the drivers in my array was disabled. The errors in syslog were: I rebooted, took the disk out of the array, added it back in and did a data re-build. Less than 24 hours and it has happened again to the same disk. SMART reports no issues. I've attached diagnostics. Any idea what this could be? Any help would be very appreciated. fatboy-diagnostics-20220812-1900.zip

Hi, has anyone been able to make a config with this plugin and the latest Unraid? The Apply button only greys out when i leave number of backups to keep and days retention to 0. Any other value and it has a red line underneath the input field and apply button does nothing. I've tried to uninstall and reinstall but now on reinstall its not showing in settings either

Thanks. I'll give it a try.

Unplugged everything and reconnected the cables, cleaned connection. It seems to be working fine. Taking a backup of everything now just in case.

Attached. fatboy-diagnostics-20220628-0547.zip

Hi, I noticed my VM's were all down and this in the logs: Jun 27 22:19:42 FatBoy kernel: nvme nvme0: I/O 44 QID 1 timeout, aborting Jun 27 22:19:42 FatBoy kernel: nvme nvme0: I/O 45 QID 1 timeout, aborting Jun 27 22:19:42 FatBoy kernel: nvme nvme0: I/O 224 QID 7 timeout, aborting Jun 27 22:19:42 FatBoy kernel: nvme nvme0: I/O 225 QID 7 timeout, aborting Jun 27 22:20:11 FatBoy kernel: nvme nvme0: I/O 29 QID 0 timeout, reset controller Jun 27 22:20:12 FatBoy kernel: nvme nvme0: I/O 44 QID 1 timeout, reset controller Jun 27 22:22:12 FatBoy kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 Jun 27 22:22:12 FatBoy kernel: blk_update_request: I/O error, dev nvme0n1, sector 1230365384 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Jun 27 22:22:12 FatBoy kernel: blk_update_request: I/O error, dev nvme0n1, sector 1230238336 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Jun 27 22:22:12 FatBoy kernel: nvme nvme0: Abort status: 0x371 Jun 27 22:22:12 FatBoy kernel: nvme nvme0: Abort status: 0x371 Jun 27 22:22:12 FatBoy kernel: nvme nvme0: Abort status: 0x371 Jun 27 22:22:12 FatBoy kernel: nvme nvme0: Abort status: 0x371 Jun 27 22:23:12 FatBoy kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 Jun 27 22:23:12 FatBoy kernel: nvme nvme0: Removing after probe failure status: -19 Jun 27 22:24:13 FatBoy kernel: nvme nvme0: Device not ready; aborting reset, CSTS=0x1 Jun 27 22:24:13 FatBoy kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 1, flush 0, corrupt 0, gen 0 Jun 27 22:24:13 FatBoy kernel: nvme0n1: detected capacity change from 2000409264 to 0 Jun 27 22:24:13 FatBoy kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1, rd 1, flush 0, corrupt 0, gen 0 Jun 27 22:24:13 FatBoy kernel: BTRFS error (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 1, rd 2, flush 0, corrupt 0, gen 0 Jun 27 22:24:13 FatBoy kernel: blk_update_request: I/O error, dev nvme0n1, sector 1195311008 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 On reboot, my cache disk is not detected. I'm guessing it is completely dead? Is there any chance it could be recovered? Anything I can do? Thanks,

OK, thanks. I’ll wait for the next release of the kext with Monterey support and add it to my OC. Is any special configuration required? Are there any compatibility issues with the latest betas of Monterey? I was considering moving my OSX to a separate SSD and passing through a dedicated SSD rather than using an image file. When Monterey arrives, I’ll do a clean reinstall and then restore from Time Machine. If so, I’ll use the same OC EFI and get a 12.0 install image.

Is this going to be needed for upgrading to Monterey?

Sorry for the late reply, I didn’t get a notification. Sadly, I didn’t get anywhere with this. I tried pinning and assigning CPU cores to VM’s and that has possibly reduced the instances of this occurring but it still happens every 1-2 days. It seems to be harmless or have no long lasting effect but am also curious what is behind this and the cause of it.

Sent!

Thank you so much for this. Normally I read the release notes and look at the section for breaking changes but otherwise leave as is (I thought, mistakenly, this would be OK). I have replaced the entire EFI with the one you sent me. It's still freezing on startup.

Oh I thought the second message was for @ab5g. I'm running Big Sur but have sent you a PM with a link to the EFI backup. Thanks again.

I actually have custom/SSDT-EC-USBX.aml already and still freezing on boot. Anything else I should try?

Thanks for this. I replaced the config.plist and also added the kext. System froze on Apple logo and loading screen. Is there anything I can do to test further? EDIT just noticed in config.plist it is referring to custom/SSDT-EC-USBX.aml. Do I need this file? I made the other change to the XML also. Thanks.

I've just sent over both to you via private message. Thank you!

Issues are minor but mostly with USB devices which go to sleep and then not wake unless disconnected and reconnected. Also, when I reboot with my webcam plugged in, boot hangs on BIOS screen. Hand-off is also not working (blank screen) but doubt this is related. And more generally, also want to learn how to inject kexts and get this working properly. Am running Unraid 6.9.2 on Gigabyte Aorus Pro X570 with AMD 3600XT. I'm passing through an RX570, Fenvi T919 and an FL1100 cards. Running Open OpenCore 0.7.1 and Big Sur 11.5.1 in the VM. The XML config is: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='5' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>OSX</name> <uuid>c1cad360-c374-42a3-5160-db74ac775f67</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="BigSur.png" os="linux"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='7'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='8'/> <vcpupin vcpu='4' cpuset='3'/> <vcpupin vcpu='5' cpuset='9'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-5.0'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/c1cad360-c374-42a3-5160-db74ac775f67_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/OSX Catalina/BigSur.img' index='2'/> <backingStore/> <target dev='hdc' bus='sata'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='writeback'/> <source file='/mnt/user/domains/OSX Catalina/opencorebasicbigsur.qcow2' index='1'/> <backingStore/> <target dev='hde' bus='sata'/> <boot order='1'/> <alias name='sata0-0-4'/> <address type='drive' controller='0' bus='0' target='0' unit='4'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x14'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x12'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x13'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x15'/> <alias name='pci.6'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x5'/> </controller> <controller type='pci' index='7' model='pcie-to-pci-bridge'> <model name='pcie-pci-bridge'/> <alias name='pci.7'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-5-OSX/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <input type='keyboard' bus='usb'> <alias name='input3'/> <address type='usb' bus='0' port='3'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/domains/OSX Catalina/Ellesmere.rom'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0a' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x06' slot='0x00' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x0b' slot='0x00' function='0x0'/> </source> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> <qemu:commandline> <qemu:arg value='-device'/> <qemu:arg value='isa-applesmc,osk=xxxxxx(c)AppleComputerInc'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/> </qemu:commandline> </domain> IOMMU groups on Unraid: Hackintool shows the FL1100 but says nothing about the ports: ioreg shows this for the FL1100: I know I need to update the config.plist, add SSDT and load some kexts but not sure which kexts and what to put in each of the files. From reading page 32, I need to copy the kexts, and then update the config.plist with the attached text and good to go?

I'm having a few small issues with USB devices also. Am using an FL1100 but not doing anything with kexts etc. Everything works fine 99% of the time but occasionally have a few minor issues. Is there any intro or how to on what kexts and other config needs to be configured?

Hi, I recently moved across a Linux Debian VM to my Unraid that was previously running on Proxmox. Usually, after a few days (7+) of uptime, I begin to get errors on the terminal like this: These occur maybe 1-2 times per day until I shut down the VM, restart and then everything goes well for several days before beginning again. I don't notice anything else resulting from these errors. I've searched through the forums and have done the following to try and avoid these without success: CPU cores 0 and 1 are not assigned to any VM. Remaining cores are assigned to different VMs but no VM's are assigned the same core. Am not passing through any other hardware to the VM and system is stable and working otherwise. No issues with memtest. I'm running latest Unraid on a Ryzen 3600XT with 32GB Ram and a Gigabyte X570 Aorus Pro motherboard. Should I be worried about these and is there anything I can do further to avoid them?

Have removed the add-on from HA completely. I also removed config and container and started again with same results. There is nothing really in the error logs: READY Server listening on http://0.0.0.0:80 Failed to retrieve config file, creating new. ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:492:3) at Proxy.readFileSync (node:fs:393:35) at default (api/getServers.js:27:36) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:378:20) at SendStream.EventEmitter.emit (node:domain:470:12) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:492:3) at Proxy.readFileSync (node:fs:393:35) at default (api/getServers.js:27:36) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:378:20) at SendStream.EventEmitter.emit (node:domain:470:12) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:492:3) at Proxy.readFileSync (node:fs:393:35) at default (api/getServers.js:27:36) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:378:20) at SendStream.EventEmitter.emit (node:domain:470:12) Error: ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:492:3) at Proxy.readFileSync (node:fs:393:35) at updateMQTT (/app/mqtt/index.js:272:30) at Timeout._onTimeout (/app/mqtt/index.js:304:5) at listOnTimeout (node:internal/timers:556:17) at processTimers (node:internal/timers:499:7) { errno: -2, syscall: 'open', code: 'ENOENT', path: 'config/mqttKeys' } The secure keys for mqtt may have not been generated, you need to make 1 authenticated request via the API first for this to work ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:492:3) at Proxy.readFileSync (node:fs:393:35) at default (api/getServers.js:27:36) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:378:20) at SendStream.EventEmitter.emit (node:domain:470:12) ERROR ENOENT: no such file or directory, open 'config/mqttKeys' at Object.openSync (node:fs:492:3) at Proxy.readFileSync (node:fs:393:35) at default (api/getServers.js:27:36) at call (node_modules/connect/index.js:239:7) at next (node_modules/connect/index.js:183:5) at next (node_modules/connect/index.js:161:14) at next (node_modules/connect/index.js:161:14) at SendStream.error (node_modules/serve-static/index.js:121:7) at SendStream.emit (node:events:378:20) at SendStream.EventEmitter.emit (node:domain:470:12) Get Docker Details for ip: 192.168.1.66 Failed Request failed with status code 503 Get Main Details for ip: 192.168.1.66 Failed Request failed with status code 503

Thanks for replying. Yes, something is very odd and this is after months of there being no issues. The only thing that changed is I moved my Home Assistant to a different VM and restored from backup. Even then, it seemed to work afterwards but die later. I've tried with one container, alternatively on the HA VM and the Unraid box and each gives the same result, albeit, slighttly different behavior: * On the Unraid box, after logging in, it does not show a second pop up window to log in again. It loads the details of the VM but only very partiually, no containers, vm's or anything. * On the HA VM, the container asks me to login again after the first auth and then does similar to above, only displaying a few details. Then the logs begin filling with 503 errors.

I've suddenly started noticing these errors: Get VM Details for ip: 192.168.1.66 Failed Request failed with status code 503 There's nothing else I can see in the logs. When I access the WebUI, I can log in and the details for the VM momentarily appear before disappearing (and VM/docker sections are empty). Also, just to confirm, do I need to have the Unraid API running on both the homeassistant VM and Unraid?

Is it possible anyone can take a look at the updated diagnostics I've attached? This is causing me real issues as Unraid is crashing every 48-72 hours. In addition to the diagnostics: * The RX560 card I am passing through is being passed with the BIOS file dumped from it. I'm having no issues at all with the reset bug. * I'm also now passing through separate wifi and USB cards. I thought this would reduce the crashes as I suspected it was related to passing the mainboard's usb bus but it's not helped at all. In any case, both of the cards are not affected also by pass through or reset issues. * I can stop and start the VM without any reset or passthrough issues. Since getting separate cards for usb and wifi, I've noticed that rather than freezing, Unraid crashes and reboots. * There are no other temperature issues. Everything is running within the default temperature thresholds. * When I am not running the VM, Unraid doesn't crash. * The crashes don't occur when I am using the VM so it doesn't seem related to any user activity. * RC1 and previous releases of 6.9 never exhibited this issue. I had an occasional crash but it was 12 over several months (if that). fatboy-diagnostics-20210215-1716.zip

An update for anyone who is interested in trying this. I ended up going with the 2 port Inateck USB 3 card (with an internal port also). I connected the internal USB port to the Fenvi card to enable Bluetooth. As I passed through both cards, it "just worked". I removed the virtual Ethernet port and reset network settings so en0 is wifi. Overall, it's working much, much better than passing through USB from my x570 and using a Bluetooth dongle. The only thing I've noticed is that when under heavy network activity, Bluetooth audio can jitter momentarily. I haven't tried continuity, hand-off etc. yet. I also haven't had any reset issues with either card, both resetting within the VM and powering it on and off also.