Shows not recording and always losing connection

Channels DVR Server
#1

@tmm1, what do you make of this error log? All my recordings didn't record today and they show as still queued up even thought the times are now in the past:

2019/09/06 17:33:36 [DVR] Error running job 1567826940-37 House Hunters: could not start stream on channels=[6104]: TVE: mkdir /storage/emulated/0/Streaming/channels-cache-119001662: read-only file system
2019/09/06 17:34:07 [DVR] Starting job 1567826940-37 House Hunters on ch=[6104]
2019/09/06 17:34:07 [DVR] Waiting 4h24m52.946025203s until next job 1567843140-23 Hawaii News Now at 10:00
2019/09/06 17:34:07 [ERR] Failed to start stream on channel 6104 via TVE-Comcast_SSO: TVE: mkdir /storage/emulated/0/Streaming/channels-cache-867155077: read-only file system
2019/09/06 17:34:07 [ERR] Failed to start stream on channel 6104 via TVE-sony_auth-gateway_net: TVE: mkdir /storage/emulated/0/Streaming/channels-cache-457750048: read-only file system
2019/09/06 17:34:07 [DVR] Error running job 1567826940-37 House Hunters: could not start stream on channels=[6104]: TVE: mkdir /storage/emulated/0/Streaming/channels-cache-457750048: read-only file system
2019/09/06 17:34:37 [DVR] Starting job 1567826940-37 House Hunters on ch=[6104]
2019/09/06 17:34:37 [DVR] Waiting 4h24m22.45316985s until next job 1567843140-23 Hawaii News Now at 10:00
2019/09/06 17:34:37 [ERR] Failed to start stream on channel 6104 via TVE-Comcast_SSO: TVE: mkdir /storage/emulated/0/Streaming/channels-cache-998340351: read-only file system
2019/09/06 17:34:37 [ERR] Failed to start stream on channel 6104 via TVE-sony_auth-gateway_net: TVE: mkdir /storage/emulated/0/Streaming/channels-cache-985124434: read-only file system
2019/09/06 17:34:37 [DVR] Error running job 1567826940-37 House Hunters: could not start stream on channels=[6104]: TVE: mkdir /storage/emulated/0/Streaming/channels-cache-985124434: read-only file system
2019/09/06 17:35:07 [DVR] Starting job 1567826940-37 House Hunters on ch=[6104]
2019/09/06 17:35:07 [DVR] Waiting 4h23m52.419327154s until next job 1567843140-23 Hawaii News Now at 10:00
2019/09/06 17:35:07 [ERR] Failed to start stream on channel 6104 via TVE-Comcast_SSO: TVE: mkdir /storage/emulated/0/Streaming/channels-cache-122903433: read-only file system
2019/09/06 17:35:08 [ERR] Failed to start stream on channel 6104 via TVE-sony_auth-gateway_net: TVE: mkdir /storage/emulated/0/Streaming/channels-cache-263442772: read-only file system
2019/09/06 17:35:08 [DVR] Error running job 1567826940-37 House Hunters: could not start stream on channels=[6104]: TVE: mkdir /storage/emulated/0/Streaming/channels-cache-263442772: read-only file system
2019/09/06 17:35:38 [DVR] Starting job 1567826940-37 House Hunters on ch=[6104]
2019/09/06 17:35:38 [DVR] Waiting 4h23m21.781096124s until next job 1567843140-23 Hawaii News Now at 10:00
2019/09/06 17:35:38 [ERR] Failed to start stream on channel 6104 via TVE-Comcast_SSO: TVE: mkdir /storage/emulated/0/Streaming/channels-cache-731515043: read-only file system
2019/09/06 17:35:38 [ERR] Failed to start stream on channel 6104 via TVE-sony_auth-gateway_net: TVE: mkdir /storage/emulated/0/Streaming/channels-cache-401971110: read-only file system
2019/09/06 17:35:38 [DVR] Error running job 1567826940-37 House Hunters: could not start stream on channels=[6104]: TVE: mkdir /storage/emulated/0/Streaming/channels-cache-401971110: read-only file system
2019/09/06 17:36:08 [DVR] Skipping job because program already started 1567826940-37 House Hunters
2019/09/06 17:36:08 [DVR] Waiting 4h22m51.706271343s until next job 1567843140-23 Hawaii News Now at 10:00
2019/09/06 18:01:06 [NAT] Successfully mapped port 8089 using natpmp
2019/09/06 18:37:00 [TNR] Opened connection to 10765FA3 for ch10.1 KMEB-HD
2019/09/06 18:37:00 [HLS] Starting transcoder for channel 10.1 from 192.168.1.61 (encoder=h264_mediacodecndk, resolution=1080, deinterlacer=blend, bitrate=8000)
Could not write header for output file #0 (incorrect codec parameters ?): No such file or directory
Error initializing output stream 0:0 --
2019/09/06 18:37:18 [WRN] Buffer for 10765FA3 ch10.1 is more than 50% full (clients=1, len=16777684)
2019/09/06 18:37:24 [WRN] Buffer for 10765FA3 ch10.1 is more than 75% full (clients=1, len=25166000)
2019/09/06 18:37:29 [WRN] Buffer for 10765FA3 ch10.1 is more than 95% full (clients=1, len=31877468)
2019/09/06 18:37:29 [WRN] Buffer for 10765FA3 ch10.1 is more than 99% full (clients=1, len=33219788)
2019/09/06 18:38:42 [HLS] Stopping inactive session ch10.1-dANY-ip192.168.1.61 @ 0s
2019/09/06 18:38:42 [TNR] Closed connection to 10765FA3 for ch10.1 KMEB-HD
2019/09/06 18:42:24 [ERR] Could not start stream for TVE-Spectrum ch6023 PARAMOUNTP: TVE: mkdir /storage/emulated/0/Streaming/channels-cache-495569613: read-only file system
2019/09/06 18:42:38 [ERR] Could not start stream for TVE-Spectrum ch6021 TVLANDP: TVE: mkdir /storage/emulated/0/Streaming/channels-cache-900080584: read-only file system
2019/09/06 18:49:49 http: TLS handshake error from 192.168.1.46:56723: remote error: tls: unknown certificate
2019/09/06 18:49:49 http: TLS handshake error from 192.168.1.46:56725: remote error: tls: unknown certificate
2019/09/06 18:49:51 http: TLS handshake error from 192.168.1.46:56727: remote error: tls: unknown certificate
2019/09/06 18:49:51 http: TLS handshake error from 192.168.1.46:56729: remote error: tls: unknown certificate
2019/09/06 18:49:56 http: TLS handshake error from 192.168.1.46:56732: remote error: tls: unknown certificate
2019/09/06 18:49:59 http: TLS handshake error from 192.168.1.46:56739: remote error: tls: unknown certificate
2019/09/06 18:50:05 http: TLS handshake error from 192.168.1.46:56744: remote error: tls: unknown certificate
2019/09/06 18:50:06 http: TLS handshake error from 192.168.1.46:56749: remote error: tls: unknown certificate
2019/09/06 18:50:06 http: TLS handshake error from 192.168.1.46:56751: remote error: tls: unknown certificate
2019/09/06 18:50:06 http: TLS handshake error from 192.168.1.46:56750: remote error: tls: unknown certificate
2019/09/06 18:50:06 http: TLS handshake error from 192.168.1.46:56752: remote error: tls: unknown certificate
2019/09/06 18:50:06 http: TLS handshake error from 192.168.1.46:56753: remote error: tls: unknown certificate
2019/09/06 18:50:06 http: TLS handshake error from 192.168.1.46:56758: remote error: tls: unknown certificate
2019/09/06 18:50:22 http: TLS handshake error from 192.168.1.46:56760: remote error: tls: unknown certificate
2019/09/06 18:50:23 http: TLS handshake error from 192.168.1.46:56765: remote error: tls: unknown certificate
2019/09/06 18:50:23 http: TLS handshake error from 192.168.1.46:56766: remote error: tls: unknown certificate
2019/09/06 18:50:23 http: TLS handshake error from 192.168.1.46:56767: remote error: tls: unknown certificate
2019/09/06 18:50:23 http: TLS handshake error from 192.168.1.46:56768: remote error: tls: unknown certificate
2019/09/06 18:50:23 http: TLS handshake error from 192.168.1.46:56769: remote error: tls: unknown certificate
2019/09/06 18:50:23 http: TLS handshake error from 192.168.1.46:56770: remote error: tls: unknown certificate
2019/09/06 18:50:23 http: TLS handshake error from 192.168.1.46:56771: remote error: tls: unknown certificate
2019/09/06 18:50:23 http: TLS handshake error from 192.168.1.46:56776: remote error: tls: unknown certificate
2019/09/06 18:50:34 http: TLS handshake error from 192.168.1.46:56788: remote error: tls: unknown certificate
2019/09/06 18:53:36 http: TLS handshake error from 192.168.1.46:56803: remote error: tls: unknown certificate
2019/09/06 18:53:36 http: TLS handshake error from 192.168.1.46:56804: remote error: tls: unknown certificate
2019/09/06 18:53:36 http: TLS handshake error from 192.168.1.46:56806: remote error: tls: unknown certificate
2019/09/06 18:53:36 http: TLS handshake error from 192.168.1.46:56809: remote error: tls: unknown certificate
2019/09/06 18:53:36 http: TLS handshake error from 192.168.1.46:56810: remote error: tls: unknown certificate
2019/09/06 18:53:36 http: TLS handshake error from 192.168.1.46:56811: remote error: tls: unknown certificate
2019/09/06 18:53:36 http: TLS handshake error from 192.168.1.46:56812: remote error: tls: unknown certificate
2019/09/06 18:54:00 http: TLS handshake error from 192.168.1.46:56817: remote error: tls: unknown certificate
2019/09/06 18:54:00 http: TLS handshake error from 192.168.1.46:56820: remote error: tls: unknown certificate
2019/09/06 18:54:00 http: TLS handshake error from 192.168.1.46:56819: remote error: tls: unknown certificate
2019/09/06 18:54:10 http: TLS handshake error from 192.168.1.46:56826: remote error: tls: unknown certificate
2019/09/06 18:54:10 http: TLS handshake error from 192.168.1.46:56828: remote error: tls: unknown certificate
2019/09/06 18:54:10 http: TLS handshake error from 192.168.1.46:56829: remote error: tls: unknown certificate
2019/09/06 18:56:09 http: TLS handshake error from 192.168.1.46:56992: remote error: tls: unknown certificate
2019/09/06 18:56:09 http: TLS handshake error from 192.168.1.46:56997: remote error: tls: unknown certificate
2019/09/06 18:56:09 http: TLS handshake error from 192.168.1.46:56999: remote error: tls: unknown certificate
2019/09/06 19:00:13 http: TLS handshake error from 192.168.1.46:57053: remote error: tls: unknown certificate
2019/09/06 19:00:13 http: TLS handshake error from 192.168.1.46:57055: remote error: tls: unknown certificate
2019/09/06 19:01:06 [NAT] Successfully mapped port 8089 using natpmp
2019/09/06 19:02:18 http: TLS handshake error from 192.168.1.46:57064: remote error: tls: unknown certificate

