phbigred

Members
  • Posts

    264
  • Joined

  • Last visited

Everything posted by phbigred

  1. Yeah the GSO bug is back in this RC1 for me. Not enough to push me off it but the log is filling up and will need to manually purge periodically until remedied.
  2. You appear to have 16GB of memory in the system assigning 12GB including overhead is why you are at 83% used. Is your jump drive 64GB for unraid? Think that's where your 55GB comes from.
  3. #1 within a minute or 2 of purchase. You drop your key on the drive and boot up. #2 this includes cache, parity, unassigned devices mounting at boot. USB drive for unraid doesn't count. #3 USB 2.0 or 3.0, SanDisk has a good reputation. If you can plug it into a USB 2.0 port on your board. Historically has a better result, but 3.0 is fine. #4 Updates are only manual. You have to initiate them.
  4. Everything should work. Recommend 3 slot pci-e motherboard. Install your nic in the 3rd slot at pci-e 2.0. Don't forget you need to get ddr4 memory.
  5. You could use Krusader docker to move from disk to disk. That's the preferred methodology. Then once you confirm you got off all the emulated data do a new config making sure to note which serial number your parity drive is.
  6. Getting odd logs and a D3 reset error since upgrading to Ryzen 3000. Now throwing code 127's when passing through the Phison controller. Jan 1 16:41:00 unraid-box kernel: vfio-pci 0000:32:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none Jan 1 16:41:00 unraid-box kernel: nvme nvme0: failed to set APST feature (-19) Jan 1 16:41:00 unraid-box kernel: vfio-pci 0000:32:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none Jan 1 16:41:00 unraid-box kernel: vfio-pci 0000:01:00.0: Refused to change power state, currently in D3 Jan 1 16:41:00 unraid-box kernel: nvme nvme0: pci function 0000:01:00.0 Jan 1 16:41:00 unraid-box kernel: nvme 0000:01:00.0: Refused to change power state, currently in D3 Jan 1 16:41:00 unraid-box kernel: nvme nvme0: Removing after probe failure status: -19 Thoughts on a solution? I'd love to get my system back functional with NVMe passthrough, having to use an old image on a sata based SSD currently. unraid-box-diagnostics-20200101-1649.zip
  7. SVM for virtualization is a biggie. If doing passthrough using multi-function in VM Manager for ACS override. Otherwise it's pretty much plug and play.
  8. Take a screenshot as a backup. But the order of disk serial are kept on the USB drive for unraid. 99% of the time if you wire up everything properly and everything is seen properly it will just work. If you are doing anything with IOMMU passthrough with hardware for vms you'll need to do a bit of resetup there otherwise you are set.
  9. See if the system pings even being stuck at that point. Mine booted but was stuck at that screen. I've seen an issue post bios flash for Ryzen 1.0.0.3 Abba. Ended up clearing the CMOS and that corrected it.
  10. Happens to me with Firefox and chrome on mobile. Not the only person with the issue. It's more annoying than anything.
  11. @limetechAny plans on putting in the fixes done by this person's recompile? This custom kernel fixes the VM VFIO bug with no GPU passthrough that @SpaceInvaderOne likely documented. This works for my MSI x370 sli plus with ryzen 3000 compatibility AGESA 1.0.0.3 ABBA code. Also were there any NIC changes with this version 6.8 branch that would affect VM br0 passthrough? Noticing an issue with gateway routing for my VPN traffic. I have to put my entire server outside the VPN as I can't individually route now.
  12. Quick question, were there changes in this build that affected the br0 settings with VMs? I can't isolate out VPN vs no VPN traffic without using the local client now. Used to just add the IPs to an alias list that routed it on the individual br0 IPs. Pfsense gateway routing used to work for unraid now doesn't function unless I remove the unraid server IP from the VPN. For clarification I haven't tested against the Limetech build as I just figured this out yesterday. Might be worth some testing.
  13. This worked beautifully on my msi x370 sli plus that I updated for ryzen 3000. Was pulling my hair out trying different settings to get iommu working until I found this thread. Mucho kudos, now if we could get Limetech to implement these fixes....
  14. Saw something similar with mine. A simple VM restart fixed it and it only happened once.
  15. Most likely a setting in your router needs to be added. Try going to the IP address directly as a workaround. This is the workaround I added to the DNS resolver of my router.
  16. CRC errors may be nothing more than a loose cable. The drive that died might be the same thing. Are you by chance using onboard connections that might be Marvell controllers? New board new connections might be something as simple as that.
  17. Have you attempted turning off docker, going to advanced. Delete docker image file under settings -> docker and rebuild? May need a reboot afterwards to see if that clears it. Then restore your Dockers.
  18. It's for others to go through that have more experience reading diags than I.
  19. Recommend going to tools tab and diagnostics. Upload what you get from it. It'll show more than the log info.
  20. Good point with the crc. I'd say Op go with your best judgement.
  21. Both are going to take time. Turn off anything that could be writing to the array. Pop out the parity and get that swapped. Order another drive to have on standby. Worst case you have a parity drive you can use for recovery should things go belly up. That's the route I would suggest.