eybox

Members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About eybox

  • Rank
    Newbie
  • Birthday 09/23/1986

Converted

  • Gender
    Male
  • URL
    https://www.linkedin.com/in/eyordanov/
  • Location
    Sofia, Bulgaria

Recent Profile Visitors

629 profile views
  1. You actually might have pointed me in the right direction here. After disabling mover logging (as suggested), and then rebooting the server, all these warnings stopped popping up. At least for the time being. I'll still monitor closely in the next 24 hours or so to see how it goes. But anyways, I'll be closing this topic as solved now. Thanks again!
  2. Hi, ti-ti jorge. And thank you for your reply. But as I've typed into the closing statements of the original post itself - sadly a reboot doesn't fix this issue. It still persists. As for the rotating syslogs, my server is running 24/7/365. I reboot it just 2-3 times per year (usually around Unraid upgrades), I don't know if this has anything to do with it or not. Kind regards, E
  3. Hello, Unraid community. There's been an issue which was bugging me for a while, but having a couple of babies at home, didn't have enough time on my hands to go after it. But as with anybody having an OCD, enough is enough - babies or not, I'm tackling this. With your help of course, as I wouldn't be able to do it myself alone The issue is as follows: There is constant polling (callbacks) for a couple of devices (sdp & sds) that are not connected and/or part of the server build (and have never been), yet the system is constantly trying to access them read/wr
  4. Hi, guys. Thanks to you @bonienl , @eschultz and @limetech for helping out. It finally seems to be working now. Upgraded and so far the initial couple of hours of testing are OK.
  5. Thank you for this lead! I do have 4 NICs. And I use only one of them - eth0, with br0 attached to everything - Dockers and VMs. I tested eth1 a lot of time ago if it worked or not, but never used br1. What is the resolution to this? Removing everything eth1 and br1 related from network.cfg perhaps?
  6. Here's everything we agreed upon on both 6.6.6 and 6.7.0. Hope this helps. Keeping fingers crossed, as I love Unraid and the latest UI change REGULAR-6.7.0-cortex-diagnostics-20190511-2334.zip SAFEMODE-6.7.0-cortex-diagnostics-20190511-2339.zip REGULAR-6.6.6-cortex-diagnostics-20190512-0203.zip SAFEMODE-6.6.6-cortex-diagnostics-20190512-0211.zip
  7. Alas I already reverted back to 6.6.6 as I described in the original post. But this offers us an unique opportunity. Would you like me to do both of these: 1. Boot into SafeMode on 6.6.6, and get diagnostics zip 2. Upgrade again to 6.7.0. Then boot into SafeMode and get its diagnostics zip. This way you would be able to compare them both for differences?
  8. First of all, please allow me to show my gratitude for the amazing work you and the people at limetech have done for all of us. As well as for you helping me right now. Cheers 🍺 Back to your question: - The router still didn't see the server as an active device on the network - Still couldn't ping the outside world from Tower. I do believe it's an in-OS change which triggered the network-related issues, at least that's what I deduced based on my troubleshooting. But I'm just not advanced enough to tackle these on my own 😢
  9. In all the "Fail" cases, I meant that it kept on working improperly as described in the points above. Not that the OS failed to start. Sorry, my bad
  10. Hi, team. I upgraded from 6.6.6 (stable) to 6.7.0 (stable). And it broke both the server and my heart. I guess this release starts off on the wrong foot for a lot of people. In Summary: - I'm having massive network-related and some PCI-related issues. - I need help. Diagnostics attached. Thank you in advance! In Full Detail: Been an extremely happy Unraid user for quite a while now. Never had any OS issues before, other than the occasional hiccups which I caused with my limited understanding of Linux. But nothing which a friendly chat here in the forums o
  11. Bumping up this thread, as I'm in the same boat as OP. Anyone knowledgeable enough to help, please?
  12. Upgraded from 6.6.3 -> 6.6.5. So far it appears to have no issues. Will monitor and let you know if this changes. Cheers!
  13. Upgraded from 6.6.2 and drank beer while doing it. No hiccups thus far.
  14. yeah, I was asking myself the same thing a while back.... I would love to contribute to this btw, updated my server yesterday from 6.6. Everything is functioning as it was before (server, dockers, VMs, etc). Thanks!
  15. I was in the same boat this morning, as you are. The original plugin has been created a while back, and hasn't been updated for a while. There is an updated version of the plugin, by a different developer. All you need to do now is to just uninstall it (your old version) from Plugins page. And then simply go to Apps and search for "hotplug". A plugin by the developer "dlandon" should come up. Just install that one, and you should be good to go! Hope this helps