Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Æþerfox

Members
  • Joined

  • Last visited

  1. I swapped my CPU and now everything works great... No idea why my CPU would be bungling up a 100%GPU task, but whatever. I guess when they say Unraid isn't compatible with 1st gen Zen Architecture they really mean it.
  2. I have yet to find a cause or solution to the issues I have been having. I am now updated to the newest available versions of Unraid and Handbrake, I see in the patchnotes that QSV is disabled by default, to prevent crashes, and when running the autoconverter it crashes about 2min into a conversion when using QSV. However, when using the GUI to manually initiate the conversiion everything runs just fine. Since updating I have successfully converted six 4kUHD HDR movies from raw rips from makeMKV to AV1 10bit using QSV, and about a dozen 1080p rips to AV1 using QSV. SO GUI works just fine but the auto converter crashes almost immediately. This tells me that the issue is somewhere in the auto conversion script.
  3. After migrating to Unraid 7.1.2 Handbrake auto converter now just saves empty files.
  4. I don't know what your skill level is, but if your up to it you could try and compose your own docker container using the official Handbrake for Linux package available at the official Handbrake website https://handbrake.fr/ Handbrake currently has native support for AMD GPU hardware encoding (as well as nVidia, and Intel) baked into the program, so the inability to use other GPUs must be a limitation baked into this container. Now if you go this route, you will be losing the automatic video encoder function, as that is a custom feature and not standard to Handbrake... Though if you can make your own container you can probably figure out how to copy that code and add it to your container as well.
  5. During my testing I eliminated the possibility of it being a conflict, as the crash was occurring even when no other containers or services were running on my server. Just Unraid, the Intel GPU plugins, and Handbrake. After extensive testing I seem to have fixed my issue, though I do not know what it was. I ended up enabling SMB sharing for my appdata folder, shutting down and removing the Handbrake container, then going into appdata and deleting all the files left behind after the removal. I then reinstalled Handbrake and had it successfully encode 12 of the movies I had ripped while Handbrake was giving me issues. I then upgraded to Unraid 7.1.0, and experienced one unrelated system issue, my USB stick got corrupted, thankfully my last backup was from 2 weeks ago. During this time I have had no other containers running at the same time as Handbrake. I will begin starting up my other containers soon, one at a time to check for conflicts, but in my professional opinion, this was most likely an issue with the update script not removing old files. If I make no future updates to this, then I am not having Furter issues.
  6. I have an issue that I cannot find a solution to elsewhere. I believe the problem to be unique to Handbrake, as nothing else running on my server is currently causing any issues. To start, I was experiencing the idle crash bug common on Linux systems running on first generation Ryzen CPUs (issue due to incompatibility between how the Linux kernal calls for C-states and how 1st-gen Ryzen handles them), during this time, as long as I could keep the server from going idle, I could keep the server up indefinitely with absolutely no issues. As my work load declined, and I was not having stuff being backed up to the server 24/7, I finally got around to finding the fix for that issue, and changed the the PSU management in the UEFI to "Typical Idle Current". Ever since I made that change, I have not been able to successfully encode anything in Handbrake. One of three things happen any time I try to do any encodes in Handbrake, in order to most frequent to least frequent they are: The Handbrake Container just stops, no event is recorded in the logs, it just stops. I can start it again, and it will get part way through an encode and then crash again in one of these 3 ways. The Handbrake Container completely locks up but still shows as running. No event recorded in the logs. If I stop the container I can then start it again, but if I choose restart from the dropdown the entire server locks up, requiring a hard reset. The Unraid GUI and the Handbrake Container both become unresponsive, but my other Containers still function and can be accessed directly. Again no event recorded in the logs, and also when this happens, I can no longer access my SMB shares from my Windows PCs. I am currently running Unraid 7.0.1 on a Ryzen 1700, ASUS ROG Strix X370-F Gaming mobo using ethernet, Intel ARC Alchemist A750 GPU, my array consists of 4 HGST 8TB Enterprise drives 1 assigned to parity (all running off the mobo SATA controller), and I have a 2TB Predator GM7000 NVMe SSD as a Cache drive. My PSU is an 80Plus Gold Rosewill Lepton 500w that has proven very reliable. I don't think its a power draw issue, as before I fixed the idle crash bug, I was able to run a Handbrake QSV encode, while having 4 simultaneous Plex streams running with QSV hardware transcoding and the GPU running at 80% and that was while also pushing files to the array from 2 Windows PCs. With all that my total system power draw was about 400w. Also running on my server is MAKEMKV, Immich, GoDaddy-DDNS, Plex, and MKVToolNix.
  7. I hope you found your answer long before now, as I believe it is covered in an earlier post, but just in case you have not, and for others in the future, your syntax is wrong, it is underscores not hyphens. SAME_AS_SRC not SAME-AS-SRC

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.