Leaderboard

Popular Content

Showing content with the highest reputation on 10/16/21 in all areas

  1. ***Update*** : Apologies, it seems like there was an update to the Unraid forums which removed the carriage returns in my code blocks. This was causing people to get errors when typing commands verbatim. I've fixed the code blocks below and all should be Plexing perfectly now Y =========== 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/dri ls 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/dri ls 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/dri Value: /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 i915 chmod -R 777 /dev/dri Press Ctrl X, followed by Y to save your go file. And you should be golden!
    1 point
  2. It is possible to setup a LAN to LAN VPN connection between two Unraid systems running Wireguard. The steps below should work on simple networks, if yours is more complicated then you'll need to figure out how to adapt it. This assumes you already have at least one working WireGuard connection and are familiar with how it works. First, gather the following information for your two networks. The names and numbers below are samples, you'll need to adjust for your situation: Network1: 192.168.1.0/24 Router1: 192.168.1.1 Unraid1: 192.168.1.50 Endpoint1 DNS: network1.duckdns.org Endpoint1 Port: 52001 Network2: 192.168.2.0/24 Router2: 192.168.2.1 Unraid2: 192.168.2.50 Endpoint2 DNS: network2.duckdns.org Endpoint2 Port: 52002 VPN Tunnel: 10.252.100.0/24 Unraid1 tunnel IP: 10.252.100.1 Unraid2 tunnel IP: 10.252.100.2 A few things: Note that Network1 and Network2 *have* to be different. For instance, you can't connect two networks that both use the 192.168.0.0/24 subnet. You also need to pick a VPN Tunnel subnet that is not being used on either network, it must be unique. You need to setup DDNS for both networks as well. LSIO has a nice Duck DNS docker you can use if needed. On Unraid1: Create a new Tunnel named "Network1-Network2". Don't add a peer to an existing tunnel, it is better if this is a separate tunnel so you can easily turn it off without affecting your other WireGuard connections. Switch to Advanced Mode Click "Generate Keypair". These are the private and public keys for Unraid1, you will need them later. Set the "local tunnel network pool" to the "VPN Tunnel" you chose above Set the "local tunnel address" to the "Unraid1 tunnel IP" from above Set the "Local endpoint" to the "Endpoint1 DNS" and "Endpoint1 Port" defined above Click Apply Click Add Peer Name it "Unraid2" Choose "LAN to LAN access" Click "Generate Keypair". These are the private and public keys for Unraid2, you will need them later. Click "Generate Key". This is the preshared key, you will need it later. Set the "Peer tunnel address" to the "Unraid2 tunnel IP" defined above Set the "Peer endpoint" to the "Endpoint2 DNS" and "Endpoint2 Port" defined above Set "Peer allowed IPs" to the "VPN Tunnel" and "Network2" defined above, with a comma between. i.e. "10.252.100.0/24, 192.168.2.0/24" Click Apply Start the Tunnel On Router1: If UPnP is disabled, setup a port forward for "Endpoint1 Port" (UDP) that points to "Unraid1" Setup a static route for all of "Network2" that is routed through "Unraid1". Note that if your router asks for a subnetmask, 255.255.255.0 is the equivalent of /24. Setup a second static route for "VPN Tunnel" that also is routed through "Unraid1". On Unraid2: Create a new Tunnel named "Network2-Network1". Switch to Advanced Mode Copy the private and public keys for Unraid2 that you determined above. Take care to use the correct keys or none of this will work. Set the "local tunnel network pool" to the "VPN Tunnel" you chose above Set the "local tunnel address" to the "Unraid2 tunnel IP" from above. Set the "Local endpoint" to the "Endpoint2 DNS" and "Endpoint2 Port" defined above Click Apply Click Add Peer Name it "Unraid1" Choose "LAN to LAN access" Copy the private and public keys for Unraid1 that you determined above Copy the preshared key from above Set the "Peer tunnel address" to the "Unraid1 tunnel IP" defined above Set the "Peer endpoint" to the "Endpoint1 DNS" and "Endpoint1 Port" defined above Set "Peer allowed IPs" to the "VPN Tunnel" and "Network1" defined above, with a comma between. i.e. "10.252.100.0/24, 192.168.1.0/24" Click Apply Start the Tunnel On Router2: If UPnP is disabled, setup a port forward for "Endpoint2 Port" (UDP) that points to "Unraid2" Setup a static route for all of "Network1" that is routed through "Unraid2". Setup a second static route for "VPN Tunnel" that also is routed through "Unraid2". Hopefully at this point your tunnels will connect and devices on one network will be able to reach devices on the other network (by IP address at least, probably not by name) Troubleshooting this will be tough, there is a lot of room for error. I don't have a lot of advice here, just double check that you are using the right values for Unraid1 vs Unraid2 and Network1 vs Network2, etc.
    1 point
  3. More info on TPM and Windows 11 for 6.10 :
    1 point
  4. Das heißt? "Heiß" werden die alle, aber solange sie nicht überhitzen, ist ja alles gut und Samsung gehört ja eher zu den kühlen Modellen. Das ist ja auch kein simpler Aufkleber.
    1 point
  5. You mention the script is not really necessary? because i think its breaking my docker permissions. on every reboot i have to reinstall some docker containers for them to work. (nzbhydra2, emby, radarr, jackett for example) i wont have this in the unraid version? Also i see people mentioning a new beta. How can i get in? i kinda need TPM for work and take a piss at the internal it manager who tought 8gb laptops are fast enough laptops. Very important stuff!
    1 point
  6. THANK YOU! It seems like I did configure it correctly!
    1 point
  7. If any bits are changed after the pre-clear, that's correct.
    1 point
  8. Hi, Sorry for the late reply. i just deleted the modprobe amdgpu line from the go file and deleted the go.save. Unfortunately I always have an error after restarting the server when launching your Jellyfin docker. But it does not matter, my CG not decoding the HECV codec, I wait to succeed in buying a 6800xt to replace my GTX1660 that I would put in my server at this time. I think this is the best thing to do Thank you very much for your time
    1 point
  9. FWIW - pre-clearing never works right for me either, always clears again when I add a drive
    1 point
  10. Clear means the partition contains ONLY zeroes. When you formatted the disk, you changed some of those zeroes to ones, undoing the clear status, so Unraid had to put them back to zero before it could add the drive. Think of the disk as a room to hold papers. Formatting adds filing cabinets and alphabetized folios with labeling and blank index cards. The room is no longer empty, but it still doesn't have any of your papers (data) yet. The file system takes up space, but makes it much easier to organize your papers instead of just dropping them on the floor. Unraid parity works with the whole room, not the individual papers, so it doesn't matter whether your file cabinets are old and small ReiserFS, or modern XFS, or fragile BTRFS, Unraid parity can reconstruct it. To add a room, it must be totally empty so anything added can be computed into parity. If you want to add a room with existing contents, even an empty file system, then you have to rebuild parity instead. BTW, the paper filing analogy works for formatting as well. Reformatting doesn't remove the paper, it just resets the index cards to blank entries. The ones and zeroes are still all there, but the addresses and file names are erased.
    1 point
  11. Unraid has a routine that tracks reads and writes to all disks. UD gets its information for reads and writes from that routine. It appears that it may be tracking the reads and writes incorrectly on the disk you removed from the array. I can't say if this disk is being included in the parity calculations. Try one thing. Click on the double arrows on the upper right of the UD GUI to refresh the UD disks and see if it clears it up. If not, I would post this issue as a potential bug in the 6.10.0 forum.
    1 point
  12. wenn du es "automatisch" möchtest dann bleibt nur der Weg, unterschiedliche shares mit den entsprechenden Einstellungen, den solltest du auch wählen bevor wir darüber sprechen "manuell oder per script" das alles zu erledigen ...
    1 point
  13. I think that formatting a disk in UD before adding it to the Array removes the signature. The proper procedure with drive from preclear is to simply put them in the Array, then Unraid knows it is all 0s and it will then propose to format the drive to the appropriate FS. @loady is there a question about format at the bottom of the Main page ? (you can post a screenshot if unsure)
    1 point
  14. Just did the same with 2 data drives. Also formatted in UD as XFS an afterwards added the drives to the array. However the drives cleared again - do not know if this has to do with building parity - afterwards the drives where shown as unmountable but you need to scroll down and tick format. Thatˋs it. The drives then will be formatted again and finally available in the array.
    1 point
  15. Thank you very much for your help. Everything is working. There were multiple problems with my server, first I had a library in the boot/extras that was breaking my user scripts. This prevented the script from mounting the unassigned device. Secondly the licence I had was at the limit of 6 devices, and I needed to upgrade my licence.
    1 point
  16. I figured it out: I had to reboot after naming server in 'Settings -> Identification'. I had the 'Settings -> SMB Settings -> Active Directory Settings' wrong: Here the 'AD short domain name' refers to the 'my' in 'my.domain.name'. Hope this helps if anyone else runs into it.
    1 point
  17. Good catch on the USB Flash. I cleaned it up and rebooted and re-installed the plugin and all is well. Seems there was a duplicate of everything in the config from March.. which was the last time I made big changes so a bad copy command. Thanks for the assistance!
    1 point
  18. Set your tag to linuxserver/unifi-controller:version-6.2.25 and try again after updating to this specific version. P
    1 point
  19. Wanted to bump this just to give a final update after managing to solve the issue, for anyone who might experience something similar in future and google this. The problem WAS the RAM in the end. After my last post, the system unfortunately locked up again after a couple of days and the unmountable disks issue returned. I decided to start again from the beginning, in case one of my original troubleshooting steps had missed something obvious - and since I'd run memtest as one of the very first things, I repeated that again (even though the first time around it had run repeatedly without finding any errors). But this time... so many errors that it halted testing within less than a minute of starting. *Three* of my four sticks of RAM, it turned out, were so badly broken that it's a miracle I was even able to boot. Why didn't anything show up the first time? I haven't the foggiest. But I guess it goes to show the importance of retracing your steps if you end up stuck down a dead end. That memory kit was only a year old, so it's currently wending its way back to Taiwan to be RMA'd - in the meantime I've borrowed a couple of spare sticks from a friend, and my system is back to its stable self. I did have one further strange issue - one of my array drives died while rebuilding parity, with a corrupt XFS filesystem on the emulated disk that just *would not* repair too. Hitting the check button in the GUI gave me an error: "update.php: missing csrf_token". Following troubleshooting steps for this I found elsewhere on the forum (safe mode, closing browser windows/tabs, etc) couldn't fix it, I couldn't fix it via the command line because it was an encrypted disk, and even resorting to a fresh Unraid install on another flash drive (copying only the disk config over from my main flash drive and nothing else, so parity would be carried over) wouldn't work. Very strange error. Only way to fix it was to new config the array and start rebuilding parity again from scratch, and restore that one disk's contents (again) from backups. Assuming no more drives fail, I'm home and dry. Phew.
    1 point
  20. I have created a new docker template for Octoprint using the official docker images and supporting webcam streaming. You need video drivers installed on unRaid for the kernel to see a camera. (on Version: 6.10.0-rc1) - install DVB Drivers in Community Apps and select LibreELEC This will need a reboot after installation plug in your camera, you should see /dev/video0 appear in a terminal session on unRaid Install OctoPrint-Spants add the following: variables: ENABLE_MJPG_STREAMER true CAMERA_DEV /dev/video0 MJPG_STREAMER_INPUT -y -n -r 640x480 (can change to suit) port: webcam container port 80 host port 5003 snapshot container port 8080 host port 5004 In octoprint's webcam settings set the stream url to http://IPADDRESS:5003/webcam/?action=stream and test - it should work set the snapshot url to http://IPADDRESS:5004/?action=snapshot and test IPADDRESS is your unraid server address if you used bridge networking
    1 point
  21. For anyone struggling to convert the MIB output to an OID, I found a way. I use PRTG to monitor snmp and it takes OIDs. It was able to auto-discover most things but not the NET-SNMP-EXTEND-MIB stuff. Not sure if the following has been noted in this thread previously but I couldn't find a coherent method among the posts. snmpwalk on the NET-SNMP-EXTEND-MIB root@BLOOTOO:~# snmpwalk -v 2c localhost -c public NET-SNMP-EXTEND-MIB::nsExtendOutLine NET-SNMP-EXTEND-MIB::nsExtendOutLine."cpumhz".1 = STRING: 3713.766 MHz NET-SNMP-EXTEND-MIB::nsExtendOutLine."meminfo".1 = STRING: MemTotal: 67461050368 NET-SNMP-EXTEND-MIB::nsExtendOutLine."sharefree".1 = STRING: appdata: 286401884160 ... Convert prefix to OID format: root@BLOOTOO:~# snmptranslate -Td NET-SNMP-EXTEND-MIB::nsExtendOutLine. NET-SNMP-EXTEND-MIB::nsExtendOutLine."" nsExtendOutLine OBJECT-TYPE -- FROM NET-SNMP-EXTEND-MIB -- TEXTUAL CONVENTION DisplayString SYNTAX OCTET STRING (0..255) DISPLAY-HINT "255a" MAX-ACCESS read-only STATUS current DESCRIPTION "A single line of output from the extension command." ::= { iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) netSnmp(8072) netSnmpObjects(1) nsExtensions(3) nsExtendObjects(2) nsExtendOutput2Table(4) nsExtendOutput2Entry(1) nsExtendOutLine(2) 0 } Take note of the numbers at the end. 1.3.6.1.4.1.8072.1.3.2.4.1.2. is the OID way of saying NET-SNMP-EXTEND-MIB::nsExtendOutLine. The OID for my appdata share is then: 1.3.6.1.4.1.8072.1.3.2.4.1.2."sharefree".1 PRTG accepts this as an snmpcustomstringsensor In PRTG use the following to extract the numerical portion of the string: What the sensor looks like:
    1 point
  22. ich nutze auch nur noch raw da der Gewinn für mich vernachlässigbar war ... ich meine in etwas so qemu-img convert -f raw -O qcow2 vdisk1.img vdisk1.qcow2 dann natürlich das image wechseln bzw. neue VM erstellen wo auf das image zeigt. das ganze ohne Gewähr und sicher ist sicher, vorher ein backup machen, auch wenn die originale nicht angefasst werden sollte ...
    1 point
  23. In episode 9 of the Uncast, @jonp is joined by @Sycotix, @DiscDuck, and @Hawks from the Ibracorp community. They have been producing great content for the Unraid community since the beginning of 2021 showing users how to get the most out of their servers. We talk about how they got started with Unraid, the value of owning your own data, some of their personal interests, and much more!
    1 point
  24. Hi all, I installed calibre/linuxserver and followed all possible instructions, from Spaceinvader too, but nevertheless when I try to enter the Web GUI I see this: and then there is no session "calibre" in the drop down: My Setup is: Any ideas? Thanks in advance!!!!
    1 point
  25. Someone please help me understand this? What if I don't wanna associate my keys and my home installs with my unraid forum account? I really like my privacy honestly and what is is my home have no business being associated with any cloud or external servers. This is a very slippery slope and I just don't like it. Is there an option to continue be offline just the way I am right now? I just don't want to be part of this new ecosystem unraid is creating. I trust my privacy and I trust no one, I am sorry..... And there’s absolutely no reason why you can’t support both ways of activating / running unraid. I should not be forced to connect with you if I have a valid key. "UPC and My Servers Plugin The most visible new feature is located in the upper right of the webGUI header. We call this the User Profile Component, or UPC. The UPC allows a user to associate their server(s) and license key(s) with their Unraid Community forum account. Starting with this release, it will be necessary for a new user to either sign-in with existing forum credentials or sign-up, creating a new account via the UPC in order to download a Trial key. All key purchases and upgrades are also handled exclusively via the UPC"
    1 point
  26. Yes you can fix that by doing the following 1. download hackintool https://github.com/headkaze/Hackintool/releases/tag/3.4.9 2. Open it and goto peripherals 3. Your nic should be en0 and a virtual intel nic (you can have other nics but you must have en0 which is intel. 4. if your nic is not en0 then run the following in mac terminal then reboot the vm. Then it should be en0 sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist sudo rm /Library/Preferences/SystemConfiguration/preferences.plist 5. You want the nic to say en0 and have a tick where it says built in as in the pic below 6. If it doesnt then you will need to open your opencore configurator goto tools then open the efi partition and open the config.plist file with open core. 7. goto device properties then at the bottom click on the list of pci devices. Find your network adapter and click it. It will add it in as below Now we need to click the plus button on the bottom far right of the screen. It will allow us to add a key Now we need to add the key built-in with the type set as Data and the value as 01 Now whilst here in opencore configurator double check that you do have a system definition defined in platform info. Now save the changes and reboot the vm, check with hackintool that it now has a tick on builtin. Now log into apple services
    1 point
  27. So I had the same issue but the solution made me feel like an absolute idiot....spent a good 20-30 minutes trying to figure this out but eventually got it: 1. Enable advanced config options on your UPS via the on screen display 2. Open configuration options and scroll down until you find ModBus 3. Change ModBus to Enabled. It is disabled by default on all APC UPS units. 4. In unRAID UPS Setting menu, set the "UPS Cable" to USB and set "UPS Type" to ModBus. No additional settings like /dev/tty** are required. It may take a minute or two for the info to load but it will. ***Make sure you use the USB-A to USB-B cable to connect your UPS to the server, not the RJ-45 to USB-A. ModBus does not seem to work with the RJ-45 port on the UPS***
    1 point
  28. You could leave the setting at ”Prefer”. That way if your cache runs out of free space files will start getting written to the array rather than the dockers starting to fail as they run out of room.
    1 point