Goldmaster

Members
  • Posts

    100
  • Joined

Everything posted by Goldmaster

  1. Im having same issues with the web. page doesnt load, but only in inconeto.
  2. I think something has covertly changed my xml or something as I did this exact fix marked as solved but when i waked my server from sleep, the vm now doesn't want to boot at all. even with this fix. I take it should be like this <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> <kvm> <hidden state='on'/> </kvm> </features> Even with the xml set like this, it fails to boot and I get 2022-08-01T11:36:43.432586Z qemu-system-x86_64: vfio_err_notifier_handler(0000:2d:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest The only thing I have done is removed the nvdia plugin and that was it. it seams to have had issues waking from sleep. After trying out the fix and brefly working, I have (once again) downgraded to 6.9 its strange as if the m.2 drive cant boot. tianocore really need to fix these kind of issues. I wonder if unraid do patch the issue they could submit a merge request so that others will receive the same fix?
  3. little strange with this issue. if you dont have the nvidia plugin, then even with that fix. the vm will still not work. i removed the nvidia plugin as i think there maybe a conflic between foldingathome wanting to use the gpu and the vm using the gpu. not sure why as i can fold fine on cpu.
  4. Where have you read this? Bit strange for a perfectly working gpu to have issues like this. its quite modern only 2016. Id more likely guess that latest hardware would have temporary issues if open source drivers are not available or been updated for support.
  5. I did try vnc and that failed. I think it maybe that I have to reinstall windows 11 as I updated from windows 10 to 11. My motherboard does support windows 11 out of the box.
  6. Hi there, is there a way to backup any projects that you have starred to zip files? Please.
  7. Very quick question, Im trying to run Debian Bullseye container and have put in my root password in the container field. yet when opening a terminal and putting in my correct password it says its wrong. yet it isnt wrong as I put in the docker template
  8. Im getting this error as well. this is the video im trying to download https://www.youtube.com/watch?v=_E0QSFHR86I I have downloaded it fine with exe from youtube dlp
  9. @Yak What happens if you just run the command again? I have found that in most cases, it should just resume from where it left off. For the web interface message, is there not a button to continue or accept? Just having a look at that error part, you may want to make sure php is up to date, just run `php occ updater.phar` in terminal and see if php is up to date, then give the update another try. I find when I get issues to try running the update again as sometimes a spotty network can cause issues.
  10. This is a similar issue to what im getting on 6.10 worked fine on 6.9
  11. Hi there, I had setup a working dual boot of windows 11 on unraid 6.9 and would work fine except for the ocational freeze up. I have a gt 710 gpu passed though, and used a m.2 drive for booting off. So I can boot in bere metal, like a normal pc or as a vm in unraid. After 6.10, the vm now doesnt boot, but just starts then pause, getting stuck at the tanocore logo and no windows loading icon. this is the xml settings <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>Windows 11 dual boot</name> <uuid>986c0163-34fc-a197-0b59-fc3497b10b59</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows11.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>8</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='16'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='18'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='20'/> <vcpupin vcpu='6' cpuset='6'/> <vcpupin vcpu='7' cpuset='22'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-5.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/986c0163-34fc-a197-0b59-fc3497a10b58_VARS-pure-efi.fd</nvram> <boot dev='hd'/> </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> <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> <controller type='pci' index='0' model='pci-root'/> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:ce:87:e6'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 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'/> <audio id='1' type='none'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2f' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/isos/vbios/GeForce GT 710.rom'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2f' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2d' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'/> </domain> When trying to boot, 2 times. this is what I get in the log window -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -netdev tap,fd=35,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:ce:87:e6,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0,index=0 \ -chardev socket,id=charchannel0,fd=33,server=on,wait=off \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -audiodev '{"id":"audio1","driver":"none"}' \ -device 'vfio-pci,host=0000:2f:00.0,id=hostdev0,bus=pci.0,addr=0x4,romfile=/mnt/user/isos/vbios/GeForce GT 710.rom' \ -device vfio-pci,host=0000:2f:00.1,id=hostdev1,bus=pci.0,addr=0x5 \ -device vfio-pci,host=0000:2d:00.0,id=hostdev2,bus=pci.0,addr=0x6 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) 2022-06-11T09:40:57.090130Z qemu-system-x86_64: vfio_err_notifier_handler(0000:2d:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest 2022-06-11T13:53:49.073923Z qemu-system-x86_64: terminating on signal 15 from pid 17120 (/usr/sbin/libvirtd) 2022-06-11 13:53:50.474+0000: shutting down, reason=destroyed 2022-06-11 13:55:36.093+0000: starting up libvirt version: 8.2.0, qemu version: 6.2.0, kernel: 5.15.43-Unraid, hostname: Hammerthread LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME='/var/lib/libvirt/qemu/domain-2-Windows 11 dual boot' \ XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-2-Windows 11 dual boot/.local/share' \ XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-2-Windows 11 dual boot/.cache' \ XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-2-Windows 11 dual boot/.config' \ /usr/local/sbin/qemu \ -name 'guest=Windows 11 dual boot,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-2-Windows 11 dual boot/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.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/986c0163-34fc-a197-0b59-fc3497a10b58_VARS-pure-efi.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-i440fx-5.1,usb=off,dump-guest-core=off,mem-merge=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format,memory-backend=pc.ram \ -accel kvm \ -cpu host,migratable=on,topoext=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 8192 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":8589934592}' \ -overcommit mem-lock=off \ -smp 8,sockets=1,dies=1,cores=4,threads=2 \ -uuid 986c0163-34fc-a197-0b59-fc3497a10b58 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=36,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -netdev tap,fd=37,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:ce:87:e6,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0,index=0 \ -chardev socket,id=charchannel0,fd=35,server=on,wait=off \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -audiodev '{"id":"audio1","driver":"none"}' \ -device 'vfio-pci,host=0000:2f:00.0,id=hostdev0,bus=pci.0,addr=0x4,romfile=/mnt/user/isos/vbios/GeForce GT 710.rom' \ -device vfio-pci,host=0000:2f:00.1,id=hostdev1,bus=pci.0,addr=0x5 \ -device vfio-pci,host=0000:2d:00.0,id=hostdev2,bus=pci.0,addr=0x6 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) 2022-06-11T13:55:41.825439Z qemu-system-x86_64: vfio_err_notifier_handler(0000:2d:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest 2022-06-11T13:56:45.026047Z qemu-system-x86_64: terminating on signal 15 from pid 17120 (/usr/sbin/libvirtd) 2022-06-11 13:56:46.426+0000: shutting down, reason=destroyed -nodefaults \ -chardev socket,id=charmonitor,fd=36,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -netdev tap,fd=37,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:ce:87:e6,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0,index=0 \ -chardev socket,id=charchannel0,fd=35,server=on,wait=off \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -audiodev '{"id":"audio1","driver":"none"}' \ -device 'vfio-pci,host=0000:2f:00.0,id=hostdev0,bus=pci.0,addr=0x4,romfile=/mnt/user/isos/vbios/GeForce GT 710.rom' \ -device vfio-pci,host=0000:2f:00.1,id=hostdev1,bus=pci.0,addr=0x5 \ -device vfio-pci,host=0000:2d:00.0,id=hostdev2,bus=pci.0,addr=0x6 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/0 (label charserial0) 2022-06-11T13:55:41.825439Z qemu-system-x86_64: vfio_err_notifier_handler(0000:2d:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest 2022-06-11T13:56:45.026047Z qemu-system-x86_64: terminating on signal 15 from pid 17120 (/usr/sbin/libvirtd) 2022-06-11 13:56:46.426+0000: shutting down, reason=destroyed 2022-06-11 14:05:05.485+0000: starting up libvirt version: 8.2.0, qemu version: 6.2.0, kernel: 5.15.43-Unraid, hostname: Hammerthread LC_ALL=C \ PATH=/bin:/sbin:/usr/bin:/usr/sbin \ HOME='/var/lib/libvirt/qemu/domain-3-Windows 11 dual boot' \ XDG_DATA_HOME='/var/lib/libvirt/qemu/domain-3-Windows 11 dual boot/.local/share' \ XDG_CACHE_HOME='/var/lib/libvirt/qemu/domain-3-Windows 11 dual boot/.cache' \ XDG_CONFIG_HOME='/var/lib/libvirt/qemu/domain-3-Windows 11 dual boot/.config' \ /usr/local/sbin/qemu \ -name 'guest=Windows 11 dual boot,debug-threads=on' \ -S \ -object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-3-Windows 11 dual boot/master-key.aes"}' \ -blockdev '{"driver":"file","filename":"/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.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/986c0163-34fc-a197-0b59-fc3497a10b58_VARS-pure-efi.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-i440fx-5.1,usb=off,dump-guest-core=off,mem-merge=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format,memory-backend=pc.ram \ -accel kvm \ -cpu host,migratable=on,topoext=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 8192 \ -object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":8589934592}' \ -overcommit mem-lock=off \ -smp 8,sockets=1,dies=1,cores=4,threads=2 \ -uuid 986c0163-34fc-a197-0b59-fc3497a10b58 \ -display none \ -no-user-config \ -nodefaults \ -chardev socket,id=charmonitor,fd=36,server=on,wait=off \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x7.0x7 \ -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x7 \ -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x7.0x1 \ -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x7.0x2 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ -netdev tap,fd=37,id=hostnet0 \ -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:ce:87:e6,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0,index=0 \ -chardev socket,id=charchannel0,fd=35,server=on,wait=off \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device usb-tablet,id=input0,bus=usb.0,port=1 \ -audiodev '{"id":"audio1","driver":"none"}' \ -device 'vfio-pci,host=0000:2f:00.0,id=hostdev0,bus=pci.0,addr=0x4,romfile=/mnt/user/isos/vbios/GeForce GT 710.rom' \ -device vfio-pci,host=0000:2f:00.1,id=hostdev1,bus=pci.0,addr=0x5 \ -device vfio-pci,host=0000:2d:00.0,id=hostdev2,bus=pci.0,addr=0x6 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on char device redirected to /dev/pts/24 (label charserial0) 2022-06-11T14:05:20.898479Z qemu-system-x86_64: vfio_err_notifier_handler(0000:2d:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest Any ideas why the exact vm that works fine on 6.9 now doesn't work on 6.10? My system specs are in my signature below. I will add that I have tried recreating the vm with what I know works and I still get the same issues. Looking at the log, it appears to be the m.2 drive. I Wonder if the latest version Isn't compatible with my m.2 or something? Thank you
  12. crying out loud, I forgot to set the Post arguments: tunnel run UUID in advanced settings! now seams to work fine.
  13. I did try that and made no difference.
  14. Did you just uninstall and then cleanup the appdata? just uninstalled and im still getting the logs not loading and just flashing by. im on 6.10 and was working fine. I should not have to fix things after a stable update.
  15. Seam to having permission issues with this on 6.10
  16. Well, after updating to 6.10 stable, my vm doesn't even start. Just pauses and then get a error when trying to resume. I thought this was a stable update? Unless I need to change something?
  17. Im getting the exact same issue. Did you end solving in the end or having to give up and wait for a fix?
  18. Hi there, I currently dont know how to format it, as I currently get webpage not available when browsing on local ip. I currently have that line as bind_addresses: ['::1', '0.0.0.0'] I have followed the other parts afterwards without issue. I just get webpage not available for no reason. In the docker log I get socket: Protocol not supported This server is configured to use 'matrix.org' as its trusted key server via the 'trusted_key_servers' config option. 'matrix.org' is a good choice for a key server since it is long-lived, stable and trusted. However, some admins may wish to use another server for this purpose. To suppress this warning and continue using 'matrix.org', admins should set 'suppress_key_server_warning' to 'true' in homeserver.yaml. -------------------------------------------------------------------------------- ******************************************** Error during initialisation: unable to open database file There may be more information in the logs. ******************************************** The socket: protocol not supported is in a long list. I have tried with a fresh new config still run into the same issue.
  19. No the reason, being is that I want to be able to read the drive on windows and exfat and ntfs are the only file systems capable of doing so.
  20. Yes, the idea is that certain folders are not deleted on the destination such as $recycle.bin and system volume information.
  21. Is there a way to male sure $recycle.bin and system volume infomation folders are not deleted when backing up to an external ntfs drive in luckybackup?
  22. you could use mouse jiggler tool, basically it moves the mouse around. which I used when I needed to leave a collage computer running overnight, and it would auto log out after a set amount of inactive use. https://github.com/arkane-systems/mousejiggler
  23. I have this issue as well with my current hardware and on bios 0503. I tried turning off cstate and that didnt make any difference. windows 11 which I have installed on a m.2 for dual boot. Windows 11 works fine then will just freeze up and I have to restart the vm. Im on build 22000.613 so not sure if this is a windows or unraid settings issue. Hyper v is enabled, so i can try and use the android on windows option. I have checked the sleep and power, and they are all set for best performance with sleep and screen off disabled.
  24. I have not done many posts here or any help guides or such. So here's a post to any future users of Unraid or, more likely, to those that do bios updates. Are considering doing bios updates and how I could have avoided three days of feeling mentally bad, a bit sick to the stomach and feeling complete uncertainly. The first question is, why did I update the bios? Well, three reasons. The first point is to help improve things in a way, and from my experience, Asus can remove bios files for the transformer pro3 after some time. However, bizarrely, the bios downloads are still available. I am not sure why I did not see them around 2018/2019. It was just a blank page, and even with ublock origin turned off and tried viewing in incognito. So, I assumed the bios downloads had gone for good. It turns out they are available. Not sure if ASUS was doing a server migration or quite what? The second point for me is it adds value when it comes to selling, as you can advertise with the latest bios. But with what I had gone through, not. The third point is that I had updated the bios from version 0405 to 0504 without any issues to see if there is a fix for GPU pass-through issues I was getting. It turns out that I had to dump the bios from the GPU using @SpaceInvaderOne userscript. I updated the bios by downloading the bios (version 1003) and then following the instructions. All went well until Unraid booted up, and I was greeted with a bond0 error message and tried every option, even flashing a new stable copy onto another USB and trying the latest RC version. However, I found that I could get Unraid to boot by plugging into the back of the motherboard, but the parity and data drives did not show up. Windows 11, which I have installed on an m.2, can see all drives and works fine. So, I knew it looked like an Unraid issue. I knew that the bios update was the cause. I downloaded version 0504 as that was the last version to work and tried to downgrade using Asus Ez Flash 3, and I got the error of invalid bios file. So as far as I could tell, I could not seem to downgrade. I felt utterly stuck and mentally bad, as the issue was on my mind. However, the critical thing to do was do other things, such as volunteering to get between me and the problem. I knew that the motherboard could use bios flashback, where a user plugs in a USB stick with the bios cap file and read it by pressing and holding down a button on the back, with no CPU, ram, or anything needed. There is also the feature that if the bios get corrupted, the motherboard can read the bios file from the USB stick and reload the bios. The risk was if the asmedia controller for the SATA ports got updated during the bios update, then Unraid would not be able to read the drives plugged into the four lefthand SATA ports, which was the only place I could plug my drives in without being blocked. However, I did not know if the bios flashback feature would revert the bios by simply plugging in a USB stick or if it was for upgrade only. No information says in the manual that it can do this. Only more or less hints at it is possible. I used a SanDisk fit USB stick and moved any files and folders off the USB stick and put only the bios cap file. I made sure I shut the computer down and disconnected parity and data drives. Plugged into the bios USB port on the back of the motherboard and pressed and held the bios flashback button until the button started flashing blue. I went away and came back, and the button was off. So, it looked like it had done it. However, I did not want to try powering up if the worst-case scenario happened, and the computer did not want to start or if it made no difference. I would be thinking about it while volunteering for hospital radio. I thought I would power up once I reconnected the SATA cables for the parity and data drives. The computer booted, and I noticed the slightly older American megatrends logo and to press f1 for defaults. I also saw the bios says 0504, so I thought that is a good sign. Windows wanted to start, but I just had to turn off fast boot and set Unraid USB as the first boot option, which is now back in the USB header slot thanks to a USB two header to USB port adapter I have. Once Unraid started, all drives showed, so the array started up fine. So, I am back in business, and I can summarise up. DO NOT JUST UPDATE YOUR BIOS JUST FOR NOTHING. ASK WHY DO I NEED TO UPDATE If you have a new CPU that needs new bios, go for it. Wait for Unraid to confirm more recent updates with support for the latest bios. In the case of version 1003, which adds support for the newer threadripper pro CPUs, but, as I have found out, does not work with Unraid. So, it may be worth waiting a while before getting a CPU upgrade, and downloading the latest bios to support it, if Unraid will not work correctly. If you plan on selling the motherboard in a few years, do not bother updating the bios. It's not your problem, and the owner might not want to update the bios due to using Linux or Unraid. If you are worried about the bios vanishing from the web, then save the bios file, just in case. It is unlikely but could happen. It's also important to know what options are if a bios update goes wrong. It's far less risky than it used to be back in the 2000s. If there are windows crashes while running the bios updater tool, that is it. There are three safeguards for the Asus WRX80 to ensure you don't brick the motherboard. If the power does go out, it's not the end of the road. At least I now know that if you have an ASUS motherboard with bios flashback or something similar, you can roll back the bios rather than trying to follow a risky video. Use official methods and don't stay up late trying to fix something, as you would be tired and more likely to make a mistake that could make a bad situation worse. I will also add that if you have ipmi on your motherboard like mine, then id strongly advice to keep that part up to date, as it is browser accessible which should be local only. You don't want a security flaw to appear where a malicious person gains access to "the control room" of your server. I updated to the latest bmc without issue. I may make edits and changes to this post where needed. I hope this helps anyone else with the Asus wrx80 or an ASUS motherboard with bios rollback. If you do not have an Asus motherboard, there may be something similar that you should thoroughly research before updating the bios, which I could only describe as "the starter motor" of your computer. Just want to thank a few people on the unraid discord for helping with a simple solution to a complex illogical issue. @Fuggin, @DiscoverIt, @AgentXXL, @Offlined and @own. I will be much more hesitant in doing a bios update from now on and I hope this helps and enlightens others out there.
  25. I have tried the latest update to the container and the bug is still present. I have tried bash and shell options as well as proxy for network and no difference there? @binhex any suggestions please?