There are more of the same above the top, so I didn't send those since they're redundant.

#2

I just got this one too, which I'm confused on. How can my recording engine be "Read Only"?

2019/09/06 19:17:37 [ERR] Could not create backup: mkdir /storage/emulated/0/Database/backup-20190906.191737: read-only file system

#3

Latest:

2019/09/06 19:49:12 [TNR] Opened connection to 10765FA3 for ch4.1 KITV-HD
2019/09/06 19:49:12 [HLS] Starting transcoder for channel 4.1 from 192.168.1.46 (encoder=h264_mediacodecndk, resolution=, deinterlacer=blend, bitrate=10000)
[hls @ 0x22454c4c00] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
[mpeg2video @ 0x2245558e00] skipped MB in I-frame at 67 2
[mpeg2video @ 0x2245558e00] Warning MVs not available
pipe:: corrupt decoded frame in stream 0

BTW, 192.168.1.46 is my MS Surface laptop I am using now. The server is on an nVidia Shield using a USB 500GB external self powered drive.

#4

The shield is not allowing write access to your drive. I don't know why this would happen. Maybe the USB drive is failing or full.

Our recommended configuration on the SHIELD is to use adopted storage instead of internal storage, and set the DVR path as /storage/XXXX-XXXX/NVIDIA_SHIELD/DVR

