Jump to content

highdefinitely

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

3 Neutral

About highdefinitely

  • Rank
    Member

Recent Profile Visitors

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

  1. Updated two servers from 6.8.2 without an issue whatsoever, as almost expected these days. Thanks for the great job unRAID team! I expect more headaches once we move to the new Linux Kernel, but for now, things run smoothly.
  2. Upgraded two servers from 6.7.2 without a problem whatsoever so far. Probably the most pain-free upgrade ever for me.
  3. Upgraded two servers from V6.7.0 to V6.7.1 without a hitch.
  4. Upgraded two servers from V6.6.7, went very smoothly, especially compared to 6.5 -> 6.6 in my case. Really like the new dashboard, looks great! Zero issues so far, been running stable for a few days. I still have the following error message in the syslog, but as it doesn't seem cause problems, I have given up trying to look for a fix: kernel: i40e 0000:b5:00.0: Error I40E_AQ_RC_EINVAL adding RX filters on PF, promiscuous mode forced on
  5. The weird thing is that in the last few days, the server has been running stable, unlike before where it crashed almost every day. For days I've been using the "tail" command on the syslog, but to no avail. One thing I did before though was manually going back to V6.6.3, because the "previous version" available in my unRAID GUI was the broken V6.6.4. So I went back to V6.6.3 and then upgraded to V6.6.5 again and had no problems ever since. Before that, I had used the GUI upgrade feature and updated from V6.6.4. I hope it stays this way and I'm not complaining, but it's weird to say the least.
  6. I am experiencing random freezes / "lockups" with this version as well. Only a hard reset / shutdown helps. unserver-diagnostics-20181119-1120.zip
  7. +1 unRAID is really lacking such an essential feature. I use rsync on a VM that acts as a "man in the middle" between both unRAID servers, but it really would make sense to add a simple and easy to use backup / sync feature to the core system (or as a docker for that matter).
  8. The SSD would be the bottleneck, especially if it's a consumer grade SSD. 128GB RAM isn't a lot for 20 Windows VMs, but depending on what those VMs are supposed to do, it could be enough, e.g. basic things like browsing, office etc. Ideally, you'd have 8GB of RAM per Windows VM, that seems to be the sweet spot for a "general purpose" Windows VM.
  9. Updated both of my machines without a hitch. V6.6.5 seems to work well, going by a few tests in the last two hours. It's important to update your Cache Dirs plugin to the "unofficial one" by Alex R. Berg though, if you use that (who doesn't?). Now I'm just waiting for those pesky Intel network drivers to be fixed for the Linux kernel to be rid of the error messages on boot.
  10. Thanks, the culprit was likely an open unRAID WebGUI.
  11. Updated from V6.6.3, have this new error in my system log:
  12. @Fireball3 Just saw those posts. Updated "manually" to 2.21 and re-enabled auto updates for the plugin again. Thanks again to both of you.
  13. I followed your instructions and it seems to work now. Thank you and a big thanks to Alex R. Berg. I also disabled auto update for the Dynamix Cache Dirs plugin for the time being. While it's working now, it still would be great to have an "official" solution to these problems with cache dirs, as I think it's a very essential part of making the unRAID experience enjoyable. So essential that it probably makes sense to fully integrate it into the unRAID code.
  14. I am experiencing the issue as well, especially since updating to V6.6.3. Please, for the love of everything that is holy, can somebody be so kind and fix this plugin? Because, and I'm not exaggerating when I'm saying this, unRAID is close to being unusable without it working properly, especially if you have two dozen disks in your system(s)....
  15. Unfortunately, this update has still not fixed the issue I have with my onboard Intel 10gbps NICs (Supermicro X11SPH-nCTF). The boot syslog shows this error, just like V6.61: Oct 14 18:57:58 unSERVER kernel: i40e 0000:67:00.0: Error I40E_AQ_RC_EINVAL adding RX filters on PF, promiscuous mode forced on Oct 14 18:57:59 unSERVER kernel: i40e 0000:67:00.1: Error I40E_AQ_RC_EINVAL adding RX filters on PF, promiscuous mode forced on I did some research online and it seems like this supposedly should have been fixed with new network drivers from Intel: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892105 But not in my case, unfortunately.