record error clobbers New/Ready

[peabody]

due to poor planning on my part, i was running chkdsk on D: (where my recordings go) when a scheduled recording tried to start. this locks the partition so the recording failed, understandably. But the odd part is that immediately after this, the "What's New" list was completely empty and the "Ready" list had only 2 items in it (previously, both had been a full screen's worth at least). gbpvr is installed on C:.

i'm attaching the logs. the event should be just after "Error starting recording" in GBPVRRecordingService.exe-1.log.

[sub]

If GB-PVR cant find the recordings in the original place it recorded them, it assumes you've manually deleted them, so it removes them from the database. This is done to ensue things are cleaned up, but there is a couple of scenarios that can cause problems.

You can disable this default behaviour by editing a setting in config.xml.

[peabody]

Thanks, sub, that solves the mystery!

In hindsight, I kind of thought that type of cleanup was going on at some point, I just hadn't expected it to be at recording start or end. But that makes sense, since the front-end startup may happen infrequently. It might be slightly more error-tolerant if it checked that the top-level recording folder was readable before doing cleanup. Admittedly this kind of error is rare.