Jump to content

mattz

Members
  • Content Count

    21
  • Joined

  • Last visited

  • Days Won

    1

mattz last won the day on March 29

mattz had the most liked content!

Community Reputation

6 Neutral

About mattz

  • Rank
    Member

Recent Profile Visitors

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

  1. This may be a bit late, but wanted to contribute. Would help recommendation if I knew more about the use case. Multimedia, but are you just hosting files or doing transcoding? And a single Windows VM- will it be the daily diver? * CPU cores, plan for more so go with the 8 cores if you can. Once you start using Docker and some VMs, you will be glad to have extra cores to dedicate to tasks * Cache drive- go for more space if you plan to use some VM's (especially for gaming and caching media) Everything else looks good.
  2. Welcome, @LumberJackGeek! I would say @jonathanm's recommendation is probably the way to go: Install UnRaid and test on another rig. It wouldn't have to be your production server, but maybe something low-powered with the new drives and then switch over. And I wanted clarification on this... Do you really have only 15 GigaBytes of data?? You can save that to a $10 flash drive or upload to some cloud storage while you try out UnRaid on your hardware.
  3. @swixter - Try the *unsupported* BIOS Downgrade utility that @Borbosch posted earlier in this thread. It should allow you to downgrade to an earlier mobo BIOS version. Right now, that's the only fix anyone has found for this problem.
  4. I did try 6.7-rc5 with the latest BIOS when I was was originally having the issue and no luck- same error. They were both using Linux Kernel 4.19. I am holding out hope that the NEXT UnRaid version will include Linux Kernel 5 and because kernel 5.2 (I think) will have Zen 2 support, we will see a fix for our problems with this stuff. This is a good idea @John_M! I will find all the model numbers listed in this thread and make an edit to the OP to include them there. I am curious on what is the root cause. At one point I contemplated buying a new high-end x470 mobo, but then I saw posts from other folks here with the same issues on other manufacturers.
  5. What a way to discover a work-around, right?? I bet there are _a lot_ of folks going through the same issue. Wonder if there are any other keywords we can use for this thread? I imagine one day there will be some sort of update to correct this, but I am not sure if it'll be a motherboard BIOS or Linux Kernel, or ...
  6. @shuruga2 - Sorry about the delayed response. The only success I had with this was to downgrade the BIOS back to an earlier edition, and that works like a charm. You should be able to do this with some *unsupported* software. Check the post I started here--other folks have helped me with my MSI bios downgrade, but I think someone mentioned Asus (which is your Prime x370, right?):
  7. @Borbosch Glad we can commiserate with you on this one. I find it worrisome and hopeful that your Asus motherboard also had this error. At one point I was hoping it was just an MSI issue, but is sounds much larger. I hope that a future Linux Kernel update (maybe??) is able to address this issue. Otherwise, all these manufacturers are going to have to come out with "fix" BIOS updates again. And being stuck on an old BIOS version is not a long term solution for this issue, but it does work right now...
  8. I did not, but it did it for me. Everything was cleared, including any OC Profile you may have had saved. So you'll have to modify back all your settings. Using custom settings on the Smart Fan curve is a real pain. 😐
  9. @tw0884 - that Flash Tool worked like a charm with the older (v14) BIOS! I recommend you do the mobo BIOS downgrade. Updating to rc5 didn't help me at all with my problem. Maybe the Linux Kernel bump they brought in on rc6 will help, but I wouldn't bet on it... Maybe for a bigger upgrade I would try again. I have successfully booted into my Windows 10 VM with the GPU pass-through! I am ecstatic. Sucks that the only solution is to use an unofficial flash tool to downgrade the BIOS to get this working... but good enough for me!
  10. @tw0884 - Sorry to hear you are also having problems. But it also makes me feel good I'm not just crazy and someone else sees it. I'll bet there are a lot more ppl noticing the problem as the update. Awesome find on that downgrade tool! I am going to give that a try... hope I don't brick my mobo but so hungry for a fix for the VM. FAILED - I bought a $40 video card and tried using it to no avail: 1) The mobo has no way to specify that card as the primary unless I move it to the top physical slot and 2) when I have a second card, the PCI-E goes from 16x lanes down to 8x lanes. I am not sure how big of an impact that may have, but I am not a fan of losing half the lanes. FAILED - I also tried using the Flashback+ built into the BIOS with no luck. I put in the flash drive with a "MSI.ROM" for the v14 BIOS, the computer powers on for 1 second, powers off, then the Flashback+ LED flashes 3 times and stays on. I guess that indicates an error with the flash process. I hit the power button and the computer boots up with the current BIOS v18. I have read that it is very particular about USB sticks, so I could go out an buy a few other brands but... Blah. I am going to load Windows 10 natively on an old SSD I have to see if everything boots OK. And then try out the MSI downgrade BIOS tool (thank you tw0884!). And then, the more desperate move, I will look to buy a new motherboard, different brand. MSI said I could start the RMA process, but if I have to disconnect everything and be out a motherboard for a week (or 2??), I am going to bail on MSI--the same problem will happen anyway once the BIOS is updated. I do worry, though, that it's not exclusively an MSI problem but linked to how Ryzen 2 talks to the sysytem... That means that the Linux Kernel(??) would have to get changed (maybe it's fixed in v5?) or... something else? But I don't want to sit idly by for it. However, since it was only the latest BIOS update where I had this problem, hoping other brands completely avoided causing this issue.
  11. This is just a rant... But going through some mobo BIOS issues (in my other forum thread posts). Does it surprise anyone that MSI takes the stance they "do not support other OSes except Windows"? Maybe all (most??) motherboard manufacturers take the same stance from a support standpoint. I do still like the hardware...
  12. Not to dredge up ancient history, but I am now having the "stuck in D3" issue after an upgrade of my BIOS from v14 to v18 on the MSI X470 Gaming M7 motherboard with a Ryzen 2 2700x CPU. Using an Nvidia EVGA 1070 card. This just happened last weekend (Mar 2019). The BIOS update seemed innocuous enough, but it did quite a number to my VM setup... In fact, I cannot pass through my GPU or sound card without errors. Sounds like all the TR folks went with a BIOS update in late 2017 and got everything working. Why this cropped up for me now is beyond me! I am going to buy a super cheap secondary GPU to try to run for Unraid so I can get my main GPU on a VM again... Any other options you can see for me?
  13. You know, I really don't get it. It seems like this is a Threadripper / Ryzen 2 issue from over a year ago. Some pretty ingenious folks on reddit posted a fix for it. However, the final fix was a BIOS update to x399 mobos. My CPU is a Ryzen 2 2700x... And it only broke with this error message on the _LATEST_ BIOS update. I have emailed MSI's tech support, but I am not getting much help from them... They still think I need to reinstall Windows to make it work. 😕
  14. Upgraded Unraid OS to 6.7.0-rc5. No good, still have that "Stuck in D3" error. Was holding out hope the Linux Kernel update to 4.19 would help, but that's a no-go... Not sure where to go now.
  15. Ok, so... I can't revert my BIOS, the MSI M-Flash does not allow to go to an older version. So at this point I am stuck unable to load my GPU into any VM, even Ubuntu. Searching for anything around a D3 power state with Nvidia has turned up very little. I did see a few references to a Linux Kernel (even the few posts that show D3 on this forum), and it pointed to Linux Kernel 4.19 (as of Unraid 6.6.7 it is still 4.18). I did notice that a Kernel update to 4.19 is coming in the 6.7.0 release--not to mention qemu to v.3.1 which @david7279 originally mentioned, so maybe I hold my breath until then! Should I get into the Next branch or wait until Stable? Would it do any good for me to get into the conversation about this next version or is my problem such an edge case I should wait for Stable? Cheers,