#5

I’m not sure what you mean by adopted storage? I am using external storage not internal (as far as I knew anyway haha!) with a 500 GB USB self powered hard drive.

How do I set it up the way you’re suggesting?

Thanks man, you guys rock!!!

#6

I don't have one but duck duck go and google show this
https://nvidia.custhelp.com/app/answers/detail/a_id/4025/~/how-to-increase-your-internal-storage-on-shield-tv

#7

External storage is the recommended way so you are doing it correctly.

1 Like
#8

Does a SHIELD go into sleep/power saving modes?
Maybe if the SHIELD is powering his external USB drive and the SHIELD goes to sleep it's not providing power to the external USB drive and takes too long to power/spin it up?

#9

As I already said, it is a self powered USB drive.

Thanks for all the suggestions and answers everyone!

#10

If I were once again using my Shield for a DVR ... I would definitely not allow it to go to sleep mode ... by disabling sleep and also enable developer options and disable sleep mode there . I would also make sure that HDMI CEC setting is not set to power off when TV is turned off.

1 Like
#11

Awesome tips Edwin, I will certainly look into those!

#12

If you're still getting the read only error then you should reboot the SHIELD.

#13

Thanks but I’ve done that countless times. Do you think it could be the router at all? I’ve suspected maybe mine is having issues but haven’t been able to nail it down.

