Jump to content


Popular Content

Showing content with the highest reputation since 06/20/19 in all areas

  1. 13 points
    To upgrade: If you are running any 6.4 or later release, click 'Check for Updates' on the Tools/Update OS page. If you are running a pre-6.4 release, click 'Check for Updates' on the Plugins page. If the above doesn't work, navigate to Plugins/Install Plugin, select/copy/paste this plugin URL and click Install: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer.plg Refer also to @ljm42 excellent 6.4 Update Notes which are helpful especially if you are upgrading from a pre-6.4 release. Bugs: If you discover a bug or other issue in this release, please open a Stable Releases Bug Report. This is a bug fix and security update release. Due to another set of processor vulnerabilities called Zombieland, and a set of TCP denial-of-service vulnerabilities called SACK panic, all users are encouraged to update. We are also still trying to track down the source of SQLite Database corruption. It will also be very helpful for those affected by this issue to also upgrade to this release. Version 6.7.1 2019-06-22 Base distro: btrfs-progs: version 5.1.1 curl: version 7.65.1 (CVE-2019-5435, CVE-2019-5436) dhcpcd: version 7.2.2 docker: version 18.09.6 kernel-firmware: version 20190607_1884732 mozilla-firefox: version 66.0.5 openssl: version 1.1.1c openssl-solibs: version 1.1.1c php: version 7.2.19 (removed sqlite support) samba: version 4.9.8 (CVE-2018-16860) xfsprogs: version 5.0.0 Linux kernel: version: 4.19.55 (CVE-2018-12126, CVE-2018-12127, CVE-2018-12130, CVE-2019-11091, CVE-2019-11833, CVE-2019-11477, CVE-2019-11478, CVE-2019-11479) intel-microcode: version 20190618 Management: shfs: support FUSE use_ino option Dashboard: added draggable fields in table Dashboard: added custom case image selection Dashboard: enhanced sorting Docker + VM: enhanced sorting Docker: disable button "Update All" instead of hiding it when no updates are available Fix OS update banner overhanging in Auzre / Gray themes Do not allow plugin updates to same version misc style corrections
  2. 7 points
  3. 7 points
    Can you promote SpaceInvaderOne? He's the only reason I use Unraid.
  4. 5 points
    To upgrade: If you are running any 6.4 or later release, click 'Check for Updates' on the Tools/Update OS page. If you are running a pre-6.4 release, click 'Check for Updates' on the Plugins page. If the above doesn't work, navigate to Plugins/Install Plugin, select/copy/paste this plugin URL and click Install: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer.plg Refer also to @ljm42 excellent 6.4 Update Notes which are helpful especially if you are upgrading from a pre-6.4 release. Bugs: If you discover a bug or other issue in this release, please open a Stable Releases Bug Report. We restored PHP/SQLite support and updated the kernel-firmware package. We are also still trying to track down the source of SQLite Database corruption. It will also be very helpful for those affected by this issue to also upgrade to this release. If you have issues with SQLite DB corruption, please post in this separate Bug Report. Version 6.7.2 2019-06-25 Base distro: kernel-firmware: version 20190620_7ae3a09 php version: 7.2.19 (restore sqlite support) sqlite version: 3.28.0 Linux kernel: version: 4.19.56
  5. 5 points
    I have made un updated video guide for setting up this great container. It covers setting up the container, port forwarding and setting up clients on Windows, macOS Linux (ubuntu Mate) and on cell phone - Android and IOS. Hope this guide helps people new to this setting up OpenVPN
  6. 4 points
    Currently unRAID uses basic auth to enter credentials for the web gui, but many password managers don't support this. Would be great if we could get a proper login page. Examples This kind of login page always works with password managers. This does not
  7. 4 points
    It's got a big LinuxServer logo at the top of the thread and lots of red warnings, and the first two posts go into some detail about how it works. The plugin is installed from Community Applications, with an author of LinuxServer.io How much clearer can we make it? Sent from my Mi A1 using Tapatalk
  8. 4 points
    Create a separate topic with a proper report of your problem and attach diagnostics. Posting a 3-line complaint on every release topic will not get you the necessary help.
  9. 4 points
    Sounds like you are attending a meeting. Stay strong.
  10. 4 points
    Today's updates to the mover tuning plugin allows you to do that (CPU and I/O priority)
  11. 4 points
  12. 4 points
    Damn, I do follow that repo and also the slackware64-current package list. What happened with this release, was that it was actually built and tested a couple days ago when 4.19.53 was released. Then noticed kernel was up to .55 very quickly and in looking at change log there is a single change (probably related to 'sack panic' changes) - and any time Greg K-H creates another patch release with a single change, it's probably important 😳 So I did a quick kernel update and rebuilt this 6.7.1 release & didn't notice that firmware update from yesterday - yeah this stuff is changing rapidly these days! How important is the f/w update to you? I can generate a 6.7.2 pretty quickly if so...
  13. 4 points
    Not sure if I'm disappointed or not. I had it in my head (based upon the avatar) that Tom wore Hawaiian shirts all the time.
  14. 3 points
    Attached is a debugged version of this script modified by me. I've eliminated almost all of the extraneous echo calls. Many of the block outputs have been replaced with heredocs. All of the references to md_write_limit have either been commented out or removed outright. All legacy command substitution has been replaced with modern command substitution The script locates mdcmd on it's own. https://paste.ee/p/wcwWV
  15. 3 points
    This is continuation of this original issue report. There is some conflicting information in that topic and, therefore, with your help, we want to try and get to the bottom of this. We have several test servers running trying to reproduce this problem, so far hasn't happened. The first thing we want to definitively establish is whether the problem is isolated to only those cases where /config inside the container is mapped to: /mnt/user/appdata vs. /mnt/cache/appdata or /mnt/diskN/appdata Note: it does not matter what the "Default appdata storage location" is set to on Settings/Docker page. Of interest is the actual path used by an individual container. What I'd like to ask is this: For those of you who have seen this DB corruption occur after updating from Unraid 6.6.x to 6.7.x, please note the placement of your 'appdata' folder and how it's mapped to your problematic container. Then update to 6.7.2 and run normally until you see corruption. At that point, please capture diagnostics and report how appdata is being mapped. If this is a huge PITA for you, then bow out of this testing - we are not trying to cause big disruptions for you. Finally I want to make clear: we are not "blaming" this issue on any other component, h/w or s/w, and also not "admitting" this is our problem. We have not changed any code we're responsible for that would account for this, which doesn't mean we don't have a bug somewhere - probably we do, and a change in the kernel or some other component might simply be exposing some long hidden issue. We are only interested in identifying and fixing the problem.
  16. 3 points
    What hostility? I haven't seen any from anyone but yourself. We are hard at work trying to reproduce and resolve this issue, but you seem to think that because we haven't yet, that we're sitting here just twiddling our thumbs. We are not. We have multiple test servers constantly running Plex and injecting new data to it to try and force corruption. Hasn't happened to us once. That leads us to believe that this may be specific to individual setups/hardware, but we haven't figured out why just yet. You have a completely valid method to get back to a working state: roll back to the 6.6.7 release. Otherwise we are continuing to do testing and will provide more for folks to try in this bug report thread as we have ideas to narrow this down. Clearly this issue isn't as widespread as some may think, otherwise I think we'd have an outpouring of users and this thread would be a lot longer than 4 pages at this point. That said, it is a VERY valid concern that we are very focused on resolving, but sometimes things take longer to fix.
  17. 3 points
    Granted this has been covered in a few other posts but I just wanted to have it with a little bit of layout and structure. Special thanks to [mention=9167]Hoopster[/mention] whose post(s) I took this from. What is Plex Hardware Acceleration? When streaming media from Plex, a few things are happening. Plex will check against the device trying to play the media: Media is stored in a compatible file container Media is encoded in a compatible bitrate Media is encoded with compatible codecs Media is a compatible resolution Bandwith is sufficient If all of the above is met, Plex will Direct Play or send the media directly to the client without being changed. This is great in most cases as there will be very little if any overhead on your CPU. This should be okay in most cases, but you may be accessing Plex remotely or on a device that is having difficulty with the source media. You could either manually convert each file or get Plex to transcode the file on the fly into another format to be played. A simple example: Your source file is stored in 1080p. You're away from home and you have a crappy internet connection. Playing the file in 1080p is taking up too much bandwith so to get a better experience you can watch your media in glorious 240p without stuttering / buffering on your little mobile device by getting Plex to transcode the file first. This is because a 240p file will require considerably less bandwith compared to a 1080p file. The issue is that depending on which format your transcoding from and to, this can absolutely pin all your CPU cores at 100% which means you're gonna have a bad time. Fortunately Intel CPUs have a little thing called Quick Sync which is their native hardware encoding and decoding core. This can dramatically reduce the CPU overhead required for transcoding and Plex can leverage this using their Hardware Acceleration feature. How Do I Know If I'm Transcoding? You're able to see how media is being served by playing a first something on a device. Log into Plex and go to Settings > Status > Now Playing As you can see this file is being direct played, so there's no transcoding happening. If you see (throttled) it's a good sign. It just means is that your Plex Media Server is able to perform the transcode faster than is necessary. To initiate some transcoding, go to where your media is playing. Click on Settings > Quality > Show All > Choose a Quality that isn't the Default one If you head back to the Now Playing section in Plex you will see that the stream is now being Transcoded. I have Quick Sync enabled hence the "(hw)" which stands for, you guessed it, Hardware. "(hw)" will not be shown if Quick Sync isn't being used in transcoding. PreRequisites 1. A Plex Pass - If you require Plex Hardware Acceleration Test to see if your system is capable before buying a Plex Pass. 2. Intel CPU that has Quick Sync Capability - Search for your CPU using Intel ARK 3. Compatible Motherboard You will need to enable iGPU on your motherboard BIOS In some cases this may require you to have the HDMI output plugged in and connected to a monitor in order for it to be active. If you find that this is the case on your setup you can buy a dummy HDMI doo-dad that tricks your unRAID box into thinking that something is plugged in. Some machines like the HP MicroServer Gen8 have iLO / IPMI which allows the server to be monitored / managed remotely. Unfortunately this means that the server has 2 GPUs and ALL GPU output from the server passed through the ancient Matrox GPU. So as far as any OS is concerned even though the Intel CPU supports Quick Sync, the Matrox one doesn't. =/ you'd have better luck using the new unRAID Nvidia Plugin. Check Your Setup If your config meets all of the above requirements, give these commands a shot, you should know straight away if you can use Hardware Acceleration. Login to your unRAID box using the GUI and open a terminal window. Or SSH into your box if that's your thing. Type: cd /dev/drils If you see an output like the one above your unRAID box has its Quick Sync enabled. The two items were interested in specifically are card0 and renderD128. If you can't see it not to worry type this: modprobe i915 There should be no return or errors in the output. Now again run: cd /dev/drils You should see the expected items ie. card0 and renderD128 Give your Container Access Lastly we need to give our container access to the Quick Sync device. I am going to passively aggressively mention that they are indeed called containers and not dockers. Dockers are manufacturers of boots and pants company and have nothing to do with virtualization or software development, yet. Okay rant over. We need to do this because the Docker host and its underlying containers don't have access to anything on unRAID unless you give it to them. This is done via Paths, Ports, Variables, Labels or in this case Devices. We want to provide our Plex container with access to one of the devices on our unRAID box. We need to change the relevant permissions on our Quick Sync Device which we do by typing into the terminal window: chmod -R 777 /dev/dri Once that's done Head over to the Docker Tab, click on the your Plex container. Scroll to the bottom click on Add another Path, Port, Variable Select Device from the drop down Enter the following: Name: /dev/driValue: /dev/dri Click Save followed by Apply. Log Back into Plex and navigate to Settings > Transcoder. Click on the button to SHOW ADVANCED Enable "Use hardware acceleration where available". You can now do the same test we did above by playing a stream, changing it's Quality to something that isn't its original format and Checking the Now Playing section to see if Hardware Acceleration is enabled. If you see "(hw)" congrats! You're using Quick Sync and Hardware acceleration [emoji4] Persist your config On Reboot unRAID will not run those commands again unless we put it in our go file. So when ready type into terminal: nano /boot/config/go Add the following lines to the bottom of the go file modprobe i915chmod -R 777 /dev/dri Press Ctrl X, followed by Y to save your go file. And you should be golden!
  18. 3 points
    Looks like the card was touching the metal surrounding the slot.
  19. 3 points
  20. 3 points
    Do you want to stay informed about all things Unraid? Sign up for our monthly newsletter and you'll receive a concise digest of new blog posts, popular forum posts, product/company announcements, videos and more! https://unraid.net/blog/unraid-monthly-digest Cheers
  21. 3 points
    To the developers, to everyone in this community involved with getting unRAID where it stands today! I guess unRAID is written differently these days. I remember starting with unRAID Server Plus almost 10 years ago, the days Tom Mortensen thanked you in person for buying a license, no criticism here of course . For some reasons, now still very obscure to my mind (getting old), I installed one of the first versions of Windows Home Server. After that it got killed by MS I went with an Apple Server, great idea (NOT) and switched to Windows 10 with Stablebit Drivepool for a couple of years now. Somehow never looked back although I never really liked it a lot, way too clean and lean for an ex-Unix admin... Until recently. I rediscovered unRAID and I must say that I was baffled about the software, the plugins, the dockers, the whole setup and especially about the supporting community that arose around this beauty. Moved 15TB of media through the Unassigned Devices plugin to a newly built array over the weekend, parity build is now ongoing. Happy! Thanks! Mike
  22. 3 points
    Hey everyone, just thought I'd put this up here after reading a syslog by another forum member and realizing a repeating pattern I've seen here where folks decide to let Plex create temporary files for transcoding on an array or cache device instead of in RAM. Why should I move transcoding into RAM? What do I gain? In short, transcoding is both CPU and IO intensive. Many write operations occur to the storage medium used for transcoding, and when using an SSD specifically, this can cause unnecessary wear and tear that would lead to SSD burnouts happening more quickly than is necessary. By moving transcoding to RAM, you alleviate the burden from your non-volatile storage devices. RAM isn't subject to "burn out" from usage like an SSD would be, and transcoding doesn't need nearly as much space in memory to perform as some would think. How much RAM do I need for this? A single stream of video content transcoded to 12mbps on my test system took up 430MB on the root ram filesystem. The quality of the source content shouldn't matter, only the bitrate to which you are transcoding. In addition, there are other settings you can tweak to transcoding that would impact this number including how many second of transcoding should occur in advance of being played. Bottom line: If you have 4GB or less of total RAM on your system, you may have to tweak settings based on how many different streams you intend on transcoding simultaneously. If you have 8GB or more, you are probably in the safe zone, but obviously the more RAM you use in general, the less space will be available for transcoding. How do I do this There are two tweaks to be made in order to move your transcoding into RAM. One is to the Docker Container you are running and the other is a setting from within the Plex web client itself. Step 1: Changing your Plex Container Properties From within the webGui, click on "Docker" and click on the name of the PlexMediaServer container. From here, add a new volume mapping: /transcode to /tmp Click "Apply" and the container will be started with the new mapping. Step 2: Changing the Plex Media Server to use the new transcode directory Connect to the Plex web interface from a browser (e.g. http://tower:32400/web). From there, click the wrench in the top right corner of the interface to get to settings. Now click the "Server" tab at the top of this page. On the left, you should see a setting called "Transcoder." Clicking on that and then clicking the "Show Advanced" button will reveal the magical setting that let's you redirect the transcoding directory. Type "/transcode" in there and click apply and you're all set. You can tweak some of the other settings if desired to see if that improves your media streaming experience. Thanks for reading and enjoy!
  23. 3 points
    Finally got around to updating to 6.7.2 from 6.7.0 (I skipped 6.7.1). So far, I have seen zero issues. System boots fine, WebGUI is normal, all plugins and dockers are functioning as expected, all disks present, etc. I have to say that has almost always been my experience since I started with unRAID back with version 5.0 beta14 (as prereleases used to be called). I have had the same flash drive through almost all those releases and the server has been through several motherboard, CPU and RAM changes as well. The only problems I ever had related to a specific release of unRAID were eventually resolved with BIOS and Linux kernel updates and that has only happened once in each case.; both times with interim workarounds. I know those who have problems, especially when those problems occur right after an unRAID OS update, may be inclined to believe something was "broken" in unRAID and can't understand how that got through testing. Keep in mind that most issues end up being related to specific hardware, USB drives, plugins, configurations, kernel revisions, BIOS revisions, id10t errors, etc. There is no way Limetech can test every possible combination. In fact, the issue might have pre-dated the unRAID OS update and was only revealed because the update required a server reboot which touches all of the above mentioned pieces of the puzzle. The swiftness with which Limetech, community developers and the community in general responds to even the most obscure edge cases is truly remarkable when compared to other OS/App vendors. With the rapid pace of kernel releases, CVEs, security mitigations and everything else lately, I am giving Limetech a huge virtual pat on the back for keeping up with it all as quickly as they do.
  24. 3 points
    It's sad that people have now made this awesome hard work become a post worthy of: https://old.reddit.com/r/ChoosingBeggars/ Please remember before this came out, we had to buy expensive large core processors AND use more power to do what we are doing today. Thank you again for all your hard work. Without it we are back to what we had before which is nothing. *I hope your family member is doing well. No amount of software/Computer work is worth not having those memories of said family members.*
  25. 3 points
    No, let's be honest here, the end user needs to take some responsibility with this one. LimeTech publishes an update, user knows that they're using an Nvidia or DVB build then you got to wait till it's done until you upgrade. As soon as I build them I post in the support thread so set up an email alert. Why do we need to do more and more work to essentially spoon feed? Come on guys, really? Sent from my Mi A1 using Tapatalk
  26. 3 points
    I do not think we should add anything messing with the update check for unraid. That is just asking for trouble.
  27. 3 points
    You guys please settle down. The fact that sqlite support was in php in the first place was an oversight. We never intended that a plugin would utilize a database application and honestly, I didn't know about this one. Seems to me using sqlite for something like this is a bit overkill ... but oh well, we'll add it back once we figure out wtf is wrong with plex/sqlite db corruption. This is correct. Also correct it should have nothing to do with the issue. But seems like it's more than just "a few users" though which is why we're tying what we can, as fast as we can, to get to the bottom of it. Please no more beating. Sure in an ideal world it maybe should have been a beta/rc/whatever but there are other significant security patches which need to be distributed to the user base. As for breaking this plugin, all I can say is "oops".
  28. 3 points
    For tehuti in this 6.7.1 release we're using tn40xx- for 6.8 beta we're using tn40xx- - which only change supposedly is to compile against 5.x Linux kernel. For intel in 6.7.1 release, correct: 5.5.5 for Unraid 6.8 beta - we still use stock ixgbe drivers because still Intel has not released build for Linux 5.x kernel.
  29. 3 points
    It got pushed back but it looks like the necessary changes to rclone union allowing unionfs to be dropped will be in the next release - 1.4.9 https://github.com/ncw/rclone/milestone/36
  30. 3 points
    There is another topic on the subject but I'm giving up on that one: We got to the point where OP was convinced that appdata/plex residing on a single-disk btrfs cache device and mapped using path: /mnt/cache/appdata/plex was stable. What would be helpful is a) others to confirm, and then b) after confirming this exact config is stable, simply change path to: /mnt/user/appdata/plex This will tell me if simply passing I/O through 'shfs' layer is introducing this issue. If it starts to fail, then there are other tests to try.
  31. 3 points
    I've bumped Unmanic to 0.0.1-beta5 This includes the following changes: Modify some historical logging of useful stats This sets us up to start adding extra info like eta during the conversion process as well as the stats mentioned below Adds new "See All Records" screen Any suggestions for stats that you would like on this screen would be great Note that due to the changes in logging, only newly converted items will show here. Old stuff wont due to missing statistics data. Sorry Create backups of settings when saving (there were some cases where the settings were invalid but still saved). This corrupted our data and made it impossible to read. So now we test prior to committing changes. FFMPEG was causing some errors on certain files. If you have noted any conversion failures in the past, can you please re-test with this version to confirm if it is now resolved or not. Log rotation If you are debugging, you are spewing a crap ton of data to the logs. This update rotates the logs at midnight every day and keeps them for 7 days. Even if you are not debugging, this is much better. The next milestone is to add extended functionality to the settings: https://github.com/Josh5/unmanic/milestone/4 This will hopefully be the last major tidy up of core functionality. I think that once this milestone is complete we can safely pull this out of beta and look at things like HW decoding and improving on data that is displayed throughout the WebUI.
  32. 3 points
    I would to know if Unraid has any plans to release an official API.
  33. 2 points
    Hi, I've posted this already, but into an incorrect forum where it remained unnoticed. So sorry for the x-post. Symptoms: Plex HW transcoding does not work with Docker on unRAID 6.7.x (0 through 2), although it is working fine when downgrading to 6.6.7 without any change in unRAID or Docker container configuration. go file: #!/bin/bash #Setup drivers for hardware transcoding in Plex modprobe i915 chmod -R 777 /dev/dri #Start the Management Utility /usr/local/sbin/emhttp & syslinux.cfg untouched as i915 support is included OOB for some time now, however during my troubleshooting attempts, I've tried to force i915 support by modifying the aforementioned config file like this (with no effect of course): label Unraid OS menu default kernel /bzimage append pci=realloc=off initrd=/bzroot i915.alpha_support=1 /dev/dri is being passed to the Plex docker container as a device and is visible to the container: root@532cd6092721:/# ls -la /dev/dri total 0 drwxr-xr-x 2 root root 80 Jun 19 11:05 . drwxr-xr-x 6 root root 360 Jun 19 11:05 .. crw-rw---- 1 root video 226, 0 Jun 19 11:05 card0 crwxrwxrwx 1 99 users 226, 128 Jun 19 11:05 renderD128 Plex transcoder does appear to see the iGPU device, Plex dashboard shows that a HW transcode session is ongoing, however video keeps buffering and playback is never initiated. I've checked Plex log quite extensively and they do IMO confirm what I've stated above - the transcoder sees the iGPU, transcode session starts, but there is no video being output. Jun 19, 2019 15:38:32.248 [0x15102bbfd700] DEBUG - TPU: hardware transcoding: using hardware decode accelerator vaapi Jun 19, 2019 15:38:32.248 [0x15102bbfd700] DEBUG - [Universal] Using local file path instead of URL: /movies/Captain Marvel (2019)/Captain Marvel (2019) - Bluray-1080p.mkv Jun 19, 2019 15:38:32.249 [0x15102bbfd700] DEBUG - HTTP requesting GET Jun 19, 2019 15:38:32.249 [0x151093dfe700] DEBUG - Auth: authenticated user 1 as obfuscated Jun 19, 2019 15:38:32.249 [0x15102b1f8700] DEBUG - Request: [ (Loopback)] GET /library/streams/181 (14 live) GZIP Signed-in Token (obfuscated) Jun 19, 2019 15:38:32.252 [0x15102b1f8700] DEBUG - Content-Length of /movies/Captain Marvel (2019)/Captain Marvel (2019) - Bluray-1080p.en.srt is 91753. Jun 19, 2019 15:38:32.253 [0x151093dfe700] DEBUG - Completed: [] 200 GET /library/streams/181 (14 live) GZIP 3ms 91753 bytes Jun 19, 2019 15:38:32.253 [0x15102bbfd700] DEBUG - HTTP 200 response from GET Jun 19, 2019 15:38:32.253 [0x15102bbfd700] DEBUG - Detected character set of UTF-8. Jun 19, 2019 15:38:32.254 [0x15102bbfd700] DEBUG - Downloaded stream from [] (codec: srt) to temporary file [/transcode/Transcode/Sessions/plex-transcode-jk19rtdgc5dtot7fu88d8gsy-ef1b128f-4370-4808-a01d-07825b462435/temp-0.srt] Jun 19, 2019 15:38:32.254 [0x15102bbfd700] DEBUG - TPU: hardware transcoding: zero-copy support present Jun 19, 2019 15:38:32.254 [0x15102bbfd700] DEBUG - TPU: hardware transcoding: using zero-copy transcoding Jun 19, 2019 15:38:32.254 [0x15102bbfd700] DEBUG - TPU: hardware transcoding: final decoder: vaapi, final encoder: vaapi Jun 19, 2019 15:38:32.255 [0x15102bbfd700] DEBUG - Job running: EAE_ROOT='/tmp/pms-85736070-8352-49fb-956e-d7be9ba4a099/EasyAudioEncoder' FFMPEG_EXTERNAL_LIBS='/config/Library/Application\ Support/Plex\ Media\ Server/Codecs/21b5515-2321-linux-x86_64/' XDG_CACHE_HOME='/config/Library/Application Support/Plex Media Server/Cache' XDG_DATA_HOME='/usr/lib/plexmediaserver/Resources' X_PLEX_TOKEN='xxxxxxxxxxxxxxxxxxxx' '/usr/lib/plexmediaserver/Plex Transcoder' '-codec:0' 'h264' '-hwaccel:0' 'vaapi' '-hwaccel_fallback_threshold:0' '10' '-hwaccel_output_format:0' 'vaapi' '-codec:1' 'dca' '-analyzeduration' '20000000' '-probesize' '20000000' '-i' '/movies/Captain Marvel (2019)/Captain Marvel (2019) - Bluray-1080p.mkv' '-analyzeduration' '20000000' '-probesize' '20000000' '-i' '/transcode/Transcode/Sessions/plex-transcode-jk19rtdgc5dtot7fu88d8gsy-ef1b128f-4370-4808-a01d-07825b462435/temp-0.srt' '-filter_complex' '[0:0]hwupload[0];[0]scale_vaapi=w=1278:h=538:format=nv12[1];[1]hwupload[2]' '-filter_complex' '[0:1] aresample=async=1:ocl='\''stereo'\'':osr=48000[3]' '-map' '[2]' '-metadata:s:0' 'language=eng' '-codec:0' 'h264_vaapi' '-b:0' '2717k' '-maxrate:0' '3623k' '-bufsize:0' '7246k' '-r:0' '23.975999999999999' '-force_key_frames:0' 'expr:gte(t,0+n_forced*5)' '-map' '[3]' '-metadata:s:1' 'language=eng' '-codec:1' 'aac' '-b:1' '148k' '-f' 'dash' '-min_seg_duration' '5000000' '-skip_to_segment' '1' '-time_delta' '0.0625' '-manifest_name' '' '-avoid_negative_ts' 'disabled' '-map_metadata' '-1' '-map_chapters' '-1' 'dash' '-map' '1:s:0' '-metadata:s:0' 'language=eng' '-codec:0' 'ass' '-f' 'segment' '-segment_format' 'ass' '-segment_time' '1' '-segment_header_filename' 'sub-header' '-segment_start_number' '0' '-segment_list' '' '-segment_list_type' 'csv' '-segment_list_size' '2147483647' '-segment_list_separate_stream_times' '1' '-segment_format_options' 'ignore_readorder=1' 'sub-chunk-%05d' '-start_at_zero' '-copyts' '-vsync' 'cfr' '-y' '-vaapi_device' '/dev/dri/renderD128' '-nostats' '-loglevel' 'quiet' '-loglevel_plex' 'error' '-progressurl' '' Jun 19, 2019 15:38:32.256 [0x15102bbfd700] DEBUG - Jobs: Starting child process with pid 586 Jun 19, 2019 15:38:32.281 [0x15102adf6700] DEBUG - Request: [ (Loopback)] PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress?status=startup (15 live) Signed-in Token (obfuscated) Jun 19, 2019 15:38:32.282 [0x151093dfe700] DEBUG - Completed: [] 204 PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress?status=startup (15 live) 0ms 203 bytes (pipelined: 1) (range: bytes=0-) Jun 19, 2019 15:38:32.282 [0x1510916b8700] DEBUG - Request: [ (Loopback)] PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress?status=opening (15 live) Signed-in Token (obfuscated) Jun 19, 2019 15:38:32.282 [0x151093dfe700] DEBUG - Completed: [] 204 PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress?status=opening (15 live) 0ms 203 bytes (pipelined: 2) (range: bytes=0-) Jun 19, 2019 15:38:32.284 [0x15102aff7700] DEBUG - Request: [ (Loopback)] PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress?status=opened (15 live) Signed-in Token (obfuscated) Jun 19, 2019 15:38:32.284 [0x151093fff700] DEBUG - Completed: [] 204 PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress?status=opened (15 live) 0ms 203 bytes (pipelined: 3) (range: bytes=0-) Jun 19, 2019 15:38:32.284 [0x15102b9fc700] DEBUG - Request: [ (Loopback)] PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress/stream?index=0&id=0&codec=h264&type=video (14 live) Signed-in Token (obfuscated) Jun 19, 2019 15:38:32.285 [0x151093fff700] DEBUG - Completed: [] 206 PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress/stream?index=0&id=0&codec=h264&type=video (14 live) 0ms 256 bytes (pipelined: 4) (range: bytes=0-) Jun 19, 2019 15:38:32.285 [0x15102adf6700] DEBUG - Request: [ (Loopback)] PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress/stream?index=1&id=0&codec=dts&type=audio (14 live) Signed-in Token (obfuscated) Jun 19, 2019 15:38:32.285 [0x151093fff700] DEBUG - Completed: [] 206 PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress/stream?index=1&id=0&codec=dts&type=audio (14 live) 0ms 256 bytes (pipelined: 5) (range: bytes=0-) Jun 19, 2019 15:38:32.340 [0x1510916b8700] DEBUG - Request: [ (Loopback)] PUT /video/:/transcode/session/jk19rtdgc5dtot7fu88d8gsy/ef1b128f-4370-4808-a01d-07825b462435/progress/streamDetail?index=0&id=0&codec=h264&type=video&profile=High&language=eng&width=1920&height=808&interlaced=0&level=41&frameRate=23.9 Affected systems: As evidenced by other users, it appears only 7th gen Intel processors including UHD600 iGPU are affected, namely Celeron J4105 (Gemini Lake) Thanks in advance for looking into this.
  34. 2 points
    Maybe the case angled the board towards that edge when tightened into the back panel? I've seen people use too tall motherboard standoffs, or just poor manufacturing tolerances. Also, the typical card in that slot would have retention at the other end of the board with the "hockey stick" clip. This board only attaches at one end, allowing uneven insertion. In any case, there was obviously zero clearance in an area that needed an air gap.
  35. 2 points
    THREAD LOCKED- Stay tuned for a blog with Tom's answer's! For an upcoming blog, we’ll be publishing a Q&A with Tom Mortensen, the Founder and CEO of Lime Technology and creator of Unraid. This is where you, the Unraid community come in: For the coming weeks, we’re opening up the floor to you all to ask Tom (@limetech) a question. Anything and everything is fair game-- just drop your question into this forum thread and he’ll do his best to get as many answered as possible (can't guarantee every question will be answered). The floor is yours! Here’s a little more info about Tom from our website: Tom began his career in enterprise-storage at a start-up company called Maxstrat. Maxstrat was one of the first companies to offer disk array products and was ultimately purchased by Sun Microsystems in 1999. After the Sun Microsystems acquisition, Tom worked in their Network Storage Division as a system architect, and later for other start-up companies before starting Lime Technology. With his passion for electronic media and background in storage, he knew there had to be a better way to store and stream media content throughout his home, so in 2005 he invented Unraid to protect and manage his media files. Unraid was a new twist on an older technology that didn’t require all the devices in an array to be continually spun up, thereby reducing power consumption, and increasing the lives of the drives. Tom is very excited about what the future holds for Lime Technology as we continue to be on the forefront of digital media storage innovation. On a more personal note, one of Tom’s favorite hobbies is brewing beer.
  36. 2 points
    Edit: This is not a problem with an easy solution at all. I can monitor the transcode processes and make sure that everything is killed - but the only solution is to kill Plex: https://forums.plex.tv/t/stuck-in-p-state-p0-after-transcode-finished-on-nvidia/387685/24 I can user fuser -vk /dev/nvidia* and it will immediately switch to a P8 state. The only process using the card when this is run is "Plex Media Server" It's not hard to write a script that will only do this if: There are no processes using the card and the card is in a P0 state. I just don't know if there are any undesirable side-effects of doing it this way. Here is such a script: #!/bin/bash while true; do cur_pstate=$(nvidia-smi --query-gpu=pstate --format=csv,noheader) running_processes=$(ps --no-headers "$(nvidia-smi |tail -n +16 | head -n -1 | sed 's/\s\s*/ /g' | cut -d' ' -f3)" | wc -l) 2>/dev/null if [[ $cur_pstate = "P0" && $running_processes -eq 0 ]]; then # if we got here, the card is only running the Xorg process and is in the P0 state, let's fix that. fuser -kv /dev/nvidia* echo "Reset Power State" fi #sleep so we aren't blocking a thread constantly. sleep 1 done Starting the X server on Unraid does allow one to open nvidia settings; to do this you can use a script like this to start the X server (note, that since chvt and fgconsole aren't available, you will have to switch back to VT7 by pressing Ctrl+Alt+F7): #!/bin/bash ##This will only work on single GPU systems: GPUID=$(nvidia-xconfig --query-gpu-info | grep BusID | sed 's/^[^:]*: //') #Now that we know the PCI BusID of the card we can create the X server with a fake display: nvidia-xconfig -s -a --allow-empty-initial-configuration --use-display-device=None --virtual=640x480 --busid "$GPUID" -o /dev/stdout | X :99 -config /dev/stdin& Once you have that server running, you can return to the default unraid GUI and run: nvidia-settings -c :99 To open nvidia-settings on the card. You could also store an xorg configuration file and use that for the virtual X display, and to set persistent nvidia settings. The only way I can think of to fix this properly is to figure out why the Plex process is claiming the card and prevent that from happening. I'll look into it some more, but this needs to be fixed properly by Plex/nVidia. The linked thread at the Plex forums has more information. I may be able to detach the Plex Transcoder process with the wrapper script, making it it's own entity, and then trapping the SIGINT/SIGKILL in the wrapper and using it to kill the transcoder, effectively using the wrapper script to separate the Plex Media Server process from the Plex Transcoder process. It's pretty kludgy, but might work. Oh Boy: We're in idle P-State while transcoding territory!
  37. 2 points
    It's all working from here. Check your sonarr if you don't believe me 😁 you really should password protect those services
  38. 2 points
    In the Bug Reports section of this forum.
  39. 2 points
  40. 2 points
    Fix Common Problems is telling me that Write Cache is disabled on a drive. What do I do? This test has nothing to do with any given unRaid version. For some reason, sometimes hard drive manufacturers disable write cache on their drives (in particular shucked drives) by default. This is not a problem per se, but you will see better performance by enabling the write cache on the drive in question. To do this, first make a note of the drive letter which you can get from the Main Tab Then, from unRaid's terminal enter in the following (changing the sdX accordingly) hdparm -W 1 /dev/sdm You should get a response similar to this: /dev/sdm: setting drive write-caching to 1 (on) write-caching = 1 (on) If write caching stays disabled, then either the drive is a SAS drive, in which case you will need to utilize the sdparm commands (google is your friend), or the drive may be connected via USB in which case you may not be able to do anything about this. 99% of the time, this command will permanently set write caching to be on. In some rare circumstances, this change is not permanent, and you will need to add the appropriate command to either the "go" file (/config/go on the flash drive), or execute it via the user scripts plugin (with it set to run at first array start only) It should be noted that even with write-caching disabled this is not a big deal. Only performance will suffer. No other ill-effects will happen. NOTE: If this does not work for you, then you will either need to contact the drive manufacturer as to why or simply ignore the warning from Fix Common Problems
  41. 2 points
    At least I'm off the hook to answer
  42. 2 points
    Oh dear. My prayers for you and your family, mate.
  43. 2 points
    It's easy to miss nuance of mood in forum posts, both in people "complaining" and in people responding to "complaints". Everyone should try and keep that in mind. The fix will be available soon, let's just give this a rest please.
  44. 2 points
    Why it's not appearing, I don't know, but effectively there's no point in any mappings when you're running on a custom bridge, as all mappings are ignored anyways
  45. 2 points
    None of this little discussion belongs in this thread, but it is what it is. But, every single user of CA has had to acknowledge this:
  46. 2 points
    The Plex database corrupted twice on my server, and Sonarr at least twice, resulting in many of my hours used resolving the problems. Both were stored in /mnt/user/appdata/. I have moved everything to /mnt/cache/appdata/ by toggling the 'use cache only' setting and so far no database corruptions. I appreciate limetech taking this matter seriously and want to say thanks for an otherwise fantastic 6.7.0 release.
  47. 2 points
    Yes, a new Docker container image is now available
  48. 2 points
    Q1: Are 2.5' HDD any good in a NAS, longetivity wise? 2.5" HDD maxes out at 5TB (and that is the 15mm thickness, some cases don't let you mount 15mm 2.5") while 3.5" maxes out at 14TB currently. That means you will have to use 3x as many 2.5" for the same capacity, likely means needing additional SATA controller, which adds potential points of failure. So longevity isn't more or less a concern vs 3.5" but it's just more troublesome. Q2: Is ECC memory absolutely necessary? What will happen if I don't have them? It's only necessary if your hardware demands it (e.g. some sever-grade motherboard/CPU only works with ECC). Q3: Are the upcoming QLC SSD any good, longevity wise? Nobody knows! Longevity needs time to test; however, SSD generally will last longer than HDD simply for not having any moving parts. QLC to SSD is like SMR for HDD i.e. reducing price for higher storage capacity at the cost of lower performance. On some workloads I tested, a TLC SATA SSD is faster than the QLC Intel 660p NVMe. Emphasis on "some". Q4: How powerful should the PSU be for a 10-drive setup? Go to pcpartpicker, enter your hardware and see the power estimate. Then add 20% just to be safe. Q5: Are the following tasks achievable via unRAID? (ordered in priority) Yes but your hardware might be slightly underpower. It's recommended to reserve core 0 for Unraid tasks, at least 1 core for dockers, leaving only 2 left for your gaming VM. Not the end of the world but for CPU-bound games, you will be able to tell the diff.
  49. 2 points
    With Unraid 6.7.0 you shouldn't need i915.alpha_support=1 in your syslinux.cfg file. The i915 driver has for a while directly supported up to 8th generation Coffee Lake. It doesn't yet support 9th generation Coffee Lake though. Beyond that I'm not sure what would prevent it from working?
  50. 2 points
    For anyone who needs the script here it is: #!/bin/bash # Drives declare -a StringArray=("ata-WDC_WD2003FYYS-70W080_WJUN0123456" "DRIVE2" "DRIVE3" "DRIVE4") # Show status echo "Current drive status: " for drive in ${StringArray[@]}; do hdparm -W /dev/disk/by-id/$drive done # Enable write caching for drive in ${StringArray[@]}; do hdparm -W 1 /dev/disk/by-id/$drive done # Show status again echo "Finished running, check if the write cache was enabled!" for drive in ${StringArray[@]}; do hdparm -W /dev/disk/by-id/$drive done Replace the serial codes in the StringArray and you should be good to go! Pop it in User Scripts.