sivart

Members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

2 Neutral

About sivart

  • Rank
    Newbie

Recent Profile Visitors

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

  1. @limetech I apologize. I think it was the telegraf docker image. Even though it was reporting not running, I think it was continuously trying to restart an issuing SMART commands. Disabling telgraf allowed the drives to spin down.
  2. Correct, but the logs I posted after that were in safe mode. When I get home, I will post the diags in safe mode.
  3. I don't think so. I booted into safe mode and had the same issue.
  4. No joy. I forced the drives to spin down and they came back up almost immediately. Dec 10 20:52:40 ion root: unRAID Safe Mode (unraidsafemode) has been set <snip> Dec 10 20:53:40 ion emhttpd: spinning down /dev/sdf Dec 10 20:53:41 ion emhttpd: spinning down /dev/sdj Dec 10 20:53:42 ion emhttpd: spinning down /dev/sdk Dec 10 20:53:42 ion emhttpd: spinning down /dev/sdl Dec 10 20:53:43 ion emhttpd: spinning down /dev/sdd Dec 10 20:53:43 ion emhttpd: spinning down /dev/sdm Dec 10 20:53:44 ion emhttpd: read SMART /dev/sdj Dec 10 20:53:50 ion emhttpd: read SMART /dev/sdm Dec 10
  5. I uninstalled disklocation and tried to put all my disks to sleep, and it immediately read smart status... Dec 10 20:41:45 ion emhttpd: spinning down /dev/sdg Dec 10 20:41:46 ion emhttpd: spinning down /dev/sdi Dec 10 20:41:46 ion emhttpd: spinning down /dev/sde Dec 10 20:41:47 ion emhttpd: spinning down /dev/sdf Dec 10 20:41:47 ion emhttpd: spinning down /dev/sdj Dec 10 20:41:48 ion emhttpd: spinning down /dev/sdk Dec 10 20:41:48 ion emhttpd: spinning down /dev/sdl Dec 10 20:41:49 ion emhttpd: spinning down /dev/sdd Dec 10 20:41:49 ion emhttpd: spinning down /dev/sdm Dec 10 20:41:5
  6. See attached. Thanks ion-diagnostics-20201210-2015.zip
  7. Interesting, I did not see this with beta35. My drives don't stay asleep with RC1. SMART queries shouldn't wake up the device.
  8. My drives (SATA) are not spinning down. When I manually spin down a drive, it spins up right away. I can see in the log that it does in fact try to spin down the drive. This was working on beta35.
  9. Thanks. I think the real issue is that the version of ubuntu this docker is built on (bionic) does not have the ffmpeg and libav libraries that have CUDA support. When and if this docker image gets upgraded to 20.04 it should 'just work', but I realize that is probably very low priority and I am ok with that.
  10. I am new to all this and keep seeing ES referenced. What is that?
  11. Yeah, it looks like that PPA doesn't include the libraries that zoneminder users. When I tried to force for CUDA mode in ZM using the ffmpeg option, it just reports this...
  12. So this repo has an ffmpeg build that should update the libraries too, but zmc still isn't using the video card https://launchpad.net/~savoury1/+archive/ubuntu/ffmpeg4?field.series_filter=bionic
  13. That is what I am looking at. It appears the ffmpeg-4 ppa there doesn't have nvidia support.. but someone has to have one!
  14. I am thinking there must be a debian ppa that has an ffmpeg with CUDA support. It looks like the one that is in the base image for zoneminder doesn't have it. It is 4.3.1 though. People are reporting the Ubuntu 20.04 works out of the box, probably because ffmpeg is built with CUDA support in that release... so I am gonna see if I can install that.
  15. I followed this post and now I see CUDA listed in in my nvidia-smi output. For those wondering, I had to add 3 options to the zoneminder config: extra parameters need to have "--runtime=nvidia" NVIDIA_VISIBLE_DEVICES Docker variable needs to be set with your video cards GUID NVIDIA_DRIVER_CAPABILITIES Docker variable needs to be set to 'all' I still don't see 'zmc' using the video card though, and ffmpeg doesn't list CUDA as an accelerator... so now I think I am having the same problem...