Broken Repeat Recording

How would I identify a rogue recording?
I've done it by binary sieve (divide and conquer) - move half the recordings into My Music (where they don't get indexed) and see if that improves things; if not the rogue one must be in the other half... and so on.

However, I reckon in your case you have worse problems which may account for it. Tried a disk check lately?
 
Thought I'd come back to this thread rather than start a new one.

On average, once a month my T2 is non-responsive to the remote and doesn't record the schedule.

Could it possibly have anything to do with having BBC Red Button FreeView 250 as its default channel?

Disk Check Result

I wasn't sure which code would present the data in the most readable form.

Any tips gratefully received.

Code:
SMART Status    PASSED   
Device Model     ST1000VM002-1ET162
Serial Number     S5146EYW
LU WWN Device Id     5 000c50 08c3c66c7
Firmware Version     SC11
User Capacity     1,000,204,886,016 bytes [1.00 TB]
Sector Sizes     512 bytes logical, 4096 bytes physical
Rotation Rate     5900 rpm
ATA Version is     ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is     SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is     Wed Sep 11 09:49:35 2019 BST
SMART support is     Available - device has SMART capability.
SMART support is     Enabled

ID     Name     Flags     Raw Value     Value     Worst     Threshold     Life Left     Notes
1     Raw_Read_Error_Rate     POSR--     16033632     108     099     006         -
3     Spin_Up_Time     PO----     0     097     097     000         -
4     Start_Stop_Count     -O--CK     5444     095     095     020     94%     -
5     Reallocated_Sector_Ct     PO--CK     0     100     100     010     100%     -
7     Seek_Error_Rate     POSR--     416573683     086     060     030         -
9     Power_On_Hours     -O--CK     22401     075     075     000     75%     -
10     Spin_Retry_Count     PO--C-     0     100     100     097     100%     -
12     Power_Cycle_Count     -O--CK     5444     095     095     020     94%     -
184     End-to-End_Error     -O--CK     0     100     100     099         -
187     Reported_Uncorrect     -O--CK     0     100     100     000         -
188     Command_Timeout     -O--CK     0     100     100     000         -
189     High_Fly_Writes     -O-RCK     207     001     001     000         -
190     Airflow_Temperature_Cel     -O---K     49     051 (49°C)     041 (59°C)     045 (55°C)         In_the_past
191     G-Sense_Error_Rate     -O--CK     0     100     100     000         -
192     Power-Off_Retract_Count     -O--CK     5443     098     098     000     98%     -
193     Load_Cycle_Count     -O--CK     5446     098     098     000     98%     -
194     Temperature_Celsius     -O---K     49     049     059     000         -
197     Current_Pending_Sector     -O--C-     0     100     100     000         -
198     Offline_Uncorrectable     ----C-     0     100     100     000         -
199     UDMA_CRC_Error_Count     -OSRCK     0     200     200     000         -
 
To actually address the post
On average, once a month my T2 is non-responsive to the remote and doesn't record the schedule.

Could it possibly have anything to do with having BBC Red Button FreeView 250 as its default channel?
Unlikely, Random hangs are an unfortunate fact of life

Using a simple timeswitch to force a daily reboot while away from home is a precaution against loosing more than a days worth of recordings
 
You're right.

The title isn't relevant to my new issue.

Apologies.

@MymsMan - Thanks for the advice. I shall probably hard reboot it once a week to try to forestall frequent freezes.
 
I shall probably hard reboot it once a week to try to forestall frequent freezes.
There is no clear evidence that rebooting forestalls freezes, it could freeze shortly after a reboot.
A timer switch reboot is a means of minimizing the impact of a freeze on unattended recordings
 
Back
Top