Alintya

Members
  • Posts

    12
  • Joined

  • Last visited

Alintya's Achievements

Noob

Noob (1/14)

0

Reputation

  1. This plugins behavior should be the default imo Otherwise, non required paths are pointless (and i personally like them as I don't need to lookup the path again if i decide to use it in the future, not to mention the potentially missing comment/instruction)
  2. Had this happen to me as well for the past year every 2 weeks or so and almost guaranteed whenever I go home with the unraid browser tab still active.
  3. Still happening with updated bios, 6.12.4 and nothing configured but 1 array disk and nvme bind. Any clues on this? Very annoying as my license goes to waste
  4. After anywhere from 30mins to 7+days, Unraid becomes almost completely unresponsive until hard shutdown. This started happening with some 6.12.x version iirc. after almost 2 years of flawless operation. What still works when "unresponsive" responds to pings responds to bare-metal keyboard input but logging in times out wireguard vpn What I have tried so far disable C-states slightly decrease vm.dirty_background_ratio and vm.dirty_ratio disable expo profile running in a minimal working scenario with only 5 dockers and no vms play with quite a few more settings (1 at a time), which i should have all reverted due to not helping System hardware MSI B550M Pro-VDH Ryzen 5600g 64GB RAM Samsung 980 Pro 1TB Samsung 870 QVO 4TB Software setup Unraid v6.12.4 Plugins: CA, Active Streams, System Temp, Fix Common Problems, FolderView, Tips and Tweaks, UD, UD+, Unraid Connect, User Scripts 1TB cache 4TB array 2 auto-start ubuntu VMs, 1 auto-start windows VM several docker containers including typical services like nextcloud behind swag Syslog server recording The attached syslog was recorded during following sequence; Normal operation for 7 days (cut from log except for last 2 entries) 15:01 unresponsive 15:05 hard shutdown 15:43 temporary unresponsiveness (just ~2mins, first time ever noticed by us in this fashion) 15:56 unresponsive syslog_oct_2.txt server-diagnostics-20231002-1714.zip
  5. There are quite a few seemingly related threads/issues, is it time for some sort of collection thread? Also, it appears to be 6.12.x specific. (I personally had no issues whatsoever for over a year with the same setup having these random lockups on 6.12) Unraid 6.12.3 crashing, docker service is unavailable UNRAID IS UNRESPONSIVE AFTER A DAY OR SO LOSE CONNECTION TO WEBUI, SSH, DOCKER. SMB STILL WORKING SERVER GOES UNRESPONSIVE DAILY, BUT STILL RESPONDS TO PINGS 6.12.4 SYSTEM HARD LOCKS OFTEN UNRAID RANDOMLY CRASHES FOR SOME REASON?
  6. I am experiencing similar issues with a Ryzen 5600G machine but for longer than 6.12.4. I didn't have any troubles updating tho. The system will become almost completely unresponsive except for wireguard, which seems to be unaffected. My logs aren't really helpful either Frequency of this happening is around once a week for me as well.
  7. I just gave it another shot with 6.12 stable and a brand-new windows install but issues remain; the vm booted up and crashed the unraid host after ~3min
  8. Yea I meant to say that that has been fixed by reinstalling but the vm issues remain.
  9. I just tried to start over completely; new unraid install with 6.11.5, cleared all (unraid)disks, setup unraid with 1 array disk, 1 cache and nothing changed regarding the VM. Array autostart wouldn't work before as it always claimed my system setup had changed.
  10. I am trying to dual boot my bare-metal win11 install as VM without luck. I've been following spaceinvaders tutorial, except binding the controller via the new checkboxes in System Devices. Whenever I try to start the vm, 95% of the time it just freezes on boot with the TianoCore splash still showing or the remaining 5%, I manage to get into windows, with the unraid host crashing shortly after (<5m). Running the VM without gpu passthrough (VNC) does work. I think I have tried every possible combination of stubbing devices (including the gpu), removing them after setup, using dumped vbios, etc. An interesting behavior is that after force killing the vm and restarting, the windows automatic repair launches just fine but choosing restart will lead to another freeze on boot. Right now, I have more devices stubbed and attached to the VM (usb controller, sata, ...) but the minimal setup with just the nvme controller and gpu exposes the same problems. Other things I have tried: - force all pcie slots to gen3 (including m.2) - disable r-bar - enable sr-iov - force enable iommu (instead of auto) - set pcie ACS override to both - update bios - another vm with the nvme in the second slot passed through (older win11 install) same behavior IOMMU groups XML: System specs: tower-diagnostics-20230522-2336.zip
  11. So it took me the whole night but I finally managed to set up a dual-bootable gaming vm. The (seemingly) only problem remaining is that I'm experiencing very low volume in the vm, having passed through my mainboards audio controller. Very low means audio in windows 100% + yt 100% is barely usable. I'm pretty lost on how I could troubleshoot this so any help would be greatly appreciated. System: MSI B450 gpc AMD Ryzen 3600 RTX 3060 Ti M.2 Nvme with bare metal windows on it Stubbed devices