• Content Count

  • Joined

  • Last visited

  • Days Won


meep last won the day on December 30 2019

meep had the most liked content!

Community Reputation

52 Good

About meep

  • Rank
  • Birthday April 29


  • Gender
  • URL
  • Location

Recent Profile Visitors

3263 profile views
  1. On, until 31st March
  2. Perhaps you can disable docker? This would allow you to either adjust your unRaid network settings so they don't conflict, or delete the docker image (and force a reinstall) which will give you a window to reconfigure or remove Shinobi. There's a thread here that has info on how someone else did this (for a different reason;
  3. Have you taken the time to edit your vm xml to ensure both the video and audio nodes of your gpu are set to the same virtual bus and slot? UnRAID borks this and can cause to problems like you are experiencing. have a look at the link in my sig for details on this and other things to try.
  4. The behaviour sounds like a situation where the GPUs have been reserved. In this scenario, the boot sequence shows up to a point, but appears to stall. Have you a clean unraid install, or have you ever set any VFIO reservations for passthrough? (if you have, and the n shifted or added devices, the assignments can change and th wrong devices can become reserved).
  5. That should be fine. I believe the recommendations are to give unRaid at least core 0, and alway include core 0 as there is some benefit in that (i'm not sure what). Remember, the above guidance is specifically around isolating cores for high performance VMs such as gaming. If you have a few dokers that are not computationally intensive, you can pin non-isolated cores to them, leaving a bit of headroom for unRaid to take as needed. Also, you don't need to isolate ALL the cores assigned to a VM. You can, say, assign 4x threads to a VM, but only isolate 2 of them. The VM
  6. @brainbudt , @sbo365web If you switch on the help in the GUI on the isolation page, you will find this; So, when you pin a core to a VM or Docker, that core is allocated to the VM/Docker, but the unRAID OS may still access it and use it for various tasks. When you isolate a core, it is no longer accessible even by unRaid for routine tasks and should therefore be 100% dedicated to wherever it's pinned. You can pin cores without requiring a system restart. You must restart your unRaid server to effect any isolation changes.
  7. As the multi-lingual aspects get more popular, the activity feed is filling up with incomprehensible posts. Is there a way to add a filter to remove certain forums / languages from the feed?
  8. So as someone who's just finishing up a trial, it looks like I missed all the pain. For me, it was a very straightforward initial setup ad the update was smoothness itself. The 1.8 UI, on first impressions, looks like a vast improvement on what went before which was somewhat clunky and tricky to navigate (on desktop). Now, my only decision is Qobuz or Tidal. (I'm leaning towards the former).
  9. That’s progress. Section 8 in my blog post suggests a solution for -43 that’s worked well for me.
  10. Check the link in my sig to see if there are any tips there that you might have missed. one trick that works well for me is to install virt manager docker, and use that to add a VNC graphics device alongside your gpu passthrough. In the vm xml , double check to ensure that the vnc adapter is first (before the gpu). then, when you boot the vm, you can observe the boot process via VNc to see what’s foing on. ive had instances in the past where the vm was stalling or jumping into seabios, of where windows was loading into recovery or waiting at the login screen
  11. I still haven't found the time to shuck and, more to the point, disassemble the server to drop in the drives. I'm waiting on another part to arrive (caught up in Christmas/Brexit shipping fiasco) so once that's here, I'll do so and report back. The pre-celaring was not so much to preclear as to run the drives at some degree of intensity while still in their cases to see if there would be any issues that would merit a warranty return. (none showed up). Also, these will be parity, and I can't recall if parity disks actually need a pre-clear Anyway, will report back once I
  12. Hi I cannot help with the specific issue, but I have a few pointers that might be of general assistance.... First, try to ascertain if it's the bonding, the dockers or a combination of both that's causing your problem. Run with one and not the other for a while, then swap. This will help a lot with narrowing down where the issue is. Second to help with retrieving logs on reboot......; Saving log files is not on by default. Go to Settings -> Syslog Server and switch the 'mirror syslog to flash' setting to 'Yes' You'll then be able to see the
  13. 3 days to preclear in their cases. I'll be shucking in the next few days
  14. Well, they are presently preclearing. I've kept them in their cases and connected via USB 3.0 but it's a slow process. Averaging 160MB/s and getting slower as the pre-read reaches the edge; If they keep going at this pace, and no problems arise, I'll have them ready for shucking by the new year!