• Posts

  • Joined

  • Last visited


  • Gender
  • URL

Recent Profile Visitors

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

Yoshiofthewire's Achievements


Rookie (2/14)



  1. Honestly, I haven't run an unraid server in over a year. And updated the server to 20200225
  2. OK, Trying to update again. I'm push out 20190815beta1, let me know if it breaks things.
  3. OK, I just reverted the change. Let me know if that seems to fix things, then we can look at the update in a week or two
  4. OK, thinking about rolling it back, should I just change the config, or roll the whole thing?
  5. Pushed 20190516beta2. If the new muti-tuner breaks something, please message me and I will revert the change. Info about this update: https://forum.silicondust.com/forum/viewtopic.php?f=119&t=71529 FYI: For the adventuress of you if you aren't also running a Plex Server, here are some tricks. 2 lines have been added to the hdhomerun.conf file. StorageID=UnraidDocker1 RecordStreamsMax=16 The StorageID in the conf file must be specified (and must be unique). I specified this as I was unsure if the server would be able to write to the config file. To limit the number of concurrent recordings set RecordStreamsMax in the conf file. Once this limit is reached another record engine will take over additional concurrent recordings. The default/max is 16. If RecordStreamsMax is set to 0 the server will be used for playback but will not make new recordings.
  6. There are actually 2 different issues here. One is a networking issue with the container. The container is supposed to be in Host Networking Mode. I forget the setting to fix this, but then I haven't used Unraid in some time, so the only changes I have made to the container over the past 2 years has been to update the Record engine by replacing the executable in the Github. Linux Subsystem for Windows for the Win. Side note, the Linux x64 version used by Unraid, also runs on Windows 10 64 bit with Ubuntu installed. .... The Log file error just means that the container isn't seeing that the Record engine is already running, and when it tries to start another one it fails and complains about it. In all honestly, it has always done this, and while I totally admit it is bad form, it shouldn't impact normal operation.
  7. Updated to [20180817] Warning: Windows users may have issues with the firmware update. See https://forum.silicondust.com/forum/viewtopic.php?f=92&t=69228 for the fix.
  8. I'm not sure why that is happening. I haven't run unraid in a while. Updated docker to 20180802beta1 You need to upgrade the firmware on your device.
  9. 20171105beta1 doesn't appear to have an update to the Linux binary or tuner firmware.