How to delete seemingly corrupted recordings?

[three6zerocool]

Is it advisable to set the timeshift directory onto a NAS as opposed to an actual hard drive?

Reason being, I created a timeshift dataset and share on my NAS for timeshift data.
I have some recurring series configured.

What has happened is that NextPVR says it is currently recording, but when I try and jump in to watch the currently recording show, I get the unable to play stream error message, which is the same one I got when I did not have the timeshift folder configured correctly.

What seems to have happened, is that the TS file in the recording folder does not increment and stays at zero size.
When the recording is finished, the filesize is still zero.

I try deleting the file in NextPVR web interface of Kodi interface, and it does nothing.
Similarly, if I go to the recording folder and try manually deleting the relevant files, it gives errors of files in use.

I am guessing that configuring live TV timeshift location to the NAS was not a good thing to do?

How should I go about cleaning up the rogue recordings?

I have configured the timeshift folder back to a local drive, and things seem to be working fine again, with the exception of the couple of rogue recordings, which don't really seem to be there, as they are zero bytes in size.

[three6zerocool]

Update:

After rebooting the system, NextPVR no longer lists the recordings at all.
However, I have a folder on the NAS with 3 files in it that I cannot delete.


SmackDown_20230729_12001405.timing    (also zero bytes)

SmackDown_20230729_12001405              (the 0 byte TS file)

SmackDown_20230729_12001405.ts.map    (size of 5KB)

[sub]

I'm guessing it's something permission related with the share you're trying to use.

I seem to remember as user in the past they weirdly had permission to create a file, but not write to it or delete it. Almost sounds like what is happening there.

[three6zerocool]

Update:  *solved*

Thanks Sub.

I looked at the permissions and could see nothing really out of the ordinary.

Restarted the NAS,  (TrueNAS) and then I was able to delete the offending files.

I had created a dataset on the NAS for Timeshift as well as an SMB share, so maybe something weird with the NAS software.

I have been recording to the NAS for a very long time now,  but had only just started placing the timeshift on there.
Seemingly this was the cause of my issue.

I have put the timeshift back onto local drive.

[Rich A]

Sorry to jump in here but I have the same problem..  I do NOT have any NAS  etc.  Just a simple HTPC running Nextpvr and not much else. Since I first installed the latest version I have had several on going problems ONE of which is exactly what you are describing here.  I randomly have shows that can NOT be deleted.  Tried everything even starting an elevated command prompt and manually deleting the file (the old DOS way) and got the SAME result .  "File is in use".  

With the older version we had an easy way to get to an option to "RESTART" the NPVR Service.  I'm new to this version (been using the old legacy 4)  And not being able to find any user setting for "restarting the service?) I brought up my windows services panel and after shutting off NPVR (which still didn't help) I finally was able to be able to DELETE the files after  turning off NextPVR and THEN manually shutting any kind of service or whatever I could see still running concerning Nextpvr..  

Once I turned off NextPVRService (32 bit),  server, and Tray, I was then able to delete those files.  Sorry I just turned them ALL off so I don't know which one fixed it.  IF you have the problem again, shut down NextPVR and stop either the "server" or "service" and I bet then you'll be able to delete the files.    Sorry to jump in here, and didn't want to hijack your thread but I've been messing with the same problem for the last week and thought I'd add my 2 cents.  Hope Sub sees this as I just had to delete another file for the third time in the last couple weeks. Just found THIS thread because before I start a new one I like to see if the problem is already being work on.

[sub]

Sorry to jump in here but I have the same problem..  I do NOT have any NAS  etc.  Just a simple HTPC running Nextpvr and not much else. Since I first installed the latest version I have had several on going problems ONE of which is exactly what you are describing here.  I randomly have shows that can NOT be deleted.  Tried everything even starting an elevated command prompt and manually deleting the file (the old DOS way) and got the SAME result .  "File is in use".  

With the older version we had an easy way to get to an option to "RESTART" the NPVR Service.  I'm new to this version (been using the old legacy 4)  And not being able to find any user setting for "restarting the service?) I brought up my windows services panel and after shutting off NPVR (which still didn't help) I finally was able to be able to DELETE the files after  turning off NextPVR and THEN manually shutting any kind of service or whatever I could see still running concerning Nextpvr..  

Once I turned off NextPVRService (32 bit),  server, and Tray, I was then able to delete those files.  Sorry I just turned them ALL off so I don't know which one fixed it.  IF you have the problem again, shut down NextPVR and stop either the "server" or "service" and I bet then you'll be able to delete the files.    Sorry to jump in here, and didn't want to hijack your thread but I've been messing with the same problem for the last week and thought I'd add my 2 cents.  Hope Sub sees this as I just had to delete another file for the third time in the last couple weeks. Just found THIS thread because before I start a new one I like to see if the problem is already being work on.

Reproduce the problem, then post the logs and we'll take a look.

[three6zerocool]

Interesting.

I did actually disable the nextpvr service and tray, and it made no difference.
I even had a complete image of my system, so nuked everything and installed the backup, and still could not delete the files.

In the end, rebooting the NAS allowed me to delete the offending files.
I thought the issue was to do with me changing the location of timeshift buffer to the NAS but might just be a coincidence.

It has not happened to me again 'yet', but if it does, I will post logs.

[three6zerocool]

Further Update:

I think I have worked out how I got 'zero' sized TS file recordings.

I recently configured a new system, and I backed up and migrated  my existing configuration.
The new rig had new tuners, which I deleted the originals, and configured the new tuners, however, it pulled in all the recurring recordings from original system.

Both rigs were configured to capture to my NAS.
Seemingly, what has happened is that the recordings have started, but I had disconnected the antenna cables and plugged them into the new rig, and also disconnected the STB feed and connected it to the to new rig.

So, essentially it was trying to record from sources with no input connected.
This resulted in files of zero size.  It seemed to start recording from my original rig first, rather than the new one.

Likely some issue occur when 2 different rigs are trying to record to same NAS, using the same recording schedule.
Does that sound a reasonable explanation?.

I have deleted all the recurring series recordings on the original rig, and so far thigs seem to be workiing OK on the new rig

Just thought I would clarify my discovery.

..Dean..