CybranNakh

Could someone help me with this? I had used this command perfect in 6.11.x but now in 6.12.x, I am pulling my hair out. I keep getting "This isn't an XFS filesystem or filesystem image." Here is what I have done: 1) xfs_undelete was installed on my unassigned device 2) I confirmed the download of dependencies needed with nerd pack 3) Stopped the array 4) Cd into the xfs folder 5) ./xfs_undelete -t 2023-09-01 -o /mnt/disks/temp /dev/md1p1 This isn't an XFS filesystem or filesystem image. I have tried /dev/sdj , /dev/sdj1, /dev/md1, /dev/mdp1 to no avail. Any adivse? Thank you!!!! Edit: SOLVED. I am using XFS encrypted which makes it impossible, I believe for xfs_undelete to even recognize it as the correct file system. Luckily, my data was first on an unassigned device which I could use undelete on. I need better backup protocols for data on the array it looks like!

I got fumagician to run, but when scanning it is not detecting my drives. I have my nvme’s on an asus PCIe breakout board, so it is not detecting my SSDs. Is this possibly my problem? Or are my serial numbers not eligible for update?

I am surprised the Remmina image is not used by more.... I have found it much more reliable than Apache-Guacamole which uses an older security protocol. This results in the inability to connect VNC to many clients such as raspberry pis without lowering the authentication protocol to legacy versions. With Remmina, I have no such problems. However, I am not sure why, but none of my icons within remmina load properly. All the icons are the same image. Is this an issue with my install or more generally with the image? I have uninstalled and re-installed several times. Cheers!

Got it. Thank you very much!

So what does this mean for me? I have a mount for security camera footage I use an UD for. It is currently mounted at /mnt/disks/security_recordings. Am I right in my interpretation that the recommendation is the move that to /mnt/addons/security_recordings? The only mapping of this folder is to Frigate If that is the case, does this mean I should delete the /disks and /remote folders?

So from inspecting the file activity, I could not find the culprit... however... the weird writing issue has gone away... the only major change I have made was disabling NZBget from writing logs for every action, but that would only impact my writes to the cache drives.... so, oh well. I guess it solved itself! Thank you!

Thank you guys for the comments! I guess I was thrown by the parity reads matching the array disks. I have downloaded and set up the file activity plugin. I ran it so I guess I will just have to wait and see if it catches anything suspicious going on. I will report back once it happens again to see if it catches anything. Cheers!

Hello! Well the title says it all. I am having a very very peculiar issue where usually overnight but also sometimes throughout the day, something is continually reading and writing to the array (usually Disk2). Now this is sometimes a "common" problem with unraid. The part that is thrown me for a curve is that it is ALSO reading and writing an equivalent amount of data to the parity drive. No errors being corrected that I can see. 1) I have tried restarting docker which I thought fixed the problem for a couple days... but then it came back. 2) iotop was not useful given the intermittent issue 3) I tried disabling party check scheduler which again stopped the problem for a couple days I think but could be a coincidence 4) I disabled ALL docker containers which did nothing so I dont think it is a container writing that much. Any help or guidance or direction is appreciated! I got to solve this before my drives go bust! apollo-diagnostics-20230125-0955.zip

I also would like to know the answer to this question.... From my research of how redis is setup... my understanding is that it would be somewhat a bad idea if they are entirely unrelated databases.... but i am not an expert and I guess the only other alternative would be spinning up multiple containers

Solved my issue by removing the Nvidia Plugin and rebooting!

Hello! I am trying to get a Windows 11 VM to work with a GPU passthrough but I am having a very odd problem.... I set up the VM as per the SpaceInvader Windows11 tutorial, and then passed through a GPU, this worked (aka I can RDP into the server) but I can not update the drivers of the GPU, nor can I see it under device manager. I set multifunction on and made sure all 4 parts of my GPU where on the same slot on Bus 4. I do have the Nvidia plugin as well as GPU stats on my server. Could these be interfering with the passthrough? It is the only GPU on the server but it is a server GPU which has integrated GPU capabilities and I ran the server without a GPU for some time already. Any and all help is appreciated! The GPU is a Asus RTX2060. I have attached my XML as well. Thank you! <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 11</name> <uuid>7ab8b9b6-c479-c148-66c8-408679685bbb</uuid> <description>Video Editing</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 11" icon="windows11.png" os="windowstpm"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='20'/> <vcpupin vcpu='1' cpuset='84'/> <vcpupin vcpu='2' cpuset='22'/> <vcpupin vcpu='3' cpuset='86'/> <vcpupin vcpu='4' cpuset='24'/> <vcpupin vcpu='5' cpuset='88'/> <vcpupin vcpu='6' cpuset='26'/> <vcpupin vcpu='7' cpuset='90'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-6.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi-tpm.fd</loader> <nvram>/etc/libvirt/qemu/nvram/7ab8b9b6-c479-c148-66c8-408679685bbb_VARS-pure-efi-tpm.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='4' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <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='qcow2' cache='writeback'/> <source file='/mnt/user/domains/Windows 11 Editing VM/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows/Win11_English_x64v1.iso'/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.217-2.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x8'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x9'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0xa'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='7' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='7' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <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'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:a6:c8:c9'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <tpm model='tpm-tis'> <backend type='emulator' version='2.0' persistent_state='yes'/> </tpm> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x1'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x2'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x2'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x3'/> </hostdev> <memballoon model='none'/> </devices> </domain>

Look to be, yes. Using NTP, correct timezone, and google time servers.

Hello! I have installed Guacamole according to the SpaceInvaderOne video but when enabling TOTP, I get to the login QR code and I am able to add the MFA to the Microsoft Authenticator, but it continually tells me "Verification failed. Please try again". I have tried a clean reinstall, and clearing browser history and a different browser. I have also tried a different MFA app. Nothing seems to work. Any ideas? Thank you very much!

+1 This worked! Thank you very much!

It really is unfortunate... I was so excited to set it up. I might try and see if I can find something on the github repository and report back....