Jump to content

Djoss

Community Developer
  • Content Count

    1320
  • Joined

  • Last visited

  • Days Won

    9

Djoss last won the day on April 12

Djoss had the most liked content!

Community Reputation

254 Very Good

3 Followers

About Djoss

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Canada

Recent Profile Visitors

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

  1. You can try to run "htop" to see which process is using the cpu.
  2. Did you try to past with Shift-Insert or with Shift-Ctrl-v ?
  3. Does MakeMKV is ripping a disc?
  4. Instead of using Extra Parameters, your can add a "Device" and set its value to "/dev/dri/".
  5. By "container log" I meant the log that is accessible via the Docker page in unRAID. Click on the little icon at the most right column.
  6. No, this is currently not supported. Using cpu shares could be easier. See :
  7. It's earlier in the log, with messages starting with "[cont-init.d] 95-check-qsv.sh". You can provide the whole log if you want.
  8. You can look at the container's log. It should explain why Intel QSV is not working and what need to be done.
  9. Did you try with another browser and/or from another device?
  10. Could you also provide the output of: ls -l /dev/sr0 /dev/sg3 Do you know if the problem started after an updated version of MakeMKV ?
  11. Could you provide the output of the following commands: docker exec MakeMKV lsscsi -g -k docker exec MakeMKV env HOME=/config s6-applyuidgid -u 99 -g 100 -G 19 /opt/makemkv/bin/makemkvcon -r --cache=1 info disc:9999
  12. You need to edit container's settings and add a "Device". The device should be the one associated to your serial port (e.g. /dev/ttyS0). Then you also need to add a variable "SUP_GROUP_IDS" with the value sets to the group of your serial device. You can get it by executing: stat -c '%g' /dev/ttyS0
  13. This same drive was recognized in the past?
  14. It seems that you have a Terminal web window opened.
  15. You can have a look at the corresponding log file under /mnt/user/appdata/NginxProxyManager/log/nginx/ to have a better understanding of what's happening when you access these locations.