Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About zAdok

  • Rank
    Advanced Member


  • Gender
  1. No dramas mate. Just happy to be able to test this app. Already dropped 2% of array utilisation
  2. I also see 1 Core maxed out when idle. It jumps from core to core also. As soon as I stop the docker that behaviour stops. @Josh.5 can i get some logs for you on this? Just let me know what log files you need.
  3. You rock @Josh.5 So far so good, getting past the 40MB point which I wasn't before.
  4. Just checked mine and it's the same. Gets 12% in and stops encoding.
  5. Working well for me, thanks @Josh.5. Looking forward to seeing some new features. Thanks again for your work on this.
  6. My first re-encode has just completed and wow. Quality is fantastic and the audio is nice too (previous build the audio was very choppy). File size has gone from about 3GB to 480MB.
  7. OK so far I've found a few bugs. 1 - When the docker was pinned to core 2,3 (i have only 4 cores) it used 100% of core 3 but wasn't actually scanning anything. Upon switching it to use all cores 0-3 it scanned the library OK and started building the queue. 2 - When you set the scheduler to 0 (to disable the schedule) the option to scan on startup does nothing. 3 - A few times when I've stopped the container and started it again, the number of workers have gone back to 3 (i've set it to 1) and the library scan went back to 60 (I had it at 180). This hasn't occurred when restarting it, only stop/start. 4 - It can't parse apostrophe characters when scanning the library, results in ' being added instead. Not sure if the file outputs this way though.
  8. Great work Josh. The previous build didn't work to well for me but I'm going to try this one out now. Thanks for your work on this.
  9. Cache2 hit 71, Cache1 was at 63 i think.
  10. So this morning I changed the SSDs onto the onboard controller as advised. After a few hours of running I started getting temp alarms from the SSDs again. I stopped the array and the temps immediately dropped 20 degrees celsius. Any ideas's why this is happening? zadok-nas-diagnostics-20170425-1055.zip
  11. OK cheers. Thanks for the helpful feedback.
  12. OK so this just happened again, this time I was able to run diagnostics. Gui reported that one cache disk was missing and that the remaining cache disk was running hot. The one that was missing was NOT the one with the reported errors last time. btrfs device stats /mnt/cache reports no errors at all since I last cleared them a few days back. Docker didn't corrupt this time. zadok-nas-diagnostics-20170424-2019.zip
  13. Thanks, heaps of write, read and flush IO errors on one of the SSDs. I'll replace that cable and keep an eye on it.
  14. Yeah thats what I was thinking. I've done this a few times in the past, replaced the SSDs as I thought they might have been causing it. Any ideas to what else could be causing this to happen?