jagz707

Silly error.. although the addresses were static, the DHCP server hadn’t excluded the range of the static addresses and I think that was causing an issue. Turned off DHCP and seems to be good now…

So I've set up a linux VM on Unraid and bridged the interface with br0 so I get a real IP address from the DHCP server. The Unraid server IP is static 192.168.66.15 and the VM IP is static 192.168.66.16. Both hosts have entries in my DNS server. When I ping either host from my Windows PC, they respond correctly for their respective IP addresses. However, when I ping the VM from the Unraid host, it responds from its own IP address (.15) instead of .16. When I try it the other way around, pinging from the VM to the Unraid host, the same thing happens. Any ideas?

case

I've started having this problem too after the system crashed due to a kernel panic. However, I was able to restart the array by using the 'play' button you find on the Dashboard screen - above the case icon in the top left, where you also see 'reboot' and 'shutdown' buttons.

Nice one, many thanks

Came across this thread and glad to hear this SAS Expander card worked.. about to go for it but a little confused about the cables I need.. I have an LSI 9300-8i HBA card in my unraid box at the moment which has 2 Mini SAS HD ports (SFF 8643) . Its currently connected to 8 SATA drives using two SFF8643-to-4x-SATA cables. So in order to use the HP 727252-001 SAS Expander card to host 18 HDD's and 5 SSD's, I think I need to order: - Two Internal Mini SAS HD (SFF-8643) to Mini SAS (SFF-8087) [Which I will connect between ports 1 and 2 of my HBA card to ports 1 and 2 of the HP SAS Expander card) https://www.amazon.com/gp/product/B01AOS4U4O/ref=ox_sc_act_image_11?smid=AE2OZG2NN3099&psc=1 - Six Internal Mini SAS SFF8087-to-6x-SATA cables [Which I will connect between ports 3 thru 9 of the HP SAS expander card and the drives https://www.amazon.com/gp/product/B088GL3NS2/ref=ox_sc_act_title_3?smid=A1IR1GJH6XB88L&psc=1 My case is a Fractal Meshify XL2 using an MSI Z590 motherboard. I dont have any backplanes and would like to connect the drives directly to the SAS expander card. I was all set to order the above until I started reading about SFF8087-SATA *REVERSE* Cables and became a bit confused. Would really appreciate some pointers!

The following is just quick notes on how to setup Traktarr on unraid to integrate with existing media management tools like radarr. It has been tested using instructions found at the Traktarr Dockerhub and Github pages: https://hub.docker.com/r/eafxx/traktarr https://github.com/l3uddz/traktarr#2-create-a-trakt-application Goto Apps tab on Unraid and search for Traktarr Click Install - accept defaults in config page, then click Apply While its installing, open another browser window and visit https://trakt.tv Sign up for an account (or skip this step if you already have one) Click on the following link to create a new trakt app: https://trakt.tv/oauth/applications/new If prompted to login, do so and then you should arrive at the ‘Create a Trakt API’ page Give a name to the new app, for example 'Traktarr' Give a description in the description box if you want like ‘Traktarr for automated downloads’ In the ‘Redirect uri’ box, type: 'urn:ietf:wg:oauth:2.0:oob' Click Save App and you will be presented with app ClientID and Client Secret - make a note of these The traktarr docker you installed on Unraid should be up and running by now. From the docker page, left click on the traktarr docker and start it if it isn’t already running Left click and select 'Console' and perform the following commands in the console terminal cd /config vi config.json The configuration file for Tracktarr will open. (This is the default configuration page that ships with Traktarr and is configured for automated downloads - more complex configurations can be found on the Traktarr github page , if you want them.) Goto the bottom of the page and enter the Client ID and Client Secret details like shown below: "trakt": { "client_id": "af55948dgk3049afb7cb3r9584393622064148f65be0f54533364a5c8014d042", "client_secret": "210wqkkto4324402a43393999e4ffkr49583ab29e0b84f7d5514884169eb98" While you have the file open, enter the API key for your Radarr and Sonarr instances, which you can find in ‘Settings’ > ‘General’ of the respective GUI’s. Also enter the quality profile you want and the root folder where Radarr stores your content For example: "radarr": { "api_key": "rt594dyyo4059gvlgk455959gvkfl2wwj49", "minimum_availability": "released", "quality": "HD-1080", (make sure you put an existing quality profile you want traktarr to use) "root_folder": "/plexdata/media/movies/", (make sure you put the correct path to your media here) "url": "http://unraid:7878/" (make sure you put the correct hostname or IP of your Unraid server here} Do the same for Sonarr if you want to use traktarr for TV shows as well. (If you do not want TV content and are only interested in movies, then near the top of the file, under ‘shows’, switch the ‘interval’ value to 0 Check the other aspects of the file and make sure they reflect your preferences. For example the blacklisted minimum and maximum years etc. Once ready, save the file (on vi, you do this by typing :wq) Run the following command in console terminal: traktarr trakt_authentication Traktarr will connect to trakt and wait for you to activate the connection. The console will display an activation code, (as shown below) make a note of this: __ /________ | | / |___ _______| | _ __ __ \ | |/ /\ _ \ __ _ __ | | | | // __ | < | | / __ | | /| | /|| || ( /| \ || ( /| ||/ / / ######################################################################### Author: l3uddz URL: -- Part of the Cloudbox project: ######################################################################### GNU General Public License v3.0 ######################################################################### 2021-10-02 03:54:36,822 - INFO - media.trakt - __oauth_request_device_code - We're talking to Trakt to get your verification code. Please wait a moment...{'Content-Type': 'application/json', 'trakt-api-version': '2', 'trakt-api-key': 'dc73c189d540afb7cb3b9b1b6a3c7622064148f65be0f54533364a5c8014d042'}2021-10-02 03:54:38,385 - INFO - media.trakt - __oauth_request_device_code - Go to: https://trakt.tv/activate on any device and enter W69XDR75. We'll be polling Trakt every 5 seconds for a reply The console will now wait for you to activate the authentication request youve sent. Visit the following link to activate: https://trakt.tv/activate - enter the code you obtained from the console. Click ‘Yes’ to allow tracktarr to use your account. The track.tv UI should tell you that tracktarr has been added. This will also be confirmed on the console, with the console no longer waiting for you to activate. Restart traktarr using the docker page on Unraid. Then left click on traktarr and click logs Make sure there are no errors reported in the log and check at the botom of the log when the next run is scheduled. If the next scheduled run is more than a minute or two away, run tracktarr manually for an initial run by opening the console for traktarr from the Unraid docker page and entering the following command: traktarr run --run-now Traktarr should fire up and start loading radarr with content to download (make sure radarr is configured to use a download client to connect and download content) Check the Activity Queue in Radarr to see items being added to radarr by traktarr. Check your download clients (NZBGET, qBitTorrent, etc) to see if items are being added. Check again at the next scheduled run time to see if anything new has been added. The above should not be used to download copyrighted content.

Thanks very much for this - not sure why I didn't try SATA! The info about not needing plopKexec was useful to - followed the HowTo and it worked fine!

Lots of great Howto's on how to run Unraid as a VM in ESXi, but they all seem to be based on passing through an HBA card to the VM. My use case is to build a small Unraid VM on my ESXi server to use for testing purposes only. (My Production Unraid host is a a dedicated server). For that, I just want to use ESXi storage from my datastore rather than put an HBA card in with its own disks.. I set up a vm with a few virtual disks based on Ubuntu32 and used PlopKexec to boot off the USB stick I had passed through in vmware. Everything boots up fine, but when I login into the Unraid UI and look at the MAIN page none of the virtual disks I provisioned in Esxi appear as devices to Unraid.. I've tried using different SCSI controllers like LSI SAS, Vmware Paravirtual, Buslogic etc as the emulation in ESXi but no joy. Also tried adding disks as SCSI thick provisioned as well as IDE but same result. Also tried changing the disk type from 'dependent' to 'indepedent' but that didnt have any effect or the VM didnt boot. I reduced the disks down to just 1 disk just to see if that made any difference as well.. it didn't.. And just for good measure, tried also to play about with the SCSI bus sharing options between physical, virtual and none.. but no joy there either.. I must be missing something obvious here.. Any help appreciated..

In case its of any help to anyone.. Migrating PLEX MEDIA SERVER from a FreeNAS Jail to Unraid Docker 1. In the Plex webUI, open the settings and uncheck ‘empty trash after each rescan’. Then save. 2. On the FreeNAS shell, locate your Plex Media Server Jail and its plex related data. In my case, my jail is called ‘plex-plexpass’ and my iocages live on a pool called ‘MEDIA’. Using a terminal shell on the FreeNAS host: root@freenas# cd /mnt/MEDIA/iocage/jails/plex-plexpass/root root@freenas# ls -lrt 3. The ‘Plex Media Server’ directory contains all the Plex config data and database files. This needs to be tarred up before being transferred to the Unraid server. root@freenas# tar -cvf PlexMediaServer_backup.tar “Plex Media Server” 4. Once the Plex directory has been tarred up using the above command, we use rsync to transfer it to the Unraid server. My Unraid server is called ‘unraid’ and the location I will store it in is called ‘backuptars’. Note that I have a local DNS that resolves ‘unraid’ to its IP address. If you don’t have one, use the IP address of your server. Note also that I use the root account on both FreeNAS and Unraid. If you use other accounts, make sure you substitute these for ‘root’ used in this how-to… root@freenas# rsync -auP PlexMediaServer_backup.tar root@unraid:/mnt/disk1/data_migrate/backuptars 5. We also need to decide where the media itself is going to be stored. Assuming this is also going to be moving to Unraid, we need to make sure this too has been shipped from FreeNAS to Unraid. We can use the same rsync command to move the Media directory. The below command assumes our media is stored in a directory called ‘plexmedia’ and that this will be moved to a share called ‘plexmedia’ on Unraid. root@freenas# rsync -auP plexmedia root@unraid:/mnt/disk2/plexmedia/ 6. Next we need to setup a Docker container on Unraid that will be our new Plex media server. I used the ‘Community Applications’ plugin by Andrew Zawadzki to make this easy. 7. From the Plugins section in Unraid, just add the Community Applications plug-in like this: 8. The URL to use is: https://raw.githubusercontent.com/Squidly271/community.applications/master/plugins/community.applications.plg For more information, please see the Unraid forum post: https://forums.unraid.net/topic/38582-plug-in-community-applications 9. Once installed and started, you should see the below in the Docker section of Unraid. 10. In order to map the right container paths to where things are stored on the Unraid directory, we need to change the host path as shown, and then save and apply. 11. Notice that /config is mapped to /mnt/user/appdata/binhex-plexpass, as shown below: 12. This is where the new Plex metadata resides. We will need to overwrite this with the data we transferred over from FreeNAS. First stop the container that is running using the UnraidUI – click the STOP ALL button: 13. Using the terminal shell on the Unraid host, go to the location where the plex configuration data resides: root@unraid# cd /mnt/user/appdata/binhex-plexpass 14. We need to rename the existing Plex Media Server Directory that is already here. root@unraid# mv "Plex Media Server" pms.old 15. Now we need to move our FreeNas Plex configuration (that we transferred from FreeNAS previously to the ‘backuptars’ directory) to take the place of the Plex Media Server directory we just renamed. NB. The reason why we move it here instead of maybe just changing the volume mapping of the docker container, is that future updates of plex may expect certain things to be in certain places… it may well work, but I didn’t want to risk it... root@unraid# mv /mnt/disk1/data_migrate/backuptars/PlexMediaServer_backup.tar . 16. And then we need to untar the file so that we have the Plex Media Directory recreated. root@unraid# tar -xvf PlexMediaServer_backup.tar 17. And then adjust file and directory ownerships: root@unraid# chown -R nobody:users "Plex Media Server" 18. Now start the Unraid Plex Docker container by clicking the START ALL button: 19. Wait a couple of minutes foe Plex to come up and settle, and then using a web browser, browse to the new Plex instance – for me the URL is http://unraid:32400/web 20. Once logged in, the plex library should be visible. However, when trying to play a video, the following error may be seen: 21. This is because the path to the media (as known to Plex from your old instance on FreeNAS) has changed and Plex can no longer find the actual media file to serve. I thought this could be fixed with putting in some symlinks, but this didn’t work for me. So, I just manually mapped my media directories in the PlexUI like this: 22. Press the BROWSE button and browse to the location of your media – for example, for my TV media, it was /mnt/media/TV 23. Plex will rescan the library (which may take a while to complete) and the media should now play. Remember to do the same for all your other media folders, Movies, Documentaries, etc. 24. Finally, re-enable the ‘Empty trash automatically’ feature in SETTINGS>LIBRARY in the Plex webUI and click SAVE CHANGES. PLEX Media Server has now been successfully migrated from FreeNAS iocage Jail to a Unraid Docker Container. 25. Now that everything is up and running, we can delete the ‘pms.old’ directory which we renamed the original Unraid Docker Plex configuration directory to, and also the PlexMediaServer_backup.tar file that we transferred from the FreeNAS server. We use the terminal shell like this: root@unraid# cd /mnt/user/appdata/binhex-plexpass root@unraid# rm -Rf pms.old root@unraid# rm -Rf pms.old root@unraid# rm PlexMediaServer_backup.tar //** There’s probably a better way of doing it that avoids having to rescan your media, but this is what worked for me.. //**