killeriq

Hello guys, Any guide where / how to setup Telegram bot for unraid? I know how to setup BOT , but not sure what to do on unRaid side. thanks

I just tested your suggestion... I probably changed the USB position by server move and the USB Controller pass through might cause the outtage. Anyway i tired to check the "New" VM ive created i have it there as well and it works Tried to Edit the GPU VM and run, its starting fine, the older one with VNC is not working and causing the outtage, so ill remove it, as the new WIN 10 VM with the same MAC as GPU VM works fine so i guess its sorted out. Thanks

Ok re-adding diagnostics after the error occurred. Tried to Recreate Win 10 VM profile with the same settings and it works... So only one thing which comes in my mind is: the "original" Win 10 VM are 2 cloned / XML edit versions 1. Win 10 with VNC 2. Win 10 with 2x GTX 1080ti Is due to the fact if im using Cards in other (Linux) VM and i want to start Win 10 with the same settings,MAC etc but via VNC. So maybe with new releases something changed in VM settings Or is there any other proper way how to clone VMs? unraidtower-diagnostics-20190907-1642.zip

Hello, Im currently on Version: 6.7.3-rc2 After some time i wanted to start my Win VM - (its via Real M2 SSD and spaces_win_clover.img), but soon as i start it i get this error: No such file or directory in /usr/local/emhttp/plugins/dynamix.vm.manager/include/libvirt_helpers.php on line 460 Log start to throw such errors: Then unRaid USB fall out and i need to reboot server... I tried to remove "/plugins/dynamix.vm.manager/" as it was suggested here on board to "recreate", tried to rename "Plugin" folder but nothing helped out. Any idea what else to try? Other Linux VM is from IMG and working fine Thanks unraidtower-diagnostics-20190907-1600.zip

getting same error msg, any progress since? Fix Common Problems: Error: Machine Check Events detected on your server Aug 7 22:08:16 unRAIDTower root: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. or where to get AMD module i dont find it in nerdpack thanks

I had this problem on Asus Crosshair Hero VI - Bios 6903 On 6808 is lastest tested and "working" Since ive tried there is newer Bios available Version 7002 2019/05/16, but i havent tried as Server is without monitor, so i would have to move upgrade , test, reconfigure bios again. Not really in mood doing that right now System is working...

Nothing to do with VM , as ive explained this only happens with latest Bios, when i revert 1 version back, all good again. Ive found few topics about the D3 error on Threadripper like 1y ago, same now with latest Bios

on 6808 bios - issue fixed with "disabling UEFI boot mode" on Unraid Flash drive on 6903 bios - still D3 error

FYI: it might help someone...i'm on v6.7.0rc7 Today ive spend couple of hours investigating what has changed after i did bios update v 6903 of Asus Crosshair Hero VI, ive started to get "2019-04-15T18:30:20.016943Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3" When i force close VM and try to start again, it wont run and is giving "internal error: Unknown PCI header type '127'" So then ive tried to go back 1 version down - v6808, D3 issue was gone. Soon as i've enabled "Permit UEFI boot mode" and booted in UEFI mode 1 card from 2x1080ti in VM is giving those errors. So ive disabled UEFI again and it was working fine. Latest FW 6903 is not working well with VMs, no clue where/what to change 2019-04-15T16:35:43.954749Z qemu-system-x86_64: -device vfio-pci,host=0b:00.0,id=hostdev0,bus=pci.0,addr=0x8,romfile=/mnt/cache/isos/Asus.GTX1080Ti.rom: Failed to mmap 0000:0b:00.0 BAR 3. Performance may be slow 2019-04-15T16:35:45.317557Z qemu-system-x86_64: vfio: Cannot reset device 0000:02:00.0, depends on group 16 which is not owned. 2019-04-15T16:35:46.387464Z qemu-system-x86_64: vfio: Cannot reset device 0000:0e:00.3, depends on group 34 which is not owned. 2019-04-15T16:35:47.407551Z qemu-system-x86_64: vfio: Cannot reset device 0000:02:00.0, depends on group 16 which is not owned. 2019-04-15T16:35:47.520017Z qemu-system-x86_64: vfio: Cannot reset device 0000:0e:00.3, depends on group 34 which is not owned. 2019-04-15T16:36:27.321705Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region3+0x40a8, 0x2bffe101,8) failed: Device or resource busy 2019-04-15T16:36:27.321756Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region3+0x15000, 0x0,8) failed: Device or resource busy 2019-04-15T16:36:27.321767Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region3+0x15008, 0x0,8) failed: Device or resource busy 2019-04-15T16:36:27.321780Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region3+0x15010, 0x0,8) failed: Device or resource busy 2019-04-15T16:36:27.321789Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region3+0x15018, 0x0,8) failed: Device or resource busy 2019-04-15T16:36:27.321801Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region3+0x15020, 0x0,8) failed: Device or resource busy 2019-04-15T16:36:27.321812Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region3+0x15028, 0x0,8) failed: Device or resource busy

Hello, seems like you are still using "old msg" - the "No" is not present anymore in settings....there are 4 other choices Warning: Your system has booted with the PCIe ACS Override setting enabled. The below list doesn't not reflect the way IOMMU would naturally group devices. To see natural IOMMU groups for your hardware, go to the VM Settings page and set the PCIe ACS Override setting to No.

tried to go to bios 6808 and now im getting those errors in VM (no D3 anymore) 2019-04-15T15:28:06.280241Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0x9008c, 4) failed: Device or resource busy 2019-04-15T15:28:06.280260Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region1+0xa0018, 0x40088,4) failed: Device or resource busy 2019-04-15T15:28:06.280274Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region1+0xa001c, 0x0,4) failed: Device or resource busy 2019-04-15T15:28:06.280289Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region1+0xa0020, 0x40084,4) failed: Device or resource busy 2019-04-15T15:28:06.280304Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region1+0xa0024, 0x0,4) failed: Device or resource busy 2019-04-15T15:28:07.610273Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0xfdf028c, 4) failed: Device or resource busy 2019-04-15T15:28:15.802311Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0xfdf028c, 4) failed: Device or resource busy 2019-04-15T15:28:23.994328Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0xfdf028c, 4) failed: Device or resource busy 2019-04-15T15:28:32.186328Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0xfdf028c, 4) failed: Device or resource busy 2019-04-15T15:28:40.378322Z qemu-system-x86_64: vfio_region_read(0000:0b:00.0:region1+0xfdf028c, 4) failed: Device or resource busy 2019-04-15T15:28:41.703547Z qemu-system-x86_64: vfio_region_write(0000:0b:00.0:region1+0xfdf068c, 0x1,4) failed: Device or resource busy --- So tried to change Settings -> VM Manager -> PCIe ACS override: to "Downstream" before i had "Both" Last time i remember there was only YES/NO option not sure with which OS update it got extended... unraidtower-diagnostics-20190415-1536.zip

@limetech - Im on Version 6.7.0-rc7 2019-04-03 and just upgraded my ASUS CROSSHAIR VI HERO bios to Version 6903 - 2019/04/11 and i start to get this issue now When i Run the VM 1st time it starts but it wont start mining, to i power OFF the VM and try to start again - getting "internal error: Unknown PCI header type '127'" In Logs: 2019-04-15T12:24:56.897909Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2019-04-15T12:24:56.902880Z qemu-system-x86_64: vfio: Unable to power on device, stuck in D3 2019-04-15T12:28:28.784776Z qemu-system-x86_64: terminating on signal 15 from pid 14010 (/usr/sbin/libvirtd) 2019-04-15 12:28:31.422+0000: shutting down, reason=shutdown ---------- Should i roll back BIOS update or what options i've got? thanks unraidtower-diagnostics-20190415-1234.zip

Hello, i just installed this Docker ...used LXTerminal to run "sudo apt get update" but is asking for password and no clue what is it? Thanks EDIT: if i install there somehting it get wiped after reboot?! Ive spend an hour installing weewx and seems like its gone

any progress guys?

hmm so seems like all changes of such "clone" needs to be done only in "raw xml" not in UI, otherwise it wont save/change it