WonkoTheSane

Members
  • Content Count

    33
  • Joined

  • Last visited

Community Reputation

0 Neutral

About WonkoTheSane

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Thanks for your answer. As you can see, the free space and the capacity of the share differ by several terabytes in each case. Just as a test, I invoked the mover and checked again after it completed. I'm seeing exacly the same numbers alternating when refreshing the directory on that share. I've got another share that also uses the cache disk for new files. There the numbers don't alternate.
  2. Hi all, this is probably a minor issue, but I've noticed for quite some time that the free space reported for an SMB share sometimes differs dramatically between refreshs of said share. See attached screenshots of the same share taken before and after a refresh/reload of the current directory on the SMB share. Best regards Matthias
  3. Hi Johnnie, I just tried that, doesn't seem to make a difference. Still 'no exportable user shares', access denied for disk shares. BUT, I compared ownership and access right flags under /mnt/ to my other Unraid server. Turns out, everything except for /mnt/disks was set to 'rw-rw-rw-' whereas on my working Unraid instance, it is 'rwxrwxrwx'. I'm not really sure how this happened, but it looks like everything is okay for now. Thanks & best regards Matthias
  4. Hi all, as of this morning, all of my user shares have disappeared. Rebooting the server did not fix this issue. The only share I'm seeing is 'flash'. The share configuration on the flash drive is present and looks fine. The disk shares seem to be configured correctly but when trying to access them I get an access denied error. I attached my diagnostics to this message. Any help is appreciated. bignas-diagnostics-20200324-0848.zip
  5. Hi Johnnie, diagnostics attached to this post. Thanks! lochnas-diagnostics-20200222-1145.zip
  6. Hi all, I'm facing a problem I'm not sure how to solve. I have two parity drives and have just replaced 2 data drives in my array. Shortly after starting the server to do a data rebuild, one of my parity drives was marked as disabled. What options do I have now? Any help is appreciated.
  7. Hi again, what I don't understand is this. When I go to the unraid main tab, I see the "Please wait, retrieving information ..." message from unassigned devices. This takes forever, in the syslog I see this: These are obviously all timing out, so something is definetly up. When I connect to the unraid server running unassigned devices via ssh and manually mount one of those NFS shares, it works without a problem in these situations. I can list the contents of the share and copy stuff to/from it. So the server is not offline but somehow the
  8. Update: I downgraded both my servers back to v. 6.5.3 and the problem persists. Let me know if you need specific information/logs.
  9. +1 for NFS issues since 6.6.0 See my post here:
  10. Hi all, since the unraid 6.6.0 update I've been having issues with NFS shares mounted by the unassigned devices plugin. I've got 2 unraid servers. Server B mounts a couple of NFS shares on server A and runs a number of rsync scripts on a schedule to push new/modified files to server A. It looks like these NFS mounts become "stale" pretty quickly. Right after a server reboot manually triggering my sync scripts works just fine. A day later, rsync hangs at "sending incremental file list" and I'm unable to "cd" to the NFS mount points. Any clues on how to fix this problem a
  11. Hi all, I had to rollback from latest to 2.3.3-1-01 since sabnzbd was unable to resolve the names of my usenet servers. Did I miss anything about some configuration changes required on my part or is this a known issue?
  12. Hi all, I just updated my sabnzbd container and it does not seem to be working any more. Here is the log, any help is appreciated. 2017-05-24 21:06:20,185 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,185::INFO::[SABnzbd:1275] SSL supported protocols ['TLS v1.2', 'TLS v1.1', 'TLS v1']2017-05-24 21:06:20,189 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,188::INFO::[SABnzbd:1386] Starting web-interface on 0.0.0.0:80902017-05-24 21:06:20,189 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,189::INFO::[_cplogging:219] [24/May/2017:21:06:20] ENGINE Bus STARTING201
  13. *I just realized I posted to the wrong thread. Sorry about that. Hi all, I just updated my sabnzbd container and it does not seem to be working any more. Here is the log, any help is appreciated. 2017-05-24 21:06:20,185 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,185::INFO::[SABnzbd:1275] SSL supported protocols ['TLS v1.2', 'TLS v1.1', 'TLS v1']2017-05-24 21:06:20,189 DEBG 'sabnzbd' stderr output:2017-05-24 21:06:20,188::INFO::[SABnzbd:1386] Starting web-interface on 0.0.0.0:80902017-05-24 21:06:20,189 DEBG 'sabnzbd' stderr output:2017-05-24 21:06