Jump to content

Hoopster

Members
  • Content Count

    1589
  • Joined

  • Last visited

  • Days Won

    8

Hoopster last won the day on February 18

Hoopster had the most liked content!

Community Reputation

174 Very Good

1 Follower

About Hoopster

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Utah USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hoopster

    how do i avoid this rsync issue

    @comet424 What he said 😀 That is the issue. known_hosts, when updated (this will only happen in RAM in /root/.ssh) after you answer 'yes' to authenticate the host, needs to be copied to known_hosts on the flash drive (/boot/.../known_hosts) so it survives a reboot.
  2. Hoopster

    how do i avoid this rsync issue

    Sorry for the hit-and-run answer, but, I have to leave for about four hours. I won't have time to look at this until then.
  3. Hoopster

    how do i avoid this rsync issue

    It looks like your known_hosts file does not contain the ip address and authorization key for the destination server as it should. You are prompted to answer the question because it is not already authenticated as a known host. You are running the same rsync backup script I am and a proper known_hosts is what prevents being prompted for the yes/no answer. I assume you have something like this in the 'go' file of both servers? # Copy SSH files back to /root/.ssh folder and set permissions for files mkdir -p /root/.ssh cp /boot/config/ssh/medianas_key /root/.ssh/id_rsa cp /boot/config/ssh/known_hosts /root/.ssh/known_hosts cat /boot/config/ssh/backupnas_key.pub > /root/.ssh/authorized_keys chmod g-rwx,o-rwx -R /root/.ssh
  4. My disks are all XFS and every one of them was spun up when only parity and one data disk should have been involved with large files transfers, backups being written to the array or recording of files via Plex DVR. I was just compiling a report after watching this happen for a few days. I updated my active server from 6.6.6 to RC4 5 days ago and that's when the behavior started. Fortunately, I came across this report first which confirms what I saw. Glad to see it has already been identified and resolved.
  5. Hoopster

    [Support] Linuxserver.io - Plex Media Server

    I agree that a lot of useful information for most docker containers is not necessarily obvious without checking the Docker Hub/Github sites. Fortunately, I learned this long ago (because something was not working as expected and I could not figure out why) and I always check them before or immediately after I install a new container. Most users are just going to install the container with the defaults and perhaps play with a few obvious settings on the container Edit screen. There is a lot of very useful and often necessary information in the readme and other docs on the Docker Hub or Github sites for most containers and I suspect many users never read that. It would not hurt to have that information more easily exposed or at least recommended in the first post. The links are there, but, many users don't know that more than code is available on those sites. The default tag of "latest" on this docker is going to put users on the bleeding edge who may not want to be there. On the other hand, the whole UniFi kerfuffle was caused because some users were upset they could not be on the bleeding edge as soon as they wanted to be. If a docker has multiple repository tags or version variables, perhaps at least that information ought to be in the first post of each container. The popup when installing UniFi-Controller is very informative and is referenced in the first posts for the container. Perhaps other containers need this information presented in a more apparent fashion.
  6. Hoopster

    Sata card

    It's discussed on the first page of this thread with a link to a thread dedicated to this topic. PCIe pins B5 and B6 on the H310 often need to be covered with some Kapton/electrical tape or the card will not boot I had to do the same with my Dell H310.
  7. Hoopster

    LSI 2008 - Cant detect any drives :(

    Didn't realize you were in Denmark. My ancestors emigrated from the Aalborg area of Denmark to the U.S. in the 1860s. I don't speak a lick of Danish, but, I have visited that beautiful country a few times.
  8. Hoopster

    LSI 2008 - Cant detect any drives :(

    I only needed/wanted .5 meter cables as well. I did not want all the extra length inside the case. I found some very good quality .5 meter forward breakout cables on Amazon, but as mentioned, always make sure it specifically says they are forward breakout cables. It is interesting how many just say Mini SAS SFF 8087 to 4 SATA breakout cables (or something like that) and never mention if they are forward or reverse. As you discovered, the difference matters.
  9. Hoopster

    [Support] Linuxserver.io - Unifi-Controller

    All my devices, after being connected in the controller after the container update, entered a disconnected/adopting loop last night and had been there for several hours when I noticed it this morning. I fixed it by connecting via SSH to each device and manually setting the inform host. All devices instantly became connected. Setting the container to host (and back to bridge after the adoption) also seems to work if you are stuck in an adopting loop. That is what I did when I first installed the old container and is certainly the easier way to address the issue.
  10. Well then, you need a larger MB with more PCIe slots or try the garycase suggestion 😀 I have never tried attaching array drives to a USB3 port. Unassigned devices, yes, but never data or caches drives.
  11. Hoopster

    [Support] Linuxserver.io - Plex Media Server

    As I mentioned in a prior post, I also had issues at first after upgrading to 1.15.0.659. Here, in order, is everything I have done to get back to a point of being able to play all media (at least everything I have tried) through all Plex clients. 1 - All versions of Plex up to and including 1.14.1.5488 played all media without issue other than a few problem here and here that were easily solved. I would occasionally have problem with the Plex Windows 10 app. 2 - Upgraded to latest Plex Media Server container from LSIO which contained PMS 1.15.0.659 - All recorded TV shows and most .mkv files would not play in any Plex client. 3 - Downgraded to PMS 1.14.1.5488 and almost all media again was playable in all clients except the Windows 10 app. 4 - After a couple of days, the same issues that I experienced with PMS 1.15.0.659 started happening on 1.14.1.5488 5 - Upgraded again to PMS 1.15.0.659 and most media again played properly, but, again, nothing played on Plex Windows 10 app and there were still issues with some (but not all) .mkv files 6 - I briefly thought about restoring the Plex db from a backup, but, I never did so. 7 - I deleted the Codecs folder from appdata/plex/Library/Application Support/Plex Media Server. As a codec is needed to play a file it is downloaded again by PMS. It looks like most of the codecs I had before have been downloaded again. 8 - Solved the Plex Windows 10 app problem by removing it completely and installing the Plex Media Player for Windows. This works and plays everything and is a better client than the WIndows 10 app. 9 - Currently running Plex 1.15.0.659 with hardware transcoding and a mixture of .mp4 and .mkv files (movies) and .ts files (recorded TV shows). All I have tried to play so far have played, and transcoded if necessary, on all clients. Interestingly, even when no media would play locally, no one who streams remotely from my server was having issues. I saw a couple of them streaming when nothing would play on my devices. They said they had not seen any issues. UPDATE: Many reported Plex transcoder crashes with PMS 1.15.0.659 appear to be with SRT subtitles enabled. I have not tried playing anything with subtitles. I'll have to try that and add the results to this report.
  12. Hoopster

    [Support] Linuxserver.io - Plex Media Server

    Oh, I agree, both add the same info in the same way to the run command. However, there are other posts insisting it did not work in Extra Parameters but did as a Device, so I threw that in there. Likely it was something else that happened that caused it to function again and it was coincidental that it happened after making the change. Perhaps just the act of restarting the docker container did it. I have seen that kick start things in the past.
  13. Hoopster

    [Support] Linuxserver.io - Plex Media Server

    --device=/dev/dri:/dev/dri is in Extra Parameters. I know some say they needed to add it as a Device container mapping. I have always had it in Extra Parameters and it has never failed as far as I know. I am also transcoding in RAM (/tmp)
  14. Another option to consider is upgrading your CPU on your current board. I also have the E3C226D2I board in my backup server. It has a CPU with an iGPU and it works on this board for Plex hardware transcoding. You could upgrade to a Xeon E3-12x5 v4 That would eliminate the need for a PCIe slot for a GPU, unless you need that to pass through a GPU to a VM, gaming, etc. You could then use the 1 PCIe slot on your board for an HBA.
  15. Hoopster

    [Support] Linuxserver.io - Plex Media Server

    This is going to be of no help to you in resolving your issue, but, I am using Plex in a docker (LSIO container) My PMS version is the latest 1.15.0.659 Hardware transcoding is setup in the container and is working - I tested 3 video and forced a transcode - all showed (hw)/(hw) decode and encode Every video I played was an MKV produced with either MakeMKV docker or Handbrake docker (also using the QSV hardware transcode function)