• Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

sir_storealot's Achievements


Newbie (1/14)



  1. If anyone else stumbles upon this via google, I had exactly the same problem, clearing the website cache and cookies in chrome fixed the issue for me.
  2. Also just ran into this on 6.9.2
  3. Go to the console and do "ps waux", you will see that many services run as non-root users. The reason for this is to limit the damage that an attacker could do if a service gets compromised. That would really depend on what services you are running, but basically any vulnerability in a daemon, service, script etc. that is accessible via the net, processes information that might be malicious etc. could result in root access. Just to be clear, it does not mean that unraid servers are now all vulnerable or can be easily hacked/compromised. Nono... An attacker would still need other means to gain local non-root access, but unfortunately that is not uncommon. How big the risk is depends on your system, only you can judge. Look up the "swiss cheese model", this is now basically another hole in the cheese, on its own it wont do anything, but if it lines up with other holes it may lead to an incident, so thats why I like to see this hole stuffed Hope this helps, cheers guys and take care!
  4. Under the hood, Unraid is using the concept of different users with different privileges in the traditional *nix sense, just like any other distro. Just because you get a root prompt when you click the console icon does not mean its not relevant. The issue here is not someone with console access having root privileges, its more about potential privilege escalation in all the services and processes that are not running as root! This is a major crack in the standard *nix security concept.
  5. Surprised nobody mentioned this yet, or I'm just too dumb to use the search function... This is huge, a hotfix would be nice.
  6. PSA for anyone trying to get DLNA server to work: DLNA server in latest few versions appears to be broken, the issue is already (being) fixed upstream... So if you have issues dont waste any time looking for a solution, it should be a matter of time until the update arrives and it starts working again...
  7. Apologies, I did not mean to offend, I was just puzzled that while you seem to be active here and responded to other questions and issues after mine, mine was completely ignored and I did not quite understand why. I am not being entitled, unfriendly, demanding any solutions etc., I was just politely inquiring, and I appreciate the volunteer effort of all the great folks that allow us to run our setups. I dont think there was a need to react in such a negative way, but you seem to have a lot of stuff to sort through, so I understand and wish you the best and a speedy recovery for your foot. Point taken and sorry for bothering you.
  8. @saarg I am not sure why you are ignoring me, and I apologize if I have done anything wrong, is there any chance that you can point me in the right direction with my issue please?
  9. I have tried to explain my issue and post all relevant logfiles I could find, but my post is being ignored. Am I doing anything wrong?
  10. This is the best way I have seen someone react to a misunderstanding/internet drama. Well done!
  11. Hi, I want to use i915 IGPU acceleration in docker. Does it mean I should disable the stuff I have added to my go file before I upgrade to new beta: modprobe i915 sleep 5 chmod -R 777 /dev/dri chown -R nobody:users /dev/dri
  12. Still having the issue and cant figure it out @saarg Do you have any advice on what I could try please?
  13. Hey there! Unfortunately I also have issues with HW transcoding using Intel 10th Gen (i3-10100). Unraid Beta 6.9.0-30 [20:35:21] [INF] [1] Main: Jellyfin version: 10.6.4 Unraid go file with modprobe, docker is configured as per instructions and extra parameters /dev/dri shows up inside the docker: root@095b9610a70f:/# ls -la /dev/dri total 0 drwxr-xr-x 2 root root 80 Nov 3 20:35 . drwxr-xr-x 6 root root 360 Nov 3 20:35 .. crw-rw---- 1 root videoEhAShCrc 226, 0 Nov 3 20:35 card0 crwxrwxrwx 1 abc users 226, 128 Nov 3 20:35 renderD128 However, when running hw transcode: /usr/lib/jellyfin-ffmpeg/ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -vaapi_device /dev/dri/renderD128 -i file:"/movies/somex256file.mkv" -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 h264_vaapi -b:v 50360234 -maxrate 50360234 -bufsize 100720468 -profile:v high -level 41 -force_key_frames:0 "expr:gte(t,0+n_forced*3)" -g 72 -keyint_min 72 -sc_threshold 0 -vf "format=nv12|vaapi,hwupload,scale_vaapi=format=nv12" -start_at_zero -vsync -1 -codec:a:0 libmp3lame -ac 2 -ab 384000 -af "volume=2" -copyts -avoid_negative_ts disabled -f hls -max_delay 5000000 -hls_time 3 -individual_header_trailer 0 -hls_segment_type mpegts -start_number 0 -hls_segment_filename "/config/data/transcodes/d9c483124123a6454888b24ba9949550%d.ts" -hls_playlist_type vod -hls_list_size 0 -y "/config/data/transcodes/d9c483124123a6454888b24ba9949550.m3u8" ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers built with gcc 7 (Ubuntu 7.5.0-3ubuntu1~18.04) configuration: --prefix=/usr/lib/jellyfin-ffmpeg --target-os=linux --disable-doc --disable-ffplay --disable-shared --disable-libxcb --disable-sdl2 --disable-xlib --enable-gpl --enable-version3 --enable-static --enable-libfontconfig --enable-fontconfig --enable-gmp --enable-gnutls --enable-libass --enable-libbluray --enable-libdrm --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libwebp --enable-libx264 --enable-libx265 --enable-libzvbi --arch=amd64 --enable-libzimg --enable-opencl --enable-vaapi --enable-amf --enable-libmfx --enable-vdpau --enable-cuda --enable-cuda-llvm --enable-cuvid --enable-nvenc --enable-nvdec --enable-ffnvcodec --enable-libdav1d libavutil 56. 51.100 / 56. 51.100 libavcodec 58. 91.100 / 58. 91.100 libavformat 58. 45.100 / 58. 45.100 libavdevice 58. 10.100 / 58. 10.100 libavfilter 7. 85.100 / 7. 85.100 libswscale 5. 7.100 / 5. 7.100 libswresample 3. 7.100 / 3. 7.100 libpostproc 55. 7.100 / 55. 7.100 [AVHWDeviceContext @ 0x5575878157c0] libva: /usr/lib/jellyfin-ffmpeg/lib/dri/ init failed [AVHWDeviceContext @ 0x5575878157c0] Failed to initialise VAAPI connection: -1 (unknown libva error). Device creation failed: -5. Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': Input/output error Error parsing global options: Input/output error I have found some folks with similar errors here, suggesting that a new ffmpeg version might be the fix, but I have no clue how to correctly update ffmpeg inside the docker: LINK Or perhaps I need to install some non-free intel drivers?! Any help would be highly welcome - thank you!
  14. Guys I have /dev/dri showing up fine on boot, and it also shows up in the jellyfin docker which I configured to enable HW transcoding... however, I cannot get the HW transcode to work... Did you make it work with Jellyfin, or are you using some other tool? Uraid 6.9.0 beta - go file: #!/bin/bash # Start the Management Utility modprobe i915 chmod -R 777 /dev/dri chown -R nobody:users /dev/dri /usr/local/sbin/emhttp & Inside the jellyfin docker: root@e561ea4f8fc0:/# ls -la /dev/dri total 0 drwxr-xr-x 2 root root 80 Nov 1 20:38 . drwxr-xr-x 6 root root 360 Nov 1 20:38 .. crw-rw---- 1 root 18 226, 0 Nov 1 20:38 card0 crwxrwxrwx 1 99 users 226, 128 Nov 1 20:38 renderD12 Error I get in jellyfin: [AVHWDeviceContext @ 0x55b0757b6300] libva: /usr/lib/jellyfin-ffmpeg/lib/dri/ init failed [AVHWDeviceContext @ 0x55b0757b6300] Failed to initialise VAAPI connection: -1 (unknown libva error). Device creation failed: -5. Failed to set value '/dev/dri/renderD128' for option 'vaapi_device': Input/output error Error parsing global options: Input/output error Any hints please?