Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About moose

  • Rank
    Advanced Member


  • Gender
  • Location

Recent Profile Visitors

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

  1. Would you mind providing a link to that bug report? Honestly I tried to find it on my own but could not...
  2. Is anyone running v5.10 or is the general recommendation to go to v5.9 max? I'm running v5.9.29 and haven't had any issues so far...
  3. @JonMikeIV I also upgraded from 6.6.7 to 6.7.0 but had no hanging issue. I'm not sure if this makes a difference but I always do this before starting the unRAID OS upgrade and have never had it hang: Stop VMs and Dockers Stop Array, confirming it stops sucessfully Then upgrade OS Then reboot I know this doesn't really help your current situation but just wondered if it might explain the hanging.
  4. Updated from 6.6.7, no issues. Thank you for the excellent work!
  5. Auggie, I have had similar issues you describe. It seemed disk access was freezing at various random times, sometimes perhaps at intervals although I didn't time them to see if there was a pattern. It would happen watching movies (freeze for 20-60 seconds or so), playing audio, reading/writing files to the array. I wasn't sure exactly when this started to happen but know its been happening for a year or more. Sometime in the past this didn't occur but I don't know that exact time frame or what unRAID release I was on at the time. I do have a computer adjacent to my unRAID server and when using that computer, noticed that when the problem occurred, I could see all the drives being accessed, one drive at a time (LED illuminating for each drive on my supermicro 5-in-3 cages). Once that random drive access stopped the problem would go away and the array would be responsive again. I've searched this forum many times with various keywords and not been able to find anything, until I searched "scanning disks freeze" and this thread was at the top of the results. I also had the Dynamix Cache Dirs pluging installed but wasn't using it. I bet you are correct and this is the root cause. I've uninstalled it and will monitor for the freezes and report back if it occurs or if it doesn't occur. Thank you for posting this.
  6. I found and fixed the unRAID SMBv1 access issue via this article: https://www.techcrumble.net/2018/03/you-cant-access-this-shared-folder-because-your-organizations-security-policies-block-unauthenticated-guest-access/ I had followed BobPhoenix's enable "SMB 1.0/CIFS File Sharing Support", also updated my hosts file per your earlier suggestion, the step in the linked article was the last step I needed. It's a Win 10 "rookie mistake" by me. (I'm new to Win 10.) Thanks for your help Frank and LT team!
  7. Thanks Frank. The hosts modification doesn't work, I already tried your other suggestions to no avail. I'll keep investigating, researching and trying other methods. I think MS changed something with Win 10 version 1809 which might prevent earlier workarounds. If/when I find a solution, I'll report back to this thread.
  8. I have a new win 10 2019 LTSC 1809 install on a laptop. I've enabled SMBv1 per BobPhoenix above, browsed his links and completed other searches for solutions via google. Nothing is working, I cannot browse my unRAID server from my new win 10 laptop. This SMB1.0 quirk between Linux and newer versions of win 10 seems unsolvable for me. Too bad we can't use SMBv2 or SMBv3 in unRAID, seems odd this isn't resolved/updated in Linux... There has to be other unRAID users with w10 1809 that have a workaround. Does anyone have any other ideas to try to resolve?
  9. Merry Christmas and Happy New Year to everyone!! :) Thank you to the Lime Tech team and community for all you do. Enjoy your time with family and friends!
  10. Upgraded from 6.5.3 to 6.6.0 with no issues. New GUI looks great! Thank you for all the hard work!! :)
  11. Hi spants, I have a question with respect to the comment/detail from yippy3000, does this mean that after some time of running the docker (as it now exists) that the docker (pihole dns server) becomes unusable/unresponsive? I ask because I installed the pihole docker and it seemed to work great for about a day or so then all LAN devices were unable to DNS resolve. My remedy was to remove pihole. I really like the function/benefit/concept of pihole and would like to reinstall/have it work as a docker. In other words is there any issue with this docker or are people successfully using it for a ~ indefinite period? (guessing the docker is fine and it was perhaps some config tweak/change I made in that first day or so)
  12. Upgraded from 6.5.2 to 6.5.3-rc2. No issues!
  13. Thanks trurl! Update: After removing and reinstalling, I was delighted to see that all my previous custom plex settings were maintained. All I had to do was uninstall the existing plex docker (also selected the remove image option), then install a new plex docker from the Apps tab and remap my previous share and transcode paths. All previous user detail and custom settings were maintained with the new plex install, awesome! Easy fix!