Mettbrot

Just a quick note. I updated the tvh pack to the latest 4.0.7 version!

I released a new update with the latest and greatest stable TvHeadend version 4.0.6

Hey I moved the rc script to /usr/local/emhttp/plugins/<plugin-name>/scripts/. An update should be available in the plugin manager. In the thread you linked Tom says it is recommended to just use /plugins/<plugin-name>/scripts/ and not the long form like you did in your sleep plugin (where I looked to adapt the location ). Doesn't this apply to rc scripts too? Thanks for the help.

If I find some time tomorrow I will push an update.

I don't know anything about hdhomerun tuners; i have never used them. BUT I know that support has recently been added to tvheadend itsself. This means they should work out of the box. There is a button "discover SAT>IP tuners" in tvheadend maybe you try that As CHBMB said maybe you'll need to configure the adapter first using a windows machine.

Hey everyone, I upgraded tvheadend to the latest stable version 4.0.5

I can imagine one for the future. But tvheadend just branched their repository for the 4.0 version. For the time being, stable and "unstable" are quite the same.

This plugin installs a stable version of tvheadend, a TV streaming backend, on your unRaid machine. It supports DVB-S, DVB-S2, DVB-C, DVB-T, ATSC, IPTV, SAT>IP and HDHomeRun as input sources. Install it via the Plugin Page of unRaid's webGUI: https://raw.githubusercontent.com/Mettbrot/unRAID/master/tvheadend.plg In order to work correctly with an USB or PCI(e) tuner you may attach to your machine, you need to replace the bz* files on your flash drive with the ones provided by CHBMB here. Select your version and then 'libreelec'!. They contain the drivers needed to recognize your hardware. After installation you will find a tvheadend Icon in your settings. There you can see if your tuner has been recognized and installed properly. You should set the config directory to a persistent path (I recommend the cache drive), and finally set your superuser login and password under "advanced configuration". After it started you can reach the tvheadend configuration interface via http://tower:9981 where you use your superuser credentials to login. There is a setting to automatically wake up for recordings, which is explained in detail here. Shoutout to piotrasd and WW for their original work on this plugin and their help - it has come a long way! Please give me feedback on how it works for you. Thank you! Changelog: 2019.08.17a: Update plugin to remove warings on settings page 2019.02.27: Update to TvHeadend 4.2.8, 2018.12.13: Update to TvHeadend 4.2.7, remove conflicting dependency to libssl 2018.04.09: Update to TvHeadend 4.2.6 2018.01.14: add missing packages for 4.2.5 2018.01.04: update to TvHeadend 4.2.5-3 2017.11.06: update to TvHeadend 4.2.4-10 2017.08.02: update to TvHeadend 4.2.3 2017.04.29: updated to TvHeadend 4.2.1 STABLE 2016.05.11: update to TvHeadend 4.1-2409 2016.05.11: update to TvHeadend 4.1 PLEASE BACK UP YOUR DATABASE 2016.03.23: update to TvHeadend 4.0.9 2016.01.15: update to TvHeadend 4.0.8, fix loading of settings, add setting for wakeup script 2015.10.29: update to TvHeadend 4.0.7 2015.10.05: Implement missing policy parts and update to TvHeadend 4.0.6 2015.08.24: Adapt to Unraid 6.1 security policy 2015.06.25: TVheadend version 4.0.5 2015.06.09: Initial version. TVheadend version 4.0.4

Hey everyone, just finished the second preclear cycle on a new drive. Maybe you can take a quick look at the details #2 Feb 28 19:01:25 Server preclear_disk-diff[757]: SMART Attributes Data Structure revision number: 10 Feb 28 19:01:25 Server preclear_disk-diff[757]: Vendor Specific SMART Attributes with Thresholds: Feb 28 19:01:25 Server preclear_disk-diff[757]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Feb 28 19:01:25 Server preclear_disk-diff[757]: 1 Raw_Read_Error_Rate 0x000f 110 099 006 Pre-fail Always - 28073888 Feb 28 19:01:25 Server preclear_disk-diff[757]: 3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 5 Feb 28 19:01:25 Server preclear_disk-diff[757]: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 7 Seek_Error_Rate 0x000f 060 060 030 Pre-fail Always - 1118246 Feb 28 19:01:25 Server preclear_disk-diff[757]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 43 Feb 28 19:01:25 Server preclear_disk-diff[757]: 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 5 Feb 28 19:01:25 Server preclear_disk-diff[757]: 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 0 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2 Feb 28 19:01:25 Server preclear_disk-diff[757]: 190 Airflow_Temperature_Cel 0x0022 064 063 045 Old_age Always - 36 (Min/Max 18/37) Feb 28 19:01:25 Server preclear_disk-diff[757]: 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 3 Feb 28 19:01:25 Server preclear_disk-diff[757]: 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 16 Feb 28 19:01:25 Server preclear_disk-diff[757]: 194 Temperature_Celsius 0x0022 036 040 000 Old_age Always - 36 (0 18 0 0 0) Feb 28 19:01:25 Server preclear_disk-diff[757]: 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 Feb 28 19:01:25 Server preclear_disk-diff[757]: 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 42h+40m+12.024s Feb 28 19:01:25 Server preclear_disk-diff[757]: 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 11721066432 Feb 28 19:01:25 Server preclear_disk-diff[757]: 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 24114452099 Feb 28 19:01:25 Server preclear_disk-diff[757]: Feb 28 19:01:25 Server preclear_disk-diff[757]: SMART Error Log Version: 1 Feb 28 19:01:25 Server preclear_disk-diff[757]: No Errors Logged It seems good to me but what do I know Thanks!

Hey, is it possible to extend the s3_sleep with an option-checkbox to suspend KVM virtual machines (and wait until its asleep) before going to sleep? Thanks

Yes, it has moved from r2 to r3. First thing noticed: "snowy mountain" is gone by default.... I will miss it. Other than that: very nice approach taking this to github!

New drive, ran two cycles, is everything okay? I get that 0 Sectors pending reallocation is good but I am always doubtful about those"pre-fail" values :-P preclear.txt

Hey, here are the results of clearing an 3 TB drive I have been using for a year now. Is everything OK? syslog_3tb.txt

Hi I just cleared my 2TB drive and curious about the results. Is everything OK with it? I only ran one sycle since I've been using it for 4 years without problems... syslog_2tb.txt

This is a new disk, and it appears there was a small region with sectors not correctly initialized. Perhaps there had been an electrical spike that scrambled them? I don't know. But the zeroing phase appears to have had no problems rewriting them, so they are correct now. Why not preclear the disk one more time, to reassure yourself that the disk is fine. I really doubt you will see any further issues with this disk. Ok, i cleared it one more time, I guess everything is allright now? (syslog attached) syslog.txt

I just finished preclearing my 3 TB drive but I am a little concerned because I have been told that 'reallocation' is a bad thing. I attached my syslog, but here is the part that made me thinking: Jan 13 00:15:55 Tower preclear_disk-diff[11408]: ============================================================================ (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: Raw_Read_Error_Rate = 120 117 6 ok 241855832 (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: Spin_Retry_Count = 100 100 97 near_thresh 0 (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: End-to-End_Error = 100 100 99 near_thresh 0 (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: Reported_Uncorrect = 64 100 0 ok 36 (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: Airflow_Temperature_Cel = 64 71 45 near_thresh 36 (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: Temperature_Celsius = 36 29 0 ok 36 (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: No SMART attributes are FAILING_NOW (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: 0 sectors were pending re-allocation before the start of the preclear. (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: 16 sectors were pending re-allocation after pre-read in cycle 1 of 1. (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: 0 sectors are pending re-allocation at the end of the preclear, (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: the number of sectors pending re-allocation did not change. (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: 0 sectors had been re-allocated before the start of the preclear. (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: 0 sectors are re-allocated at the end of the preclear, (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: the number of sectors re-allocated did not change. (Misc) Jan 13 00:15:55 Tower preclear_disk-diff[11408]: ============================================================================ (Misc) syslog.txt

Hi there. I am also getting this message 'waiting for usb subsystem'. I am running in VMware Workstation and have mounted the usb stick as hdd...