[mythtv-users] Suddenly 0byte recordings

[Mark Perkins]

> On 4 Mar 2015, at 11:55 pm, "James Linder" <jam at tigger.ws> wrote:
> 
> 
>>> On 4 Mar 2015, at 8:00 pm, mythtv-users-request at mythtv.org wrote:
>>> 
>>> Over ages I???ve occasionally had 0 byte recordings, suddenly I???m getting a truckload.
>>> 
>>> I???ve a haupuge USB dual card. I replugged it - no change
>>> During a zero byte recording I stop mythbackend then start it - normal recording
>>> 
>>> The log shows:
>>> 2015-03-03 18:37:00.812140 I [13786/13786] CoreContext scheduler.cpp:705 (UpdateRecStatus) - Updatin
>>> g status for Mythbusters on cardid 1 (Tuning => Recorder Failed)
>>> 2015-03-03 18:37:00.925860 I [13786/13836] Scheduler scheduler.cpp:2140 (HandleReschedule) - Resched
>>> ule requested for CHECK -9 7 0 UpdateRecStatus2 | Mythbusters |  | Can a ninja slap a bullet out of
>>> the air? Can drivers who hold the steering wheel in the 10-2 position, have their thumbs ripped off
>>> by an airbag? Can an RFID tag explode if placed inside an MRI? |
>>> 
>>> I would think ???OK the dongle is broken??? except other channels *do* record and restarting backend ???fixes??? the issue.
>>> I???m using
>>> fixes/0.27 [v0.27.4-27-g40506c2]
>>> which I???ve been using since it came out.
>>> 
>>> Can anyone suggest where I might look?
>>> 
>>> top - 10:28:45 up 20 days, 20:16,  5 users,  load average: 1.00, 1.01, 1.05
>>> Tasks: 208 total,   1 running, 207 sleeping,   0 stopped,   0 zombie
>>> %Cpu(s):  0.2 us,  0.1 sy,  0.0 ni, 99.7 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
>>> KiB Mem:   3980628 total,  3837272 used,   143356 free,    85952 buffers
>>> KiB Swap:  4193276 total,   393096 used,  3800180 free.  2800716 cached Mem
>>> 
>>> [poohcorner] /store/mythlogs [331]% who
>>> jam      :0           2015-02-11 14:12 (console)
>>> jam      pts/0        2015-02-24 18:28 (:0.0)
>>> jam      pts/1        2015-03-03 21:55 (haycorn.home)
>>> jam      pts/2        2015-02-24 18:56 (:0.0)
>>> jam      pts/3        2015-03-04 10:15 (haycorn.home)
>>> 
>>> [poohcorner] /store/mythlogs [332]% df
>>> Filesystem     1K-blocks      Used Available Use% Mounted on
>>> /dev/sda2       20510716   7515816  11929944  39% /
>>> devtmpfs         1982424         8   1982416   1% /dev
>>> tmpfs            1990312         0   1990312   0% /dev/shm
>>> tmpfs            1990312      2272   1988040   1% /run
>>> tmpfs            1990312         0   1990312   0% /sys/fs/cgroup
>>> /dev/sda1         103202      4848     98354   5% /boot/efi
>>> /dev/sda6      909101360 577598164 331503196  64% /store
>>> /dev/sda3       20510716     44992  19400768   1% /other
>>> /dev/sda4       20510716   4513288  14932472  24% /home
>>> 
>>> Nothing looks dreadfully amiss
>> If "other channels" - by which I assume you mean using the same device - record 
>> successfully, then it looks as if that channel has moved. Try rescanning.
> 
> Hika thanks, but a 3 month old dongle in a 3 month old NUC means power supply issues are possible, but not likely.
> Mike the fact that stop then start fixes the issue for hours or 10s hours says channel moved is not an issue.
> Definitly *something* is wrong so I wont discount any suggestion.
> Is any of the debug logging likely to show anything?
> Thanks
> James
> 
> 
> _______________________________________________
Is it in a USB3 port? Try temporarily disabling USB3 in bios as a test. Just a guess.