Jump to content

killeriq

Members
  • Content Count

    278
  • Joined

  • Last visited

Community Reputation

8 Neutral

About killeriq

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Seems like it fixed my issue, Thanks! ( After creation of New VM and wanted to install Windows 10 , i was getting Blue screen "Kernel...." ) Asus Crosshair Hero VI + Ryzen 3700x Seems like after each change in UI, it goes back to default host-passthrough' value @limetech Please is not possible to give some selection into UI for this Fix? probably everyone on new releases will be facing it. Thanks
  2. Hello, Today ive tried CrushFTP9 from you. Initial setup went fine, but got popup from CrushFTP Update to 9.3.2 and then it stopped to work... So in App update is not wanted and need to wait for docker update? Thanks
  3. I was in the state where i had VM Module OFF, soon as i enabled it...Server got frozen and needed to reboot. So i coudn't get into any VM config via WebUI. FYI: someone replied that Limetech will fix it in next release. But still Ryzen 3xxx are over 6 months on the market and still having such issue... Everyone complains about Windows, but those HW implementations seems to be much faster there...linux been always delayed, in case you are not a Linux guru who compiles his own kernel
  4. thanks for info ! finally Btw here is some workaround which i find useful in my case
  5. Please fix this issue on all Ryzen 3xxx series - seems like its happening on all chipset X370,X470,X570 My small workaround AMD Starship/Matisse PCIe Dummy Function | Non-Essential Instrumentation (0c:00.0) Jul 5 13:02:30 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 1023ms after FLR; waiting Jul 5 13:02:32 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 2047ms after FLR; waiting Jul 5 13:02:35 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 4095ms after FLR; waiting Jul 5 13:02:40 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 8191ms after FLR; waiting Jul 5 13:02:50 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 16383ms after FLR; waiting Jul 5 13:03:07 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 32767ms after FLR; waiting Jul 5 13:03:42 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 65535ms after FLR; giving up Jul 5 13:03:43 unRAIDTower kernel: clocksource: timekeeping watchdog on CPU10: Marking clocksource 'tsc' as unstable because the skew is too large: Jul 5 13:03:43 unRAIDTower kernel: clocksource: 'hpet' wd_now: b4700ed2 wd_last: b3954a18 mask: ffffffff Jul 5 13:03:43 unRAIDTower kernel: clocksource: 'tsc' cs_now: 1d337ecfa60 cs_last: 1d337dd658c mask: ffffffffffffffff Jul 5 13:03:43 unRAIDTower kernel: tsc: Marking TSC unstable due to clocksource watchdog Jul 5 13:03:43 unRAIDTower kernel: TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Jul 5 13:03:43 unRAIDTower kernel: sched_clock: Marking unstable (510899129422, -8570651)<-(510996221197, -105679272) Jul 5 13:03:45 unRAIDTower kernel: clocksource: Switched to clocksource hpet
  6. After i added 2nd GPU card - needed to do some testing...all was good. Then removed it , kept only one and the same issue started again and FREEEZEs. Read through your notes, some custom patch has to be applied (for version 6.8.3). I was already on 6.9.1b22 so not able to revert 2version back. Anyway not really sure how i was able to run it before without any patch, but i assume this is the way: I wasnt able to start VM module, soon as i wanted it freeze with error bellow. So what to do: 1. in BIOS disable IOMMU 2. Start the Unraid2 3. Start VM module. Make all possible VMs with "AMD Starship/Matisse PCIe Dummy Function | Non-Essential Instrumentation (0c:00.0)" on Disabled AUTO start, then restart unraid 4. Enable IOMMU in BIOS 5. Unraid shold boot , VM module should be visible. Edit the VMs and look for "AMD Starship/Matisse PCIe Dummy Function | Non-Essential Instrumentation (0c:00.0)" added into your VM image - you shold UNTICK IT, then SAVE...next time when you EDIT VM image is not present anymore. 6. Start the VM and all should be running fine I added limetech to my reply , to include patch...as seems like all users with new Ryzen 3xxx series have the same problem. "AMD Starship/Matisse PCIe Dummy Function | Non-Essential Instrumentation (0c:00.0)" source of issues Jul 5 13:02:30 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 1023ms after FLR; waiting Jul 5 13:02:32 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 2047ms after FLR; waiting Jul 5 13:02:35 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 4095ms after FLR; waiting Jul 5 13:02:40 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 8191ms after FLR; waiting Jul 5 13:02:50 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 16383ms after FLR; waiting Jul 5 13:03:07 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 32767ms after FLR; waiting Jul 5 13:03:42 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 65535ms after FLR; giving up Jul 5 13:03:43 unRAIDTower kernel: clocksource: timekeeping watchdog on CPU10: Marking clocksource 'tsc' as unstable because the skew is too large: Jul 5 13:03:43 unRAIDTower kernel: clocksource: 'hpet' wd_now: b4700ed2 wd_last: b3954a18 mask: ffffffff Jul 5 13:03:43 unRAIDTower kernel: clocksource: 'tsc' cs_now: 1d337ecfa60 cs_last: 1d337dd658c mask: ffffffffffffffff Jul 5 13:03:43 unRAIDTower kernel: tsc: Marking TSC unstable due to clocksource watchdog Jul 5 13:03:43 unRAIDTower kernel: TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Jul 5 13:03:43 unRAIDTower kernel: sched_clock: Marking unstable (510899129422, -8570651)<-(510996221197, -105679272) Jul 5 13:03:45 unRAIDTower kernel: clocksource: Switched to clocksource hpet
  7. Also requesting patch if possible @limetech - Could you please apply this fix ? many users with 3xxx Ryzen are having this issue, would really appreciate it to release quick fix for that. Thanks!
  8. Hi Thanks for the reply, i got it working few days ago with help of one user in unraid Discord channel. Problem was that the default "latest" repo wasn't working, soon as i added "beta" all good and is pretty recent also https://hub.docker.com/r/buanet/iobroker/
  9. Hello, I would like to Request for IOBroker docker template, as im not able to get it working :( https://hub.docker.com/r/buanet/iobroker/ https://forums.unraid.net/topic/61663-need-help-with-iobroker/?tab=comments#comment-863899 Thanks!
  10. @Squid Hi Please could add some more hits how to run it? Ive picked https://hub.docker.com/r/iobroker/iobroker/ 2y old Then i added even more Ports: But still not loading the WebUI Tried also https://hub.docker.com/r/buanet/iobroker/ which seems more recent / updated, but the same problem. Thanks
  11. i was playing around with that , but cant definitely tell which step did the fix... "i assume as i moved to 6.9.0 beta 1 it upgraded kernel and fix it somehow."
  12. @J89eu : reading your post - seems like u have similar issues like i did few days ago when i switch from Ryzen 1700 to Ryzen 3700x First i was also suspecting RAM , bios settings etc. I did many things and not sure what really fix it but i assume as i moved to 6.9.0 beta 1 it upgraded kernel and fix it somehow. And ive also tried this : As i was getting the same error, added it into the Start menu...later i removed it. Try also play with (if u have such setting in Bios) SVM - Enable/Disable IOMMU - Enable/Disable how it behaves
  13. upgraded to unraid 6.9.0 beta 1 I was able to boot up with SVM - Enable IOMMU - Enable 1. But VM on OS was disabled, soon as i enabled it and checked log, getting this and then is freeze whole OS and need to manually reboot Apr 23 23:02:22 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 1023ms after FLR; waiting Apr 23 23:02:24 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 2047ms after FLR; waiting Apr 23 23:02:27 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 4095ms after FLR; waiting Apr 23 23:02:32 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 8191ms after FLR; waiting Apr 23 23:02:41 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 16383ms after FLR; waiting Apr 23 23:02:59 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 32767ms after FLR; waiting Apr 23 23:03:34 unRAIDTower kernel: vfio-pci 0000:0c:00.0: not ready 65535ms after FLR; giving up Apr 23 23:03:34 unRAIDTower kernel: clocksource: timekeeping watchdog on CPU1: Marking clocksource 'tsc' as unstable because the skew is too large: Apr 23 23:03:34 unRAIDTower kernel: clocksource: 'hpet' wd_now: a9d6f73e wd_last: a80c745e mask: ffffffff Apr 23 23:03:34 unRAIDTower kernel: clocksource: 'tsc' cs_now: 1c4ec8e5fec cs_last: 1c40186b0f8 mask: ffffffffffffffff Apr 23 23:03:34 unRAIDTower kernel: tsc: Marking TSC unstable due to clocksource watchdog Apr 23 23:03:34 unRAIDTower kernel: TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Apr 23 23:03:34 unRAIDTower kernel: sched_clock: Marking unstable (498609729347, -14912016)<-(498630463494, -35648793) Apr 23 23:03:37 unRAIDTower kernel: clocksource: Switched to clocksource hpet Apr 23 23:04:50 unRAIDTower kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks: 2. Also this seems new in VM machine Setup Any clue what is it for? per MAC address is the same device which is system waiting for When i opened VM setup didn't uncheck it, getting this msg 3. over here i discovered this setting which help unraid to not completely freeze with SVM/IOMMU enabled So like label unRAID OS menu default kernel /bzimage append initrd=/bzroot would become label unRAID OS menu default kernel /bzimage append initrd=/bzroot clocksource=hpet 4. After unticking AMD Starship i was able to run VM and got floaded with this, but Server didnt freeze (luckily) 23:51:04 unRAIDTower kernel: vfio-pci 0000:0b:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 23 23:51:04 unRAIDTower kernel: br0: port 2(vnet0) entered blocking state Apr 23 23:51:04 unRAIDTower kernel: br0: port 2(vnet0) entered disabled state Apr 23 23:51:04 unRAIDTower kernel: device vnet0 entered promiscuous mode Apr 23 23:51:04 unRAIDTower kernel: br0: port 2(vnet0) entered blocking state Apr 23 23:51:04 unRAIDTower kernel: br0: port 2(vnet0) entered forwarding state Apr 23 23:51:05 unRAIDTower kernel: vfio-pci 0000:0b:00.0: vfio_ecap_init: hiding ecap 0x19@0x900 Apr 23 23:51:05 unRAIDTower kernel: vfio-pci 0000:0b:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff 64bit pref] Apr 23 23:51:05 unRAIDTower kernel: vfio-pci 0000:0b:00.0: No more image in the PCI ROM Apr 23 23:51:05 unRAIDTower avahi-daemon[8306]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fef2:6195. Apr 23 23:51:05 unRAIDTower avahi-daemon[8306]: New relevant interface vnet0.IPv6 for mDNS. Apr 23 23:51:05 unRAIDTower avahi-daemon[8306]: Registering new address record for fe80::fc54:ff:XXXX on vnet0.*. Apr 23 23:51:24 unRAIDTower kernel: vfio-pci 0000:0b:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff 64bit pref] Apr 23 23:51:24 unRAIDTower kernel: vfio-pci 0000:0b:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff 64bit pref] Apr 23 23:51:24 unRAIDTower kernel: vfio-pci 0000:0b:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff 64bit pref] Apr 23 23:51:24 unRAIDTower kernel: vfio-pci 0000:0b:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff 64bit pref] Apr 23 23:51:24 unRAIDTower kernel: vfio-pci 0000:0b:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff 64bit pref] Apr 23 23:51:24 unRAIDTower kernel: vfio-pci 0000:0b:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff 64bit pref] Apr 23 23:51:24 unRAIDTower kernel: vfio-pci 0000:0b:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff 64bit pref] Apr 23 23:51:24 unRAIDTower kernel: vfio-pci 0000:0b:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff 64bit pref] Apr 23 23:51:24 unRAIDTower kernel: vfio-pci 0000:0b:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff 64bit pref] Apr 23 23:51:24 unRAIDTower kernel: vfio-pci 0000:0b:00.0: BAR 3: can't reserve [mem 0xf0000000-0xf1ffffff 64bit pref] whole OS become laggy and i need to reboot
  14. Hi guys, I've switched today from Ryzen 1700 to 3700x (on Asus Crosshair VI Hero, latest bios 7704) and soon as i enable SVM , system is freezing after booting or keyboard via USB-C monitor hub is randomly not being detected. I have F4-3200C14D-32GTZ (G.Skill Trident Z 2x16GB DDR4 3200MHz CL14, DIMM, 1.35V) set on 3200Mhz over DOCP, but even if i leave all on default 2133Mhz still the same result Without touching SVM (Virtualization) is all working fine seems like, but without this option Enabled im not able to run VMs via Unraid OS With ryzen 1700, was all fine. EDIT: Just tried 1. SVM - Enable IOMMU - Disable it Works 2. SVM - Disable IOMMU - Enable it works 3. SVM - Enable IOMMU - Enable it doesnt work Any clue what to do? Thanks
  15. mine is working on chrome and Brave