tazire

Just curious if i have this done right. I have an SSD mounted with UD to specifically be used with plex as a transcoder drive. I then have a container path in plex pointing to the mounted drive. theoretically is this all i need to do to make the drive available in my docker? Just having a bit of trouble getting it to work how i want it. I'll go to the plex docker support if i at least have this much done right.

yea i did look into it alright. I have 16gb which tbh I doubt is enough. although im not sure how much would be required for transcoding.... I imagine ill upgrade to ryzen in the future and take this route but atm im prob just gonna have to go with the above plan.

Basically at present I run my plex media server and torrents fully off my cache. As a result I have massive writes to the drive. I dont want my cache to burn out too quickly if I can help it. I am toying with the idea of putting another unassigned SSD into my unraid server for just transcodes from plex and possibly another one for my torrents. Before I plow ahead with this plan I'm just curious if anyone else has better solutions to this issue?

I have just started to venture into 4k content. I made a separate library which is only available to me so no worries about others trying to transcode the 4k content. I am only slowly adding 4k of content I really like. 4k hdr in a nice high bitrate is a serious hog on space!

No need right after this i went and double checked the https port for unraid and i dunno what i had done before but the assigned port never took and defaulted back to 443. i reassigned it and all is back to normal for now. I will be trying to set up the reverse proxy again soon now that ive been reminded.

You're right im not. I was having issues getting it up and running correctly for me. I got it going with the intention of getting back to it. I just havent sat down to do it yet. I changed my unraid port for https but nextcloud still wont start...

I have done as stated above with the port change but now i have to specify the port when i want to connect to the nextcloud. essentially where xxx.duckdns.org used to work to connect I now have to put in xxx.duckdns.org:12345 in order to connect to the nextcloud... I'm guessing this isnt actually a nextcloud issue and something I can fix with my duckdns?

just a quick question.... i currently run my plex docker completely from my cache drive. As i understand this can cause high disk usage when all the meta data/ transcoding etc is done on the cache drive. I have read into the whole ram disk option but with 16gb I'm not sure i have the capacity for that to be viable. Would it be recommended to install another ssd as an unassigned device to run solely my plex meta data and transcoding to lower the load on my cache drive? I have 2 fairly new 1tb evos installed as the cache drives so i have no immediate concerns but i wouldnt like to burn them out with over use if i can help it.

Thats exactly what I have. I didnt realise this card didnt need to be connected what so ever. I had read that it needed to be connected for power reasons! obviously not. Thats spot on. Ill get on connecting this up tomorrow now. Thanks again.

The H97 should be UEFI, but I cant check right now. The toolset used for the Dell H310 has the necessary files for an EFI boot. Cant post a link as I'm on my mobile only. Thanks very much for this. The toolset had everything i needed. I didnt do it exactly as the read me said as I already had certain parts of the process completed in dos but its all up and running again. Just one last question... and i think i already know the answer to this one... I have an intel sas expander card.... it connects to a full pci e slot from what i can see... but im told this is just for power draw.. not a hope of this ever working in a pci slot im guessing??? Im fairly sure im gonna need a new mobo to accommodate it.

Is your BIOS up-to-date? It 100% is on the z87-k I even updated it after trying to load into the shell a few times. but its an old board and the latest bios is still old... The gigabyte board though doesnt appear to have a boot to efi shell on it. but it does have an override boot as you suggested earlier but i havent ever seen it populated. Its a cheap enough board... h97m-d3h or something i think. I havent updated that bios yet. not that it makes an awful lot of difference for the flash but the gigabyte board is the mobo on my server. I may just make the usb again... keep it as simple as i can with no other files other than the efi shell until i actually manage to get into the efi... I have followed a number of different how to's on this at this stage though.

This could be my issue but I set up my usb drive as a boot device using rufus. I have shellx64.efi then placed on the drive. It doesnt seem to appear in the override boot section on the gigabyte modo. On the asus one I just cant get past the secure boot at all... I have it set to other os and states the secure boot is disabled but i still get the secure boot issue. You could be right that I havent got the usb set up right. But on the other hand I have been able to boot into the freedos thats loaded onto it. and i can see all the files using the dir command etc...

Im in the middle of trying to flash my 9240-8i at present and i am having a nightmare trying to get into the efi shell.... its literally impossible.... using an old enough motherboard i guess.... ASUS z87-k. No matter what i do it will tell me i cant load into the efi shell due to secure boot issues... I have this turned off but still get the issue. I also have a gigabyte H97 board but I dont see the efi shell option anywhere. I have tried a few different versions of efi shell to try get it to work and nothing... Anyone got through this or know of another way to flash??

Yea im in the process of doing that as we speak. guess thats likely just the safest way. thanks for the quick reply

as the title states i have just replaced my cache drives and all went well all the files are back as i want them and that. I am having an issue with the docker.img. I had my original one backed up from mnt/cache/ and realised I wasnt sure how to get the file back into that path. Anyway as a way around in the docker settings I changed the path to mnt/user/appdata and pasted my saved docker.img there. When I went to restart my docker.img I got this error. Your existing Docker image file needs to be recreated due to an issue from an earlier beta of unRAID 6. Failure to do so may result in your docker image suffering corruption at a later time. Please do this NOW! My question now is will I be able to move this docker.img to mnt/cache and get all my existing docker installs back or should i start over with my docker.img??

thanks for the responses lads. you are correct. that error has gone since.

ok I did it... although I have just gotten an error. Cache pool BTRFS too many profiles Everything seems to be working fine from what i can tell. although strangely the amount of space taken up by the cache is now half what it was while in raid0... any ideas?

thanks for the reply.

Basically as my title states i am looking to convert my cache storage from raid 0 to raid 1. essentially i have been seeing the odd error creep into one of my ssd's. I have plenty of available space to convert from raid 0 to raid 1. 102gb used out of 720gb (2x120gb & 2x240gb). I have found the commands and just wanted to double check i have it all correct before implementing it and also that all the data should be fine while making this conversion? -dconvert=raid0 -mconvert=raid1 My intention is to eventually buy replacement SSD's (2x500gb samsung 850EVO) to sort out the issues but i just want to stop the cache from being completely unusable before i replace them. Thanks in advance.

having an issue with the update to 11.0.3. on the check for expected files it is finding an unexpected .rnd file and it wont update. I havent tried the old manual way as yet but im just curious if anyone else has experienced this??? EDIT Manual update worked fine.

thanks for that.

Sry i couldnt see your sig so didnt know what you wanted.

Ok let me start again. Up until now i have been using delugeVPN and sonarr with no issues. I didnt have Jackett installed. I wanted to try expand my indexers and just installed jackett. I set up the indexers i wanted to use in jackett and linked it to sonarr as directed. test on sonarr says everything is working. when i search for missing files using sonarr, i opened the logs on jackett and can see that it is searching the indexers and finding the files. I open deluge and nothing was added. I was just reading what other people were doing and I didnt know if jackett outputted its results to the /download container path and then if i should set deluge to auto download the jackett outputs from that path. bypassing sonarr if that makes sense??

Sonarr works fine and deluge will dl everything it gets through other indexers just not through jackett indexers

Just looking for a bit of help with the setup on this. I have it installed and working with sonarr in the sense that the logs show the searches and results etc. Just it doesnt appear to be sending the results to deluge. From what i can see the results dont go anywhere. Should the folder i have set as downloads be filling up with these resulting torrents? also i have deluge set to monitor that folder. I've attached my setup. log.txt