Jump to content

Living Legend

  • Content Count

  • Joined

  • Last visited

Community Reputation

13 Good

About Living Legend

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

994 profile views
  1. Thanks for the breakdown. I'm going to keep playing around with Emby and see where it takes me. I'm running a dual E5-2670 CPU setup along with 64GB RAM so fortunately backend transcoding works pretty well. Before the Fire Sticks 4k, I was most recently running a couple VMs of LibreELEC off this server for my client devices, and then using a basic graphics card to output the video. Have used everything from the original RPi, to RPi 3, and Chromebox. The reason I've been on the sticks recently is for the native Netflix App as this has always been a bit of a hassle to get to work (and continue working) on Kodi.
  2. TLDR: I've been a Kodi (local, synchronized databases), Plex (remote) user for my media for almost a decade until recently when most of my devices are now Fire TV Sticks (4k) because Netflix gets a high usage. Plex has been used for local media on the sticks for some reason. Finally loaded Kodi to a stick and then read about Emby maintaining the library rather than using the Kodi-Headless docker or running a Kodi VM again. Didn't know anything about Emby until reading about it today. Curious as to why people use Emby, what it has replaced, and how it integrates into their media setup. ****************************************************************** I have always seen Emby in the app section, but never looked through it's uses until very recently. I was a long time Kodi user for close to a decade. My set up until recently was all Kodi devices throughout the house with a synchronized database. One of the clients was a VM which was on 24/7, so library updates were pushed to this device. I had issues in the past with the Kodi Headless Docker not updating movies because of a scraping issue, so directing to the VM was a fine solution. In the past year, with the increase in Netflix usage and the accumulation of a few FireTV (4k) sticks, 95% of media is being consumed through Netflix/Plex. I cut the cord with FiOS TV completely and sold my HDHR. No long recording through MythTV was another reason my Kodi usage was no longer a high priority. With that said, I had some time today so I looked into side loading Kodi onto the Fire Stick. I was toying around with the headless Kodi docker again since I no longer use the Kodi VM, and read a post about how the Linuxserver.io guys were mostly on Emby these days as it related to Kodi. Wasn't sure what that meant so I dug a bit further and it appears people use Emby as the backend server that gets updated with media. This data can be pulled with the Emby/Kodi add on, and run natively on Kodi clients. Seems useful. So now I'm juggling between a Emby backend where I'm only using it to monitor my library, Kodi front ends to display my media library, and Plex for people when outside of the household to connect to the library. Mostly curious here, but what are the primary use purposes people have for Emby as it relates to Kodi and Plex? I know this is certainly a use case dependent thing, but have there been any types of prevailing opinions on the most efficient ways of handling media libraries running to many clients locally and remotely?
  3. Interesting, because while I did ultimately buy another quad port NIC for cheap on eBay, I'm now fairy certain that I could have managed without one. When I installed the additional NIC, I now had 8 ports, all with the same ID, so my problem still existed. I followed this thread to resolve: This method allows the user the select specific PCI numbers to pass through rather than device IDs. Then these specific PCI #s can be utilized in the VM by manually editing the VM XML file.
  4. Ah, I see. I have had the issue in the past where it continues to grow. which was why I ballooned it to 50G. I cleared out a few old unused dockers and reset a few mappings to try and resolve the issues. It looks like I may have partially resolved the issue though since I"m currently sitting under 20G
  5. Yes, you're definitely right. I have many many dockers and there has to be at least one or two that are storing some sort of file inside the container and making them grow. Haven't found a simple way to solve his one yet. This shows it should be around 20GB. Not sure why zoneminder and HA get so big. Homeassistant database gets large but that's on the array. Zoneminder recordings have their own share. DelugeVPN downloads to different folders within a share. Always been perplexed by this one.
  6. Yes, I have made this mistake. I could not figure out why some of my movies that initially downloaded to cache were not moving out of cache. I'd try to move them manually and then poof, they'd disappear. I wish I could attribute this loss of data to the user error mentioned above, but unfortunately that's not the case here. If the error was on me it'd be easy to move on and learn from my mistake, but the problem is I haven't manually moved files into a disk share in probably over a year. I only add or delete files at my user shares. So I have absolutely no idea how this one random share that I haven't accessed in about a month has all the files names but no data. To me this goes to show the importance of backing up important data outside of the array because every once in a while, even though unRAID is meant to protect your data in the event of drive failure, it may throw out some quirk and gobble up a few files.
  7. Out of curiosity, to attempt to prevent in the future, what can cause something like this? Is this a file corruption issue or potential disk failure issue? If the former, I understand that an actual backup would be the only way to resolve. But if the latter, shouldn't I have had some sort of drive failure notification so that I could attempt to rebuild before I hit the point of no return?
  8. Yeah, that's what I assumed. I assume that there's no basic resolution to this type of issue?
  9. Here are the search results for one of the files: I looked in all three locations. All 3 locations show 0 kb file size. Am I screwed?
  10. Certainly not on purpose. I had an issue last week where my docker files crapped out and I had to rebuild from my appdata backup. Other than that, I made no material changes to anything related to that share.
  11. Here are the settings for the share with the issue:
  12. This is an odd one. I have a bunch of shares set up on my unRAID server. One of them I use to keep track of anything related to projects and maintenance I'd do around the house. Random things like car oil changes, getting the septic pumped, replacing parts on lawn equipment, etc. Today I went into that share to look something up relating to a basement remodel. All of the files were there. But they were all listed at 0KB size. Any .txt file opens, but has nothing inside it. None of the pictures, .doc files, or .xlsx files open. Quite concerning. I went into all the other shares and spot checked and didn't find this issue anywhere else. Any idea what this issue could be, and am I SOL or are there potential ways to remedy this? unraid-diagnostics-20190211-0849.zip
  13. This was my process to start from scratch and recreate the issue: 1. Deleted container/image. 2. Deleted appdata tvheadend folder. 3. Downloaded docker 4. Enter docker WebUI 5. Complete wizard 6. 403 Forbidden on admin 7. Open google incognito instance. 8. 403 Forbidden on user Shown below is a quick gif of the install: - Running uBlock Origin on chrome as an adblocker, but have since tried on internet explorer with same error. - Below is the run command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='tvheadend' --net='bridge' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'PGID'='100' -e 'PUID'='99' -p '9981:9981/tcp' -p '9982:9982/tcp' -v '/mnt/user/appdata/tvheadend':'/config':'rw' -v '/mnt/user/downloads/tvheadend/':'/recordings':'rw' -v '/mnt/user':'/unraid':'rw' 'linuxserver/tvheadend' b34e7739f62a447c88910ffff6603782cb7854bf06bfaabc7b97f057b6a7f3eb The command finished successfully!
  14. I'll screenshot the process in a little bit to make sure that I've explained things appropriately.