J89eu

Members
  • Posts

    150
  • Joined

  • Last visited

Everything posted by J89eu

  1. Yep that fixed it, not using the iGPU for anything I wasn't expecting that to work, especially as the Discord seemed to agree! Nonetheless we are now working.
  2. Hi all, just branching this off from the 6.12 release. Since updating my system performance has gone insanely bad, to the point the web interface is not usable if I perform a simple task like erasing a drive... I've been talking about this loosely in the Unraid discord but seems no one is able to really concentrate on the one issue to help, and I get that, there's a lot of people asking questions that overlap, it is what it is. So I updated from a working system, no pre-existing issues. I then noticed my server seemed dead on first boot, no screen output, no ping etc, but I had to go for lunch, when I came back it was up and working. Logged in and then went to set up my cache from btrfs to ZFS and this is when I noticed these huge pauses. To cut a long story short, I have no VMs, no docker containers etc running. System is an 11400 Intel so not old nor underpowered for the task at hand! Attached CPU usage when just asking it to format a drive, being the first peak (set to 5M) and then after startng the array with also the TOP output from console. Diagnostics also attached. I have also updated my BIOS since having the issue, diagnostics are from before this. I've also recreatd a fresh USB image and transferred over my config, same issue. I have tried safe mode with no GUI and plugins, issue remains. Downgrading to 6.11.5 immediately resolves the issue. atlas-diagnostics-20230619-0928.zip
  3. Hi all, since updating my system performance has gone insanely bad, to the point the web interface is not usable if I perform a simple task like erasing a drive... I've been talking about this loosely in the Unraid discord but seems no one is able to really concentrate on the one issue to help, and I get that, there's a lot of people asking questions that overlap, it is what it is. I'm happy to separate this out to an entirely new thread if needed... So I updated from a working system, no pre-existing issues. I then noticed my server seemed dead on first boot, no screen output, no ping etc, but I had to go for lunch, when I came back it was up and working. Logged in and then went to set up my cache from btrfs to ZFS and this is when I noticed these huge pauses. To cut a long story short, I have no VMs, no docker containers etc running. System is an 11400 Intel so not old nor underpowered for the task and hand! This is the CPU usage when just asking it to format a drive, being the first peak (set to 5M) and then after startng the array with also the TOP output from console. Diagnostics also attached. EDIT: To add I just downgraded back to 6.11.5 and all my problems disappeared to this seems to be an issue specific to 6.12 for me atlas-diagnostics-20230619-0928.zip
  4. Ok well, formatted Disk5 in the end, I have no idea what was on that disk, nothing seems broken... Probably movies/TV but is there any way to work it out? Also regarding the uncorrectable errors on Disk2, I ended up with around 1200 but not sure what can be done about that? I guess the disk is just dying?
  5. Ok I will try that once this btrfs scrub runs on disk2. Currently showing 19 uncorrectable errors...
  6. So the files can't be emulated by the parity drive? Man... Yes it was definitely btrfs, I've changed nothing really.. It just randomly went read only!
  7. Thanks JorgeB, i just tried that command and got the following output No valid Btrfs found on /dev/sdl1 Open ctree failed I guess its dead? If I format this volume do I lose any data that was on the disk? Most of the other errors were down to a dodgy cable which has been replaced, not sure what to do aboutt he corruption on disk2, should I try some sort of repair there? Thanks
  8. Hi all I had a disk that went read only so after rebooting the server I now get that it's unmountable. I have attached my diagnostics and also looked through some older posts but most appear to be XFS file systems. I did try some of the things in here: But I got as far as the below where it fails: root@Atlas:~# mount -o usebackuproot,ro /dev/sdl1 /x mount: /x: wrong fs type, bad option, bad superblock on /dev/sdl1, missing codepage or helper program, or other error. and for the 2nd method root@Atlas:~# btrfs restore -v /dev/sdl1 /mnt/disk7/restore No valid Btrfs found on /dev/sdl1 Could not open root, trying backup super No valid Btrfs found on /dev/sdl1 Could not open root, trying backup super ERROR: superblock bytenr 274877906944 is larger than device size 536870912 Could not open root, trying backup super Could someone help? it's disk 5. Thanks atlas-diagnostics-20210206-2202.zip
  9. I've had a few hard locks when using my VM, VM locks up then when I killed the VM the server crashes and i get MCE errors.. I hve MCELog installed and diagnostics uploaded atlas-diagnostics-20201122-2026.zip
  10. Hi guys I am passing through my onboard Bluetooth adaptor to a VM which has all of it's cores isolated and only used for the VM. The Xbox controller picks up and pairs fine. I then go into a game and it seems to work intermittently, no matter the game.. It will work for a few seconds and then either get stuck on the last pressed button/movement or not take any inputs. It's specifically the fully wireless Xbox One controller. Anyone had this issue? Cheers
  11. Herein lies my issue, stupid me! I was adding it to extra parameters. Special thanks to Marius on the Discord for correcting me. I do feel rather embarrassed.
  12. Hey GilbN, I'm on your Discord if you wanted to chat there about it but appreciate you are not my technical support person! If you mean this line then yes I did do that:
  13. Hi, thanks for getting back to me so fast!! Here's my variables, they all seem correct to me: Also my default is indeed set: Of note is that I also get no SMART data, I did add the telegraf.conf option as advised in the 1st post. Additionally I'm on the latest 6.9 Beta if that makes any difference
  14. Hi all I've followed all the dependancies etc but not getting any disks showing, I haev the input source etc all set right... Not sure what's going on
  15. Anyone getting Kernel Security Check Failure when trying to boot from Q35 5.0 with this update on a Windows 10 VM?
  16. Hi all I was having an issue with the docker losing all stats when a setting change was made, I had this with the Unifi docker and it was caused by the interface settings. I noticed that I was not running this docker on my custom interface so I swapped to that but it wouldn't start, I managed to get it working using these settings: "Network type" I had to keep as br0 rather than my custom interface called "atlas" but I was able to get it started by settings the INTERFACE as "atlas" and the "ServerIP" as the custom IP I wanted, does that look right? Hopefully it will fix my stats being reset each time too.
  17. Tg Tried all those... SVM disabled stops any VM from working at all, IOMMU beeing enabled or disabled didn't seem to change anything!
  18. A lot of these issues seem like what I have been facing on these 2 threads: I don't even know where to go next but seems I am not alone...
  19. I've now bought a 1070ti to replace the AMD card but I'm getting the exact same issue..!
  20. This forum always confuses me, someone says a one liner then you ask for more info and get nothing....
  21. Ok, I did ran that at 2666MHz with XMP off and as soon as I started the VM which span for a while before the server ground to a halt and locked up again Why? I don't understand
  22. Ah ok, interesting, will give that a go and it it works I'll try and find some memory that actually is the advertised speed!
  23. Hi, I can try that though my RAM is 3200MHz Corsair Vengeance LPX CMK32GX4M2Z3200C16
  24. Hi all, I'm having a real nightmare with Unraid lately. I had everything working on the Unraid version that had Linux kernel 5 in, stable as anything, no reboot bug on my AMD GPU, VM working flawlessly and then since that update was pulled and the next one reverted to kernel 4 the issues started. My install is *currently* set at the unraid 6.9 beta to try and sit at what the 6.8 version was. AMD Ryzen 3700x MSI B450 Carbon AC Motherboard Vega 56 GPU 8x drives 2x SSD for cache 1x NVMe M.2 used for passthrough Creative Z Soundcard LSI 9208 (i think) RAID card Symptoms I currently have without the VM Plugins page extremely slow to load Random Dynamix errors in the log, tried to remove plugins that I thought were causing this but still get them, 3 examples: /bin/sh: line 1: 18906 Segmentation fault /etc/rc.d/rc.diskinfo --daemon &> /dev/null /etc/cron.hourly/user.script.start.hourly.sh: line 2: 17357 Segmentation fault /usr/local/emhttp/plugins/user.scripts/startSchedule.php hourly /bin/sh: line 1: 19893 Segmentation fault /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null Symptoms with the VM When starting it, sometimes locks the server up If I do the AMD reboot script that spaceinvaderone made to drop the GPU and then put the server to sleep and then start the VM, sometimes works, mostly doesn't, sometimes works for a few hours then the server locks up I posted a thread here I didn't really get anywhere with it, tried the custom Vega/Navi patches, no changes to note. You can see in that thread that I tried a lot of things like a fresh USB stick If I can get the VM to work for more than a day it will work until the next server reboot absolutely fine, and an example of the XML for that VM would be as follows <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 10</name> <uuid>b6aeda16-43c9-b72d-b2b2-f77ebbe8c9b3</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>16777216</memory> <currentMemory unit='KiB'>16777216</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='4'/> <vcpupin vcpu='1' cpuset='12'/> <vcpupin vcpu='2' cpuset='5'/> <vcpupin vcpu='3' cpuset='13'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='14'/> <vcpupin vcpu='6' cpuset='7'/> <vcpupin vcpu='7' cpuset='15'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/b6aeda16-43c9-b72d-b2b2-f77ebbe8c9b3_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <hyperv> <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'> <topology sockets='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='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.173-2.iso'/> <target dev='hdb' bus='sata'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'/> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <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='0xb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0xc'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x4'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0xd'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x5'/> </controller> <interface type='bridge'> <mac address='52:54:00:89:0f:af'/> <source bridge='br0'/> <model type='virtio'/> <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='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2b' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/Powercolor.RXVega56.8176.170730.rom'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2b' slot='0x00' function='0x1'/> </source> <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='0x26' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc262'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x1e7d'/> <product id='0x2dcd'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x2516'/> <product id='0x0004'/> </source> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> </hostdev> <memballoon model='none'/> </devices> </domain> I'm at my wits end, I just do not have anything solid to point the issue at. I can't work it out. I can get the VM working sometimes but it's always some random series of rebooting, running the SIO script, starting the VM, praying.. Nothing consistenly works. I'll add a diagnostics shortly if anyone reads this before I've added it.. Help?! atlas-diagnostics-20200422-0857.zip