Recording and remote viewing issues

Don’t know if this is related to the latest Shield firmware update or not but recently seems like recordings are failing and remote viewing via the web or the iphone app fails. When the remote viewing fails I keep seeing that the HDHRun Prime buffer is full, see snippet from DVR log below.

The only things I have done in the past week are to update the Shield firmware and update the DVR app running on the Shield via the Google Play store. I have made no other changes to my network setup, AppleTV, etc.

2017/10/31 07:39:16 [TNR] Opened connection to 131A0091 for ch1002
2017/10/31 07:39:17 [HLS] Starting transcoder for channel 1002 (encoder=h264_mediacodecndk, resolution=480, deinterlacer=linear, bitrate=2000)
av_interleaved_write_frame(): No such file or directory
Last message repeated 1 times
Error writing trailer of /storage/3A70D09670D059E9/NVIDIA_SHIELD/Streaming/ANY-ch1002/stream.m3u8: No such file or directory
2017/10/31 07:39:33 [WRN] Buffer for 131A0091 ch1002 is more than 50% full (clients=1, len=16777684)
2017/10/31 07:39:40 [WRN] Buffer for 131A0091 ch1002 is more than 75% full (clients=1, len=25165868)
2017/10/31 07:39:45 [WRN] Buffer for 131A0091 ch1002 is more than 95% full (clients=1, len=31877468)
2017/10/31 07:39:46 [WRN] Buffer for 131A0091 ch1002 is more than 99% full (clients=1, len=33219788)
2017/10/31 07:39:52 [HLS] Stopping transcoder session ANY-ch1002 @ 4.396066s
2017/10/31 07:39:52 [TNR] Closed connection to 131A0091 for ch1002
2017/10/31 07:47:52 [TNR] Opened connection to 131A0091 for ch1002
2017/10/31 07:47:52 [HLS] Starting transcoder for channel 1002 (encoder=h264_mediacodecndk, resolution=720, deinterlacer=linear, bitrate=6000)

The error messages sound like your DVR drive is not attached, running out of space or that it’s name changed.

I will check the connection when I get home but that would surprise me as the Shield and the USB drive are in a cabinet and have not been moved for weeks.

The drive is defiantly not out of space, showing 2.5 GB available.

How would the drive name get changed and how would I know?

Try playing existing recordings to see if they work.

Also try use a file explorer app, or go to x.x.x.x:8089/restore to navigate around the filesystem to see if the /storage/3A70D09670D059E9 is still valid.

Existing recordings won’t play, went to x.x.x.x:8089/restore and /storage/3A70D09670D059E9 appears to still be valid, meaning I can see folders and navigate to them although response seems to be slow.

I tried copying a recording made this morning from the USB drive to my Mac via wifi to see if I could play the file from my computer once it copied over and got this error: The operation can’t be completed because an unexpected error occurred (error code -8084).

What next?

And here’s the error log from this evening when I got home and tried to play recordings via the web interface on my computer:

2017/10/31 17:16:32 [ERR] Failed to read directory /storage/emulated: open /storage/emulated: permission denied
2017/10/31 17:17:36 [HLS] Starting transcoder for file-148 at 0s (encoder=h264_mediacodecndk, resolution=360, deinterlacer=linear, bitrate=720)
2017/10/31 17:17:36 [HLS] Stopping transcoder session file-148 @ 0s
2017/10/31 17:18:12 [HLS] Starting transcoder for file-147 at 0s (encoder=h264_mediacodecndk, resolution=360, deinterlacer=linear, bitrate=720)
2017/10/31 17:18:12 [HLS] Stopping transcoder for file-147 after seek to 3m13s (out=0s, finished=false)
2017/10/31 17:18:12 [HLS] Stopping transcoder for file-147 after seek to 3m13s (out=0s, finished=false)
2017/10/31 17:18:12 [HLS] Stopping transcoder for file-147 after seek to 3m13s (out=0s, finished=false)
2017/10/31 17:18:45 [HLS] Starting transcoder for file-147 at 3m13s (encoder=h264_mediacodecndk, resolution=360, deinterlacer=linear, bitrate=720)
2017/10/31 17:18:45 [HLS] Starting transcoder for file-147 at 3m13s (encoder=h264_mediacodecndk, resolution=360, deinterlacer=linear, bitrate=720)
2017/10/31 17:18:54 [HLS] Starting transcoder for file-147 at 3m13s (encoder=h264_mediacodecndk, resolution=360, deinterlacer=linear, bitrate=720)
[mpegts @ 0x203f45f600] Dropped corrupted packet (stream = 1)
[mpegts @ 0x203f45f600] Dropped corrupted packet (stream = 2)
[mpegts @ 0x201f85f600] Dropped corrupted packet (stream = 1)
[mpegts @ 0x201f85f600] Dropped corrupted packet (stream = 2)
2017/10/31 17:19:34 [HLS] Stopping transcoder for file-147 after seek to 3m18s (out=0s, finished=false)
[mpegts @ 0x203f45f600] read_timestamp() failed in the middle
/storage/3A70D09670D059E9/NVIDIA_SHIELD/TV/Good Morning Nashville on News 2/Good Morning Nashville on News 2 2016-11-20 2017-10-31-0559.mpg: could not seek to position 6223.080
/storage/3A70D09670D059E9/NVIDIA_SHIELD/TV/Good Morning Nashville on News 2/Good Morning Nashville on News 2 2016-11-20 2017-10-31-0559.mpg: I/O error
Finishing stream 0:0 without any data written to it.
Finishing stream 0:1 without any data written to it.
[mpegts @ 0x201f85f600] read_timestamp() failed in the middle
/storage/3A70D09670D059E9/NVIDIA_SHIELD/TV/Good Morning Nashville on News 2/Good Morning Nashville on News 2 2016-11-20 2017-10-31-0559.mpg: could not seek to position 6223.080
/storage/3A70D09670D059E9/NVIDIA_SHIELD/TV/Good Morning Nashville on News 2/Good Morning Nashville on News 2 2016-11-20 2017-10-31-0559.mpg: I/O error
Finishing stream 0:0 without any data written to it.
Finishing stream 0:1 without any data written to it.
[hls @ 0x201f85fc00] failed to rename file /storage/3A70D09670D059E9/NVIDIA_SHIELD/Streaming/file-147/stream193.ts.tmp to /storage/3A70D09670D059E9/NVIDIA_SHIELD/Streaming/file-147/stream193.ts
[hls @ 0x201f85fc00] failed to rename file /storage/3A70D09670D059E9/NVIDIA_SHIELD/Streaming/file-147/stream.m3u8.tmp to /storage/3A70D09670D059E9/NVIDIA_SHIELD/Streaming/file-147/stream.m3u8
2017/10/31 17:22:15 [HLS] Starting transcoder for file-147 at 3m18s (encoder=h264_mediacodecndk, resolution=360, deinterlacer=linear, bitrate=720)
2017/10/31 17:22:15 [HLS] Stopping transcoder session file-147 @ 0s

Maybe a disk failure? You could try shutting things down for a bit and then booting back up to see if that helps.