#14

That error comes from the operating system, which is Android TV in this case.

You said you're using external storage, but your path looks like its saving your recordings to internal storage.

External storage paths start with something like /storage/XXXX-XXXX/NVIDIA_SHIELD

#15

Oh I think I know why it looks like that. When you install an external drive on the Shield, I think it initially asks you if you want it to be an extension of the internal storage or used as a separate external and removable drive. I think I recall setting that option as the former (internal extension). Maybe some Shield experts here know for sure?

I mounted this drive long before I installed Channels DVR. It has worked great for a long time with Channels and only recently has had these issues.

Do you think it best to remove it and then reinstall it as a pure external drive?

#16

That's what I was referring to earlier wrt adopted vs external storage.

Adopted storage is encrypted and can only be accessed by the SHIELD. External storage can be moved around to any other device.

Before reformatting as external you would presumably want to use some sort of file explorer to copy your recordings somewhere.

#17

Oh duh! Thanks for the clarification.

So which is better for channels then, adopted or external? To me it sounds like external based on what I think you’re saying.

How can I access the drIve from an external source if it’s encrypted?

#18

Encryption is at rest.

When the device is running, on the device that encrypted it, then it’s unlocked to be used by services like local access and sharing.

2 Likes
#19

OK, I am getting many of the same errors now again for some reason. The BIG difference is, this is a new nVidia Shield Pro 2019 (old one with same errors was a 2017 model) and also a new 2TB external USB HDD. It is definitely connected and being used as an external drive on the Shield, as instructed by @tmm1 a year ago, plus I made sure to follow all the suggestions to disable sleep mode, CEC, etc.

It appears mostly to be issues with TVE recordings, which almost all get cutoff early from recording, so for the news shows I record via TVE that are supposed to be an hour/60 minutes, they almost all get stopped and cutoff prematurely. After they're "done" and in the recordings folder they show truncated show times of like 28 minutes, 36 minutes, 18 minutes, etc. (out of what should be 60).

I am fairly certain that the nVidia Shield Pro should be able to record and play back more than about 3-4 concurrent streams, no? It seemed to be working just fine for the first few months I've had this new setup, now these errors again. :frowning:

Here are the latest log entries if these help any. I sent a diagnostic file report a few days ago and haven't heard anything since:

2020/09/03 11:59:00.016288 [DVR] Starting job 1599170340-38 Special Report With Bret Baier on ch=[6073]
2020/09/03 11:59:00.017679 [DVR] Waiting 1h0m59.982332742s until next job 1599174000-5 NHL Hockey
2020/09/03 11:59:01.606621 [TVE] stream timestamps: fnc: start_at=2020-09-03T11:59:05-10:00 current_at=2020-09-03T11:59:25-10:00 end_at=2020-09-03T11:59:34-10:00
2020/09/03 11:59:01.606722 [TNR] Opened connection to TVE-Comcast_SSO for ch6073 FNC
2020/09/03 11:59:01.754195 [DVR] Recording for job 1599170340-38 from TVE-Comcast_SSO ch6073 into "TV/Special Report With Bret Baier/Special Report With Bret Baier S2020E177 2020-09-03-1159.mpg" for 1h1m59.982247377s
2020/09/03 11:59:01.766897 [IDX] Generating video index for job 1599170340-38
2020/09/03 11:59:23.297812 http: TLS handshake error from 192.168.1.46:58900: remote error: tls: unknown certificate
2020/09/03 11:59:23.340321 http: TLS handshake error from 192.168.1.46:58902: remote error: tls: unknown certificate
2020/09/03 12:00:04.662176 http: TLS handshake error from 192.168.1.46:58913: remote error: tls: unknown certificate
2020/09/03 12:00:04.701318 http: TLS handshake error from 192.168.1.46:58915: remote error: tls: unknown certificate
2020/09/03 12:04:46.460375 http: TLS handshake error from 192.168.1.46:58932: remote error: tls: unknown certificate
2020/09/03 12:04:46.497842 http: TLS handshake error from 192.168.1.46:58934: remote error: tls: unknown certificate
2020/09/03 12:04:49.343961 http: TLS handshake error from 192.168.1.46:58936: remote error: tls: unknown certificate
2020/09/03 12:04:49.543786 http: TLS handshake error from 192.168.1.46:58939: remote error: tls: unknown certificate
2020/09/03 12:04:49.556559 http: TLS handshake error from 192.168.1.46:58940: remote error: tls: unknown certificate
2020/09/03 12:04:49.556675 http: TLS handshake error from 192.168.1.46:58938: remote error: tls: unknown certificate
2020/09/03 12:05:17.835549 [DVR] Pruning old recording Special Report With Bret Baier S2020E174 2020-08-31-1159.mpg
2020/09/03 12:05:17.839952 [DVR] Pruning old recording MLB Baseball Atlanta Braves at Philadelphia Phillies 2020-08-28-1259.mpg
2020/09/03 12:05:18.091621 [DVR] Deleting /storage/CE9E6EE99E6ECA13/NVIDIA_SHIELD/Channels DVR/TV/Special Report With Bret Baier/Special Report With Bret Baier S2020E173 2020-08-28-1159.mpg
2020/09/03 12:05:21.552664 [DVR] Deleting /storage/CE9E6EE99E6ECA13/NVIDIA_SHIELD/Channels DVR/TV/NFL Live/NFL Live 2020-08-25-0959.mpg
2020/09/03 12:22:13.672875 [TNR] Cancelling stream TVE-Comcast_SSO ch6073 after 2m0s read timeout
2020/09/03 12:22:14.386446 [MTS] Statistics for "TV/Special Report With Bret Baier/Special Report With Bret Baier S2020E177 2020-09-03-1159.mpg": skipped=0 unhandled_packets=0 discontinuity_detected=43 transport_errors=0 invalid_pts=0 invalid_dts=0 saw_pcr=false saw_pmt=true highest_pts=1283.899356
2020/09/03 12:22:16.649042 [TNR] Closed connection to TVE-Comcast_SSO for ch6073 FNC
2020/09/03 12:22:16.747782 [DVR] Job 1599170340-38 Special Report With Bret Baier ended prematurely: 38m43.252232598s
2020/09/03 12:22:16.764659 [DVR] Starting job 1599170340-38 Special Report With Bret Baier on ch=[6073]
2020/09/03 12:22:16.764722 [DVR] Waiting 37m43.2352914s until next job 1599174000-5 NHL Hockey
2020/09/03 12:22:19.127666 [TVE] stream timestamps: fnc: start_at=2020-09-03T12:22:22-10:00 current_at=2020-09-03T12:22:43-10:00 end_at=2020-09-03T12:22:51-10:00
2020/09/03 12:22:19.127793 [TNR] Opened connection to TVE-Comcast_SSO for ch6073 FNC
2020/09/03 12:22:19.156946 [DVR] Recording for job 1599170340-38 from TVE-Comcast_SSO ch6073 into "TV/Special Report With Bret Baier/Special Report With Bret Baier S2020E177 2020-09-03-1159.mpg" for 38m43.235240723s
2020/09/03 12:28:07.814315 http: TLS handshake error from 192.168.1.46:59165: remote error: tls: unknown certificate
2020/09/03 12:28:07.835098 http: TLS handshake error from 192.168.1.46:59167: remote error: tls: unknown certificate
2020/09/03 12:28:07.847663 http: TLS handshake error from 192.168.1.46:59168: remote error: tls: unknown certificate

Again as before, the IP address showing tls certificate errors is the IP for my Windows Surface Pro tablet. Those tls errors only populate the logs when I have the Surface Pro on and am using it to look at the Channels DVR Server on the Shield. Could that be what is causing these issues by chance? How would my Surface Pro, which isn't even watching a Channels DVR show, cause issues on my nVidia Shield's Channels DVR Server??? How do I fix it so these tls errors don't show up in my Channels DVR Server's logs, and of course fix the recordings being cutoff?

Another symptom I see is when I am watching a recording after it is finished and it appears that it recorded the entire show properly, after watching for about 10-30 minutes or so, the stream starts glitching, pausing, stopping, getting choppy, etc. This happens on any client I try it on, TiVo Stream 4K, AppleTV 4K, etc.

Any clues? As always, thanks for the incredible service here!

#20

This seems like the key log entry error:

2020/09/03 12:22:13.672875 [TNR] Cancelling stream TVE-Comcast_SSO ch6073 after 2m0s read timeout