Jump to content

jonp

Administrators
  • Content Count

    6045
  • Joined

  • Last visited

  • Days Won

    17

jonp last won the day on July 15 2019

jonp had the most liked content!

Community Reputation

326 Very Good

About jonp

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • URL
    http://lime-technology.com
  • Location
    Chicago, IL

Recent Profile Visitors

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

  1. You're overcomplicating this. Just download the ISO from your Windows VM. Double-click the ISO and it will mount it as a drive letter. Right-click on the VirtIO Ethernet controller in device manager, update drivers, then browse to the drive letter of the ISO and let it search.
  2. I don't doubt the results your getting, but we can't recreate the issue here on our equipment and I would imagine we'd be hearing about this issue from a lot more folks if it was a software bug. Another thing you can try is updating the virtio drivers. We haven't updated the list that propagates inside of Unraid yet, but the latest VirtIO driver release is here: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.173-4/virtio-win-0.1.173.iso Try updating the virtual network driver in the VM using this ISO and see if that improves things. If not, I can give you a few other things to try and narrow this down.
  3. That is going to make the issue very difficult to diagnose. Network traffic to the server is network traffic to the server, regardless if that's over a WAN or LAN. Internet speed is limited by your router/ISP, not Unraid OS. Perhaps something configured on your router, firewall, or switch may be doing this? Any QoS policies in place? How sophisticated is your network? Are you using a rented router/modem or do you provide your own? What about using other speedtest sites for testing?
  4. Let us know if you are 100% stable on 6.7.2.
  5. Ok, how about general network performance? How is it copying a file from a machine on the network to the Unraid server?
  6. The biggest challenge here is trying to figure this out without a copy of your system diagnostics. Can you upload those here from your current flash that is having problems? My guess is there is something in that configuration causing this modprobe issue. To confirm its not anything specific to the flash device itself, you can make a full backup of your flash, then wipe the flash fresh, reinstall Unraid, and boot. If no modprobe issue, then you can most likely rule out the flash device itself as the culprit and restore the backup. Now it comes down to figuring out what on your flash is causing this problem. Please share your system diagnostics so we can see (from the Tools > Diagnostics page).
  7. The syslog to flash method is not valid for capturing log events related to major crashes like you're experiencing. The problem is that the hang can occur before the write to the flash can occur. This is why I am suggesting you connect a monitor / keyboard to the system.
  8. Hi there, Looks like you need to update your forum signature as your hardware has changed from AMD to Intel ;-). That said, I'm not seeing any events in the logs themselves that show a problem. And I'm not sure what this is supposed to mean: Also hoping that you removed this container while troubleshooting this: At this point, I would suggest hooking up a monitor and keyboard to the system and tailing the log (command is tail /var/log/syslog -f). This will begin printing the log out to the screen. Then try to get the system to crash again and capture whatever was printed to the screen (use your phone to take a picture if necessary). This should give us at least some information to point towards a cause. I'd also check for a BIOS update on your motherboard.
  9. That would give us more information...
  10. Hi there, Saw your email into support as well and reviewed your logs. Nothing is glaring at me that is looking out of place. Unfortunately these types of issues can be notoriously difficult to diagnose as they are often hardware-specific. Have you tried reseating the GPU into a different PCI slot? What about a BIOS update? That CPU is awfully old at this point (7+ years). Sometimes these pass through issues come down to just needing a good old fashioned face-lift on the hardware.
  11. Just an FYI guys, I think we have this sorted thanks to @limetech! We were able to recreate the issue and in an internal build today, we think we may have it squashed. Stay tuned...
  12. Thanks for the update! Not sure what would have fixed this from 6.8.1, but either way, glad it's resolved for now!
  13. You definitely need to be stubbing any storage, Ethernet, or USB controllers you wish to use in your VM. Otherwise the host OS will load a proper driver and potentially block you from starting the VM. If with all of those devices stubbed, you're still having a problem, I'm running out of ideas. After starting your VM with the devices assigned, go ahead and recapture diagnostics and upload here. We need to see something in the logs to point to the source of the issue. If nothing is there, it's likely a hardware-specific issue which will be very difficult to remediate.
  14. A few things to try: 1) UEFI boot mode. Use OVMF instead of SeaBIOS. See if that makes a difference. 2) Try i440fx (instead of q35). 3) Try setting the CPU to emulated instead of host-passthrough. If none of those work, let us know and I can try to recreate the issue on our end.
  15. I've gone ahead and copied this into our bug reports forum for stable releases. I've listed it under the category of "annoyance" as it doesn't seem to affect functionality, but obviously isn't reporting the correct data. Further commenting on this should be done